Upcoming Feature
File Versioning
Vault files now have version history — edits from Assistant or uploaded files save as a new version on the same file, keeping Vaults clean and original content always preserved and recoverable.
What's Coming
Before, editing a Vault file either created a duplicate or overwrote the original. File Versioning solves this and turns each Vault file into a version chain instead of a single static entry. When a file is edited, the change saves as a new version on the same file rather than as a separate file. Users can preview, download, or restore any prior version at any time, and the original content is always preserved underneath the latest version.
Feature Highlights
- Save edits from Assistant or uploaded files directly onto the original Vault file as a new version
- Preview, download, or restore any prior version at any time — original content is always preserved
- Eliminates duplicate file clutter — repeated edits collapse into a single file with a clean version chain
FAQs
Q: What happens to the original file when I save a new version?
The original content is always preserved underneath the latest version. You can preview, download, or restore any prior version at any time — nothing is permanently overwritten.
Q: Does this affect how files are stored in Vault?
Yes, in the best way. Instead of accumulating duplicate entries for every round of edits, each file maintains a single entry with a version chain attached. Vault stays clean regardless of how many edits a file goes through.
Q: Can I pull a specific version of a file into Assistant?
Yes. Users can select a specific version of a Vault file to work with in Harvey — useful for legal ops and DMS admins syncing historical versions from iManage, or in-house counsel tracking how a contract changed across negotiation rounds.