Forms
File Requests
Ask anyone to upload documents to you. A gated inbox for files, on Team and Business plans.
A file request reverses the share link: instead of pushing a document out, you ask someone to push files in. ID documents, proofs, deliverables, anything that belongs in your library.
Creating a request
- Name and description. What you are asking for; the uploader sees this.
- Destination. Where received files land in your library.
- Access. The same gate family as share links: email verification, password, expiry, max submissions.
- Guidance. Instructions and the file types you expect, shown on the upload page.
Share the request link. The uploader needs no account.
What the uploader sees
A clean upload page with your branding and instructions: drag files, see them verified, submit. Files upload through the same resumable pipeline as your own uploads. Large files do not die on flaky connections.
What lands on your side
- Files arrive in your library, tagged to the request. Traceable to who sent them and when.
- The request's record shows every submission: uploader identity (verified or claimed), file list, timestamps. In the audit trail.
- Requests respect plan limits: Team allows 100 active requests, Business 500. Hobby and Starter do not include the feature.
States
- Open. Accepting uploads.
- Closed / expired. The link stops accepting; received files stay in your library.
- Limits reached. A request at its submission cap refuses further uploads and logs the attempt.
Requests vs envelopes vs forms
- File request. "give me documents." Files in, nothing signed.
- Web form. "give me answers." Data in, optionally a signature.
- Power Form. "sign this." A document out, a signed copy back.
Combine them in a flow: a file request for the ID, a Power Form for the agreement, a data room for the ongoing exchange.