Secure inbox: receiving and requesting files

External parties upload files encrypted and without an account. With a secure inbox, shared pools and a guided request for individual documents.

SecureFiles receives files just as securely as it sends them. External parties upload encrypted, without an account of their own. The occupied storage counts towards the account of the inviting person.

Secure inbox

The secure inbox is a public upload link. Create it once, share the link, and others upload files to it. Only the inviting person sees the files, the uploader stays anonymous.

For anonymous upload, upper limits can be set so that an inbox does not overflow:

  • Maximum number of files and maximum total volume, each summed across all callers.
  • Maximum size per file and permitted file types.
  • Optional password protection for the upload link, shared out of band.

Shared pool

A shared pool is a shared upload folder with invited members. Existing tenant members receive direct access, external addresses are released by invitation. Limits apply per member: storage, number of files, maximum file size and permitted file types. In addition a total pool storage limits the volume of all members together. The pool suits ongoing collaboration with suppliers or project partners.

Requesting files in a structured way

Instead of a bare upload link, a guided request can be built. Under Request documents, create groups with the expected documents, each document mandatory or optional, with a format hint. The recipient opens the link in the browser, sees a checklist of what is still missing and uploads document by document.

Recurring requests such as onboarding or opening an account can be saved as a template. During review each document is accepted or returned with a request for correction, without the whole request starting over. Background on the solution page creating a file upload form.

Further reading

Every upload is virus checked and recorded in the audit log. How recipients and uploaders are protected is described in recipient authentication. How the occupied storage is distributed is described under storage and quota. On active sending see sending files, and use cases on the solution page secure inbox. Back to the SecureFiles overview.