Pergamon’s document versioning helps you track changes, maintain revision history, and restore previous document states without losing work. Each version is preserved so you can review, compare, and restore earlier versions at any time.
How document versioning works
Every time you restore a version, Pergamon generates a new version number. All versions are listed in the Version history tab, where you can view content from any previous point in time.
In Version history, you can:
View older versions in read-only mode
See who created each version
Read the version description
Restore a previous version by creating a new version based on it
Version numbering
Pergamon uses a two-part version number:
Major.Minor
Examples: 1.0, 2.3, 3.4
Major version → Used for significant changes
Minor version → Used for incremental updates
When restoring a version or creating a new one, you choose whether to increment:
Minor version → 3.3 → 3.4
Major version → 3.3 → 4.0
Initial version
Every new document in Pergamon starts at Version 1.0. This includes documents created:
manually (“Create Document”), or
automatically through Document Assembly
Version 1.0 represents the first saved state of the document. All later versions are increments of this baseline.
Viewing older versions
You can open any version from the Version history tab. Older versions open in View mode, which allows you to inspect content but not edit it.
If you decide to reuse an older version, you must restore it.
Restoring previous versions
Restoring allows you to bring older content back into the current workflow. When you restore a version:
Pergamon does not replace the old version
Instead, it creates a new version containing the restored content
Earlier versions remain unchanged
Example: Restoring Version 1.0 while working on Version 3.3 results in a new version such as 3.4.
This protects version history and prevents accidental loss of information.
Creating a new version
You can manually create a new version at any time from the Documents Hub, without restoring older content.
Use More actions → New version when you want to begin a new revision cycle or prepare a major update. You can:
Increment the major or minor version number
Add comments describing the change
Start editing the new version immediately
Why restored versions create a new version
Because Pergamon maintains an immutable version history, restoring earlier content always results in creating a new version. No historical version is ever deleted or overwritten.
This design protects revision integrity and prevents accidental content loss.
Purpose of version comments
Why version comments matter
Version comments provide meaningful context for each saved version. They help teams understand:
What changed
Why a change was made
When and by whom it happened
They are essential for:
Audit trails
Regulatory compliance
Translation workflows
Collaboration
Debugging issues or reversing changes
Clear version comments make version history useful and trustworthy.
Key benefits of document versioning
Full audit trail
Safe recovery of older content
Immutable historical record
Clear major/minor update tracking
Read-only inspection of older versions
Comments
0 comments