USE CASE
Collect files back from clients through a share link
A share link can allow uploads as well as downloads. Files sent back wait in a review queue until someone on your team accepts or rejects them.
The situation
Clients are asked for logos, copy, signed documents or photography, and the files come back by email, in chat or through several different transfer services. Someone then has to find them, rename them and file them, and nothing records who sent what or when.
Who this is for
- Agencies
- Brand and marketing teams
- Event organisers
- Freelance designers
What happens, step by step
- 1
Create a share link for the project and switch on upload. Download and comments are separate options.
- 2
Optionally set a password, an expiry date and a short message for the recipient.
- 3
The recipient opens the link and confirms their email address with a one-time code. Nothing is installed.
- 4
They upload files on the same page they download from.
- 5
Uploads go to a review queue with a thumbnail and their origin. They are not part of the library yet.
- 6
A team member accepts a file, which files it as an asset in a Received via share folder, or rejects it. Rejected files are deleted after 30 days.
Related use cases
-
Receive revisions from external designers in one place
Receive each round of freelance work through one link and keep revisions as versions.
Read the use case: Receive revisions from external designers in one place -
Replace email attachments with one link
Send one link in place of attachments and one-off file transfers.
Read the use case: Replace email attachments with one link -
See what happened to a file you shared
See who opened, downloaded or uploaded through each share link.
Read the use case: See what happened to a file you shared