Document Versioning
v2026.4 · Updated 30 Sep 2026 · 2 min read
Before you start
Where you do this
Documents → Document Details → Version History
You will need
Nothing — this is background reading
Takes about
Two minutes
Document versioning
SasCon never lets you overwrite or delete a document outright. Instead, updating a document creates a new version on top of the existing record — called superseding — so the full history of how a document changed over the life of the project stays intact and traceable.
Version vs. Revision
The document register tracks two related but separate fields for tracking change:
- VersionLetter-based (vA, vB, vC)Auto-incremented each time a document is superseded; can be manually overridden
- RevisionPlain number (0, 1, 2, 3)Entered/updated manually as part of the document's metadata
Where version history lives
- Every document's Details page has a Version History tab listing each version that document has gone through.
- Each entry there corresponds to a completed Supersede action — there's no separate manual way to add a version outside of superseding.
- The Version History tab is read-only; you view past versions here, but make new ones through the Supersede action itself.
For the actual steps to create a new version, see Superseding a Document under Documents Management.
You need one of these roles:Viewing version history requires only project access (Viewer role and above). Creating a new version via Supersede requires the Uploader role or higher.
Related articles
Was this article helpful?
Version 2026.4 · Last reviewed 30 Sep 2026 by the SasCon documentation team