Early Access Feature
File Versioning
Vault files now have version history — edits from Harvey threads or uploaded files save as a new version on the same file, keeping Vaults clean and original content always preserved and recoverable.
Interested in testing this feature?
Contact your Customer Success Manager for early access.
Overview
When you edit a file in a Harvey thread, or upload a file with the same name into a Vault folder, you can save that change as a new version on the existing file instead of producing a separate copy. The original content stays intact in a previous version listing, so your Vault holds one entry per document instead of a set of duplicate files.
Each version records who saved it, when, and a short auto-generated note describing the change. You can preview, download, or restore any version in the chain at any time. Restoring an older version doesn't delete anything that came after it; restored content is added as the newest version on top of the chain.
Key Features
- Version chains: Every edit to a Vault file saves as a new version on that file rather than as a duplicate file.
- Non-destructive restore: Restoring a prior version adds it as the current version; it never deletes history.
- Save-as-new-version prompt: When a saved or uploaded file matches an existing filename, Harvey asks whether to add it to the version chain or create a separate file.
How to Use
Save a New Version of a Vault File in a Thread
- Attach a Vault file to a thread and ask Harvey to edit it.
- When Harvey presents the updated file, review and accept the changes.
- In the thread, hover over the file output and select Add to Vault.
- Choose the Vault where the original file resides and select Save to Vault.
- Because the file shares its name with your original Vault file, Harvey opens a dialog asking how to handle the duplicate. In the dialog, select Replace duplicates.
Your edit becomes the newest version attached to that file. The original content stays intact underneath and can be restored at any time.
Create a New Version by Re-Uploading a File to Vault
- In a Vault folder, upload a file that has the same name as an existing Vault file.
- In the dialog, select Replace duplicates to add the upload to the original file's version chain.
View, Download, or Restore a Version
- Select a file in your Vault, then open its version history from the right side panel.
- Select a version to preview or download it, or select the Restore version button to make an older version the current one.
Note: Restoring a version is non-destructive. It adds the version you chose to the top of the history; nothing is deleted.
Notes & Limitations
- Version history retains earlier drafts and pre-redaction copies until the file or those versions are deleted. This means that anyone with access to the file can download them. Take this into account if your workflow previously relied on overwriting a file to remove prior content.
- Prior versions inherit the same Vault permissions and ethical walls as the current version. If you can't see a file, you can't see its history either, and restore actions respect those same permissions.
- Restore only moves forward in the chain. There are no branching versions (or a "keep both" option) within a single file's version history.
- Deleting a file removes its entire version chain, and deleting a version removes everything created after it. If you re-upload a file with the same name after deleting the old one, it starts a fresh version chain.
FAQs
Q: What happens to the original file when a new version is created?
The original content is preserved underneath the latest version, and you can preview, download, or restore any earlier version in the chain at any time.
Q: If a file is split or merged, does the output stay in the same version chain?
No. Split outputs and merge outputs each become new files with their own version chains.