How versions work: two switches, and the filename is the label

The whole model in one sentence: clients watch whatever is active, can only browse what you mark visible, and every version is called what its file was called.

Every time you upload a file onto an existing asset, it becomes a new version of that asset, the way re-exports pile up in your export folder (EDIT 10, EDIT 10_1, EDIT 11). The whole feature rests on one sentence: clients watch whatever is active, can only browse what you have marked visible, and every version is called what its file was called.

The two switches

• Active is the one version that plays everywhere the asset is shared: review links, embeds, reels. Exactly one version is active at a time. Uploading a file makes it active by default, and you can flip an older version back to active to roll back.
• Visible to reviewers decides whether clients can find a version in a review link's version list. This is off for everything by default, including every file you uploaded before this feature existed. Nothing a client did not already have shows up unless you turn it on.

Filenames, not V1 / V2

A version is labelled with its filename. No invented numbers, no renumbering to keep straight. The name in HoldFast, the name in your editing app, and the name your client types into their feedback are the same string. You can rename a label any time.

One rule of thumb

Revisions are versions; alternatives are separate assets. The typo fix, the new grade, the client-notes pass: versions of one asset. The 30-second cutdown and the vertical crop: their own assets, because a reviewer asked to compare "the film" wants cuts of the same film, not different deliverables.

Where this takes you

• Add a new version covers the three ways to get a file on.
• The quiet fix swaps the file behind a live link with nothing exposed.
• Publish a cut is the one deliberate path that ever shows a reviewer two cuts.
• Stage a draft parks a file on the asset without making it live.