Short answer: keep drafts out of the data room. Let each team work on drafts in its own workspace, give one person per workstream the right to publish, and upload a new version under the same file name into the same folder, so the room replaces the document instead of adding a near-duplicate. Use the room's version history where it exists, mark the change in a short "updated" log, and tell guests about material updates on purpose rather than on every upload. Check how your provider handles versions first: some keep a full history, others simply replace the file.
Why version control goes wrong in data rooms
- Too many uploaders. Legal, finance and HR each upload "final_v3_clean.pdf" – buyers see three files and do not know which one counts.
- Renamed files. A new name means a new document: the old one stays visible, and some rooms only treat a same-name upload as a new version.
- Silent replacements. A number changes in the financials, nobody tells the bidders, and the Q&A later quotes the old figure.
- Per-page billing. On per-page plans, every re-uploaded draft can be billed again (see data room cost).
How data rooms and file-sharing tools handle versions
| Provider | Keeps earlier versions | Guests told about updates | Limits / notes |
|---|---|---|---|
| Ansarada | Yes – document history, restore an earlier upload | Optional "notify affected users" when updating – off by default | – |
| iDeals | Yes – new versions do not overwrite the history (product page) | Not stated | – |
| Firmex | Yes – uploading a file with the same name and extension creates a new version (announced 2015) | Not stated | Check current behaviour with Firmex |
| Intralinks | "Replace" a document (VDRPro); Filesplit replacements keep earlier alert links pointing to the new file | Filesplit: no new alert by default | Replacing fails if the file was moved or renamed |
| Box | Yes | Not stated | Business / Business Plus 50 versions, Business Starter 25, Personal Pro 10 |
| SharePoint | Yes | Not stated | Default 500 major versions; admins can change it |
| Dropbox | Yes | Not stated | 30 days (Basic, Plus), 180 days (Standard, Business), 365 days (Advanced, Business Plus) |
| Google Drive | Yes – "Manage versions" for uploaded files | Not stated | Older versions deleted after 30 days or 100 newer versions unless marked "Keep forever" |
| HelpRange | No history – a same-name upload replaces the document behind every existing link and room | Guests always open the latest file; tell them in the room or by e-mail | Keep the previous version in your own archive folder |
| Datasite, SecureDocs | No public help page found on versioning – ask the vendor | ||
Sources: Ansarada; iDeals; Firmex; Intralinks VDRPro and Filesplit; Box; SharePoint; Dropbox; Google Drive.
A version-control process that works with several teams
- Separate drafting from publishing. Drafts live in each team's own drive; the data room holds only documents ready for the other side.
- Name a publisher per workstream (legal, finance, commercial, HR). Only they upload into their part of the index.
- Fix the file name, not the version number. "3.2 Customer contracts – top 20.pdf" stays the same name; the date of the current version goes in the document or the index, not in the file name. Same name + same folder = replaced, not duplicated.
- Keep a change log – a one-page "Updates" document at the top of the room: date, document, what changed.
- Notify deliberately. Material changes (financials, key contracts) get a message to the affected bidders; typo fixes do not.
- Archive superseded versions outside the guest-visible folders, especially if your room does not keep a history, so you can show later what each party saw and when.
- Freeze before key dates – no uploads in the 48 hours before bids or signing, except agreed corrections.
In HelpRange
Uploading a file with the same name into a data room updates that document: every guest and every link opens the new version, and nothing has to be re-shared. HelpRange does not keep earlier versions, so archive the previous file yourself if you need a record. Per-guest activity shows who opened each document and when, so you can see who has read a document since it changed. Data rooms are included in Pro (up to 3 rooms) and Unlimited ($174 per team a month), or $199 once for a single deal with the Deal Room Pass.
FAQ
How do I manage version control in a virtual data room?
Keep drafts out of the room, let one publisher per workstream upload, replace documents under the same file name, keep a short change log, and notify guests about material updates. Use the room's version history where it exists.
Do data room guests see old versions?
Usually they see only the current version. Admin-side history exists in Ansarada, iDeals, Box, SharePoint, Dropbox and Google Drive; other rooms replace the file, so archive the old one yourself.
Are guests notified when a document is updated?
Only if you choose to: Ansarada's update notification is off by default and Intralinks Filesplit replacements send no new alert. Tell guests about material changes on purpose.
Should version numbers go in file names?
No. A new file name creates a new document next to the old one in most rooms. Keep the name stable and record the version date inside the document or in the index.
Related: how to set up a data room · data rooms with audit logs · what is a virtual data room.