USE CASE
Keep a version history for files clients rely on
Replacing a file keeps the earlier one in the asset's history. Restoring an old version creates a new version, so nothing is overwritten.
The situation
Files called final, final-2 and final-use-this accumulate in folders and inboxes. People download an older copy, edit it and send it on, and nobody can say which version a client was actually given.
Who this is for
- Designers
- Agencies
- Marketing teams
- Print and packaging teams
What happens, step by step
- 1
Open the asset and replace the file with the new one.
- 2
The previous file moves into the asset's version history.
- 3
Anyone with access always gets the current version from the same asset page and the same share link.
- 4
Download any earlier version when you need to check what was sent.
- 5
Restore an earlier version and it comes back as a new version, so the history stays complete.
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 -
Keep brand assets and their licences in one place
Hold logos, colours, fonts and guidelines together with the licence details of each asset.
Read the use case: Keep brand assets and their licences in one place -
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