When a policy or procedure changes, you should not create a duplicate library entry unless you truly need a new record. Use Upload new version on the existing row so the current semver advances and prior revisions remain in history. Requires document_management:upload_new_version.
Step 1: Find the document
From the document library table, locate the correct title. Use search and status filters if the list is long—getting the right logical document matters more than the filename alone.
Step 2: Open “Upload new version”
Open the row Actions menu and choose Upload new version. A modal asks for the replacement file and version details.
Step 3: Provide the new file and version
- File: Pick the authoritative new file from your machine.
- Version: Enter the next semantic version (for example bump minor or patch per your scheme).
- Version notes: Optional context for reviewers and auditors (what changed, ticket reference, approval ID).
What happens next
The API stores the new binary, updates the document’s current version pointer, and retains older rows in Version history. Your ISMS evidence chain stays intact: you can prove which file was current at a point in time.
Storage and errors
If the tenant is at storage quota, the upload may fail—resolve quota in Subscription management or remove unneeded inactive bytes where policy allows. Multipart validation errors surface a clear message; fix the input and retry.
Manage versions in ISMSVision
Log in and open the document library to roll forward controlled documents safely.
Log in to ISMSVision