Versions

Music is iterative. Mix 1 becomes mix 2 becomes the master. Geniviv is built for that: instead of scattering mix_v1, mix_v2, mix_final across a drive, you keep one file with many versions.

How versions work

A file in Geniviv isn’t a single frozen thing — it’s a stack of versions:

• The newest upload is the current version — what people get when they open or download the file.
• Every previous take is still there, in order, in the file’s version history.
• Nothing is ever silently overwritten. A new take is added on top, never instead.

One file, one home

Because all takes live under one file, there’s never confusion about which is “the file.” There’s just the file — and its history. Sharing, access, and activity all stay attached to that one file across every version.

Adding a new version

1. Open the file you want to update.
2. Choose to add a new version and upload your new take.
3. It becomes the current version; the previous one drops into history.

Everyone with access sees the update, and anyone who cares about the file gets a notification that a new version landed.

Tip

Adding a version is for new takes of the same thing. A genuinely different file should be its own upload. The rule of thumb: “Is this a new draft of this file, or a new file?”

Reviewing history

Open a file’s version history to see every take in order — who uploaded each one and when. It’s the story of how the work evolved, in one place.

Who can add versions

Adding a version is an edit, so it requires at least Editor access:

• Viewers can open and download, but not add versions.
• Editors and Owners can upload new versions.

See Sharing & access for the full breakdown.

Locking a file

When a file is finished — the master is signed off — an Editor or Owner can lock it. A locked file is protected from further edits until it’s unlocked, so nobody accidentally uploads over a final. It’s the “do not disturb” sign for your most important work.