You keep a private version history of a document by replacing the file on the same document in your room each time it changes, rather than saving scattered copies across email threads and folders. The room keeps every earlier version, so you can check what changed and when, and earlier versions stay private to you and your room members unless you choose to show them on a link.
Steps to keep a version history
- Pick one home for the document, a single room, rather than letting copies spread across email, chat and local folders.
- Choose Replace file on the document each time it changes. The new file becomes the next version of the same document (same file type only: a PDF replaces a PDF). Only the document's owner can do this.
- Type a short reason under "What changed" (up to 500 characters). This text is shown to recipients as the reason the document changed, as well as kept in your Version history, so write it for both audiences.
- Keep recipients on the live link, which always shows the current version. If someone needs a frozen copy, open Version history, choose the version and select Share this version: it creates a separate link that always shows that version. This is the same behaviour covered in how to swap the file behind a link without resending it.
- Check back through the history when something is disputed. Open the document and use the Version button in the preview toolbar to open Version history. Each version lists its number, date, who uploaded it, its size, pages and your note, and you can open any of them to read it.
- Tidy up unpublished drafts. A draft you never published can be deleted from Version history; published versions stay in the history, so anything ever shared remains on record.
Edge cases and what to check
A private version history inside your room is not the same as a legally binding record of what a signer saw. If a document was signed, the audit certificate is the record that matters for that specific version, since it captures a SHA-256 fingerprint of exactly what was signed. Keep both: the room's history for your own working trail, and the signed certificate for anything that needs to hold up later.
Only the document's owner can replace the file, and a replace made from an out-of-date copy is refused with a message to reload, so two near-simultaneous uploads cannot silently overwrite each other. Members can read the history but not replace the file. Once a document is sent for signature its file cannot be replaced at all, so the room never shows different bytes from the agreement that was signed.
Version history is on every plan, including Free. Free and Plus upload PDFs, so each version of a PDF is another PDF; Word, Excel and PowerPoint are on Pro and above, and a Word document stays a Word document across its versions. Check pricing to see which plan fits before you commit a whole document set to one plan.
After building a version history, check that the current version genuinely reflects what you think it does, that anything already sent externally is clearly distinguishable from internal drafts, and that anyone who needs to reference an old version can actually find it rather than relying on someone's memory of what changed.
If your current tool cannot do this
Version history built out of file names on a shared drive, "final_v3_reallyfinal.docx" and similar, fails the moment two people edit at once or someone forgets to rename a file. Judge a tool against these questions before trusting it to hold your history.
- Does uploading a new file replace the old one in a tracked way, or does it just sit alongside every previous version with no clear "current" copy?
- Can you tell who changed what and when, or only that the file's timestamp is more recent?
- Is the history private to your team by default, with you deciding whether a link may show earlier versions?
A tool that treats a document as one thing with a history, rather than a folder of loosely related files, clears this bar. In 99 Data Rooms, earlier versions are private by default and visible only to you and your room members, and Save as draft in the replace dialog keeps a revision off every link until you publish it. What is a virtual data room, and do you actually need one explains why a structured room beats a shared folder for exactly this reason, our comparison of data room vs shared drive covers the same gap in more depth, and if the change ever needs undoing entirely, our guide to version control for documents you have already sent covers that broader scenario.
Version history vs a shared drive of file copies
| Version history in a room | Renamed files on a shared drive | |
|---|---|---|
| What "current" means | The version marked current | Whichever file someone last renamed "final" |
| Recipient confusion | Low: the live link shows the current version | High, wrong file gets sent regularly |
| Team clarity on ownership | Clear: one document, one owner who replaces it | Depends entirely on discipline |
| Audit value if disputed | Each version records who uploaded it, when, its size and your note | Only as good as file timestamps |
A version history is really a discipline problem that a room's structure solves for you, rather than something you have to enforce through naming conventions and hope everyone follows.
Frequently asked questions
Is a private version history the same as an e-signature audit trail? No. Version history is your own working record of how a document changed over time. An audit trail is generated at the point of signing and records a fingerprint of the exact version that was signed, which is the record that matters if a signature is disputed.
Will recipients see my earlier drafts? Not by default. Earlier versions stay private to you and your room members unless you turn on "Show earlier versions" for a particular link, and an unpublished draft is never shown on any link.
How far back should I keep old versions? Published versions stay in the document's history, which is what you want for anything that was ever shared externally and might be referenced or disputed. Only a draft you never published can be deleted.
Do I need a paid plan to keep a version history? No. Version history is on every plan, including Free, for PDF documents. Word, Excel and PowerPoint are on Pro and above, since Free and Plus upload PDFs.
What if two people try to upload a new version at the same time? Only the document's owner can replace the file, and a replace made from an out-of-date copy is refused with a message to reload, so two near-simultaneous uploads cannot silently overwrite each other. Members can read the history but not replace the file.
Keep one trail, not five files
Stop naming files "final" and "final-v2". Replace the file on the same document in your room, keep recipients on the live link, and use the document's Activity tab to see whether the current version was actually opened before you assume the old one is history (the time on each page is from Plus). Start free and give your next document one home instead of five.
Sources
- Version-swap and tier behaviour reflect 99 Data Rooms product facts. General claims about shared-drive file naming and version confusion describe common workplace practice, not any single named vendor.