...
Additional recipients, to whom will the package be delivered, but will not be listed and visible as package recipients. Works similarly as a hidden/blind copy (BCC) in e-mails.
Contributors
If the user is allowed the cooperative packages feature, he can set contributors here who will also have the permission to modify the package (add, rename, or delete files). Contributors must have an account in the application and be logged in. Collaborating on a package cannot be done anonymously (without logging in).
Limited number of accesses
If the administrator enabled this feature, a logged in user can set a limit on number of accesses for a package when sending it. The administrator can also enforce this limit to be set for all users' sent packages.
A package with a limited number of accesses counts the accesses made by recipients and becomes inaccessible when all accesses are exhausted. The recipient is notified when trying to access a package with a limited number of accesses and is given a choice whether really to open the package and therefore exhaust one access. If he opens it, he can then download its contents without restrictions for the time set by the administrator (default 30 minutes) and it counts as one access.
Package accessibility (type)
...
For a detailed description of the form, see the section Anonymous upload of a file package. Only the differences are described here.
Packages waiting for approval before being sent
According to settings made by the administrator user’s packages may require approval before being sent out. In such a case a package is not really sent out and accessible to the recipients after being sent by the user, but is instead waiting in a queue of packages requiring approval. It must be approved or rejected by a user with appropriate permission, who is notified about waiting packages by an email, or by the administrator. The sender may be notified about approval or rejection of his package according to the settings made by the administrator.