Quick answer: Use email attachments for a small, low-risk one-off exchange when the recipient and version are obvious. Use a shared folder when both sides need continuing access to the same working files. Use an upload request when clients need to send files to your team but should not browse other clients’ submissions. Decide by who must see, add and revise each file, then test that route with a sample document.
For: small service teams collecting briefs, images and project documents. This is an operating decision, not a security certification or a promise that any tool meets your industry’s legal requirements.
Decide in three steps: (1) Name whether the client sends, receives or revises files. (2) Choose the narrowest route that permits that action. (3) Test access, version and arrival with a harmless sample before sending real material.
Map the direction of the work
Before sharing a link, name the file owner and answer three questions. Is the client sending files to you, receiving files from you, or collaborating on a common set? Will the same document be revised? Who must still access it after the current staff member leaves? These answers decide the route more reliably than the size of a single attachment.
On a small screen, swipe the table sideways to see all columns.
| Route | Use when | Check before sending |
|---|---|---|
| Email attachment | One small, final file goes to a known recipient once. | Recipient, file version, size and whether the business needs a durable copy outside one inbox. |
| Shared folder | Named people on both sides need to read or edit a changing set of files. | Viewer versus editor access, link scope, ownership and how access will be removed. |
| Upload request | Clients need to submit files without seeing the team’s working folder or other submissions. | Upload destination, storage capacity, naming, expiry and who reviews new files. |
For a concrete product example, Dropbox distinguishes viewing, editing and collecting files. Its file request lets people upload without a Dropbox account; the destination is private by default unless you choose or share a shared folder. These are documented capabilities, not a hands-on evaluation of Dropbox against another service. Check the current account’s limits and controls before relying on them.
Choose a route for an illustrative project
A small design agency asks a client for a logo, brand colours and three approved photos. The client only needs to submit originals. An upload request fits that direction: it avoids adding the client as an editor to the agency’s working folder. The project manager sets a named destination and asks the client to label each file with the project and subject. This is an illustrative workflow, not a real client case.
After receipt, the agency reviews the files and places approved versions in a working folder available to the assigned team. If the client must comment on drafts over several weeks, a separate shared folder with named access may be more suitable. The team should not turn the intake folder into an unrestricted long-term project space just because the first upload succeeded.
Run four acceptance tests
- Outside view: Open the invitation as the intended recipient would. Can they do the required action without seeing unrelated files?
- Version: Upload or share a clearly named sample. Can the reviewer distinguish it from an older version, and is there one agreed location for the approved copy?
- Notification: Confirm who notices the arrival and when the file is considered reviewed. A link that accepts uploads but is never checked is an unfinished process.
- Exit: Remove a test collaborator or close a test request using the product’s normal controls. Confirm the team retains the approved files and knows which links remain active.
Do not use real private client data for a casual test. For sensitive or regulated records, agree on the required handling, retention and access policy with the responsible professional before choosing a tool.
Make the file route part of onboarding
Ask for a file only when the delivery owner knows what decision it will support. For a one-time brief, put the request and its due date beside the intake form. For repeated draft reviews, name the current version, approver and authoritative location in the team checklist. Our client onboarding decision guide separates the form that gathers answers, the checklist that tracks team work and a portal used for continuing client review.
Hypothetical example: a client sends three approved photos. The receiving owner marks each as received or missing and tells the designer which versions may be used. If the client later replaces one photo, the owner moves the old file out of the approved set and records the replacement decision. The upload confirmation alone does not mean a file is approved for production.
Mark received, usable and approved separately
A delivery team can lose a day by treating an upload notification as permission to proceed. In a hypothetical website job, three photos are requested, two arrive, and only one has been approved for the page. Record each photo against the request: missing, received for review, usable or approved for this version. The receiving owner checks the files; the named client approver makes the content decision. The designer can continue an unrelated page while the last decision is open.
If the missing file changes a promised review date, send one specific request and name the next check. The missing client inputs guide provides a copyable request and a rule for which work can continue. Do not leave “waiting on files” as the only status; a colleague needs to know which file, which version, who owes it and when the date will be reassessed.
Keep a simple file exchange record
Record project, file type, sender, receiving owner, route, destination, reviewer and deletion or retention decision. Make the owner responsible for moving accepted files from intake to the project’s durable record. A client should receive one clear instruction: what to send, how to name it, where to send it and what confirmation to expect.
If a file exchange is part of leaving a tool, use our SaaS data export checks to verify the formats and dependencies. For an agency handover, use the website handover guide to confirm the business owns the essential assets and accounts.
Sources and limits: Dropbox sharing routes and file request documentation, reviewed October 2, 2026. The example is illustrative. No account-side upload, security audit or provider price comparison was conducted for this article.
Useful detail: Let an upload arrive without granting folder access
Dropbox file requests accept uploads from people without a Dropbox account, and a closed request stops new uploads until reopened.
For a one-way document collection, a file request can avoid giving the client a shared-folder role. The receiving folder and capacity still need an owner.
Try this:
- Create a dedicated destination for this collection.
- Test one harmless file from the requester’s link.
- After the collection is complete, close the request and retain the agreed record of what arrived.
Source: Dropbox: create and manage file requests. Checked October 3, 2026. The practical check is a PSL suggestion.
