Skip to main content

Version Control

Version management is planned, not yet available

Uploading new versions to an existing document record, browsing version history, and downloading or restoring prior versions are not yet available — neither in the UI nor via the API. This page documents the intended model. If versioning is a hard requirement for your workflow, contact your account team so the priority is recorded.

When versioning ships, Locker will automatically preserve the full history of every document. Each time a new version is uploaded, the prior version will be retained so executed agreements and signed copies remain recoverable regardless of how many updates follow.

How Versions Work​

  • Uploading a file for the first time creates Version 1.
  • Each subsequent upload to the same document record creates the next version (Version 2, Version 3, and so on).
  • The latest version is shown by default in the document list and on the document detail page.
  • All prior versions are preserved in storage and remain accessible.
Coming Soon

Screenshot: locker-document-version-indicator, the document detail page showing the current version number and a version history tab

Working with Multi-Revision Documents Today​

Until native versioning ships, the practical pattern is:

  • Upload each revision as a separate document and tag them so they cluster together in search and filters (e.g., nda-acme-corp plus revision:v2, revision:v3)
  • For Sign-originated documents, the executed copy lands in Locker as a fresh document record — keep the unsigned draft as a separate tagged record if you need both
  • Track the canonical "current" copy in your tag scheme; do not rely on a stable Version 2 / Version 3 numbering

When versioning ships, the existing tagged-revision documents will need to be reconciled into single document records.

When versioning is available, the workflow will be:

  • An NDA is amended, upload the amended copy as Version 2 of the original record
  • A draft contract becomes final, upload the executed PDF as the next version
  • A policy document is updated annually, upload each revision to the same record

Version Retention​

How long all versions are kept is controlled by your retention policy:

  • When the retention period expires, all versions are subject to the configured action (archive or delete), not just the latest.
  • Documents under Legal Hold retain all versions indefinitely, regardless of any policy.
  • If a document is deleted, all versions are permanently removed.
tip

For executed agreements and signed documents, set a retention policy that matches your legal or compliance requirements, not just business convenience. Losing a prior version of a signed contract is irreversible.

Sign-Originated Documents​

Agreements completed in Propper Sign are automatically stored in Locker as a new document record. Until native versioning ships, a re-executed or amended agreement produces a separate Locker record — keep them connected via tags or a stable name prefix so they cluster together in search.

See Sign & Locker Integration for how Sign documents land in Locker.