Creating a Dropbox

Go to Workgroups from the Faspex menu and select Create New > dropbox.

Name the dropbox.

If you want, enter instructions for submitters.

You can use HTML tags and CSS classes in your instructions.

For a list of available tags, see Available HTML Tags and Attributes in Faspex.

For more information on using CSS classes, see Creating a Custom CSS File.

If an administrator created metadata profiles for Faspex, you can apply a metadata profile to the dropbox. The metadata profile defines additional, optional and required fields for the dropbox package submission form.

For more information on setting up your metadata profiles for dropbox and normal package submissions, see Faspex Metadata.

If an administrator created metadata profiles for Faspex, you can choose to save the metadata information to the server's root directory as the aspera-metadata.xml file.

If SaveMetadataInPackage is set to true in the faspex.yml configuration file, Faspex includes the aspera-metadata.xml file in submitted packages instead of saving it to the server.

For more information about faspex.yml options, see faspex.yml Configurations Reference.

If you want to set an expiration policy for all submitted packages, select Custom package expiration policy and configure the expiration.

To set time-based package expiration, select Packages expire and set the number of days Faspex makes the package available.
Select an option for download-based package expiration:
- Do nothing: Do not delete the submitted package after it is downloaded.
- Delete files after any member of this dropbox downloads all files: Delete the submitted package if any dropbox member downloads all the files in the package.
  Important: When this option is selected, a forwarded package can be deleted before the original recipient has downloaded it.
- Delete files after all members of this dropbox download all files: Delete if all dropbox members have downloaded all the files in the package.

Note:

This policy overrides the global package expiration setting. If global package expiration is enabled, but you want to disable time-based and download-based package expiration for only this dropbox, select Custom package expiration policy, but clear Packages expire and select Do nothing.

For more information about global package expiration, see Configure Package Storage Expiration.

If you want to set an expiration policy for invitation links, select Custom invitation link expiration policy and configure the expiration.

To set time-based link expiration, select Invitation links expire and set the number of days Faspex keeps the link available.
To set download-based link expiration, select After one successful upload. The link expires after an outside submitters uploads one package.

Note:

This policy overrides the global link expiration setting. If global link expiration is enabled, but you want to disable time-based and download-based link expiration for only this dropbox, select Custom invitation link expiration policy, but clear all settings for Invitation links expire.

Configure encryption-at-rest (EAR). The Require encryption-at-rest only appears when enabled for dropboxes by an admin.

Choose from the following options.

Use server default: Use the globally conifgured option (displayed in parentheses).
Always: Always use EAR. Users must enter an encryption password when sending a password.
Never: Do not use EAR. This is the default setting.
Optional: Users may choose to encrypt when uploading a package.

For more information on encryption-at-rest, see Configuring Security Settings.

Allow submission of packages from a public URL. The Allow submission via public URL option only appears when enabled for dropboxes by an admin. For more information on public URLs, see Configuring Public URLs.

Important:

A Public URL can be used by external senders to submit packages to both registered Faspex users and dropboxes. Public URLs allow external senders to submit a package without being individually invited to submit a package. When a Public URL is enabled and sent to an email, instant message, website, and so on, the following workflow occurs:

The external sender clicks the Public URL for the dropbox.
The sender is directed to page where he or she is asked to enter and submit an email address.
A private link is automatically emailed to the sender.
The sender clicks the private link and is automatically redirected to the dropbox package submission page.
Once the package is submitted through the private link, the dropbox receives the package.

Select Allow to enable the Public URL feature for this dropbox. Select Deny to disable the feature for this dropbox. Changing the dropbox setting overrides the system default set in the Faspex Server settings.

Choose your dropbox's inbox destination. Packages sent to the dropbox are stored at this location.

Server default: Use the server default node and directory.
Custom: Choose from a list of local and remote nodes as the default location for your custom inbox.
- Incoming packages are stored in both the custom inbox and the default server inbox. Deleting packages from the default inbox through the web UI do not automatically remove the same packages from the custom inbox.
- Use the Upload directly to custom inbox option to prevent Faspex from storing a copy in the default inbox if the workgroup or dropbox is the only recipient of a package.
  Note: If a user sends a package to two workgroups or dropboxes, even if both workgroups and dropboxes are configured to upload directly to the custom inbox, Faspex stores the package on the default inbox and then relays the packages to the custom inboxes.

When selecting a Custom inbox destination, note the following:

Only Faspex admins can set the location of a dropbox inbox. dropbox admins do not have this power.
Incoming packages are stored in two locations: the custom location and the server default location. When packages are deleted from the default location through the Web UI, they are not automatically removed from the custom location.
Tip: If you do not want packages stored in two locations, you can select Senders upload directly to custom inbox. When this feature is enabled, packages sent to this dropbox are not stored in the default location but only in the custom inbox.
Even if symbolic links are enabled for a storage location, packages sent to a dropbox with a custom inbox will not be symbolic links. The default inbox location contains symbolic links, but custom inboxes contain actual files.

If you want to forward package to remote destinations, set up file relay. Select Enable Relay. For each desired destionation:

Check Relay.
If you want to overwrite files if they exist on the destination, check Overwrite.
If you want to notify users on relay start, error, or completion, enter a list of usernames or email addresses in the relevant field.

For more information about file relay, see File Relays.

Set permissions for dropbox admins and standard dropbox users.

Click the Create button.

Your new dropbox should now be listed on the Workgroups page along with any other existing dropboxes or workgroups.