USE CASE
Receive revisions from external designers in one place
An external designer gets one link to download the brief and upload each round of work. The team accepts files and keeps revisions as versions of the asset.
The situation
Freelancers send revisions by email, through personal storage or in chat. Rounds overlap, the wrong file gets forwarded to print, and the history of what changed between rounds is spread across several inboxes.
Who this is for
- Design studios
- In-house design teams
- Print and packaging teams
- Agencies working with freelancers
What happens, step by step
- 1
Put the brief, references and current artwork in a project.
- 2
Share the project with upload and comments enabled, and send the link to the designer.
- 3
The designer downloads the material and uploads each round of work on the same page.
- 4
Uploads wait in the review queue. A team member accepts or rejects each one.
- 5
To keep rounds together, replace the file on the existing asset. The previous round moves into its history.
- 6
Questions and answers stay in the comments on the link.
Related use cases
-
Collect files back from clients through a share link
Let clients upload through the share link and review each file before it enters the library.
Read the use case: Collect files back from clients through a share link -
Keep a version history for files clients rely on
Replace files without losing the earlier ones, and restore a version when needed.
Read the use case: Keep a version history for files clients rely on -
Run each client as a project with its own access
Give each client or campaign its own project, roles and message board.
Read the use case: Run each client as a project with its own access