Document Version Control in TouteGestion
How TouteGestion keeps document revisions together, preserves version history and prevents updated files from becoming disconnected copies.
What version control solves
Business documents change. Replacing files manually or circulating names such as final-v2 and final-final makes it difficult to know which copy is authoritative. TouteGestion keeps revisions under one document record so the document identity remains stable while its file versions evolve.
Add a new version
On a document, a user with documents management permission selects a replacement or revised file. A file is mandatory. Optional manual text can be supplied to support search when useful. TouteGestion adds the file through the document version workflow rather than creating an unrelated new document.
Keep the current record connected
The document maintains a current-version relationship while previous version records remain part of its history. This means metadata, access, approval and retention controls continue to apply around the governed document instead of being lost every time a file changes.
Search and traceability
Search results expose information from the current version while the document detail retains its version history. This is useful for policies, contracts, procedures and other records where staff need the latest working copy without erasing evidence of earlier revisions.
Approval and versions
An approval request can target a specific version or the document workflow as configured. When review matters, submit the version that should be assessed instead of treating an emailed attachment as proof of approval.
Practical example
A human-resources policy can begin as version 1, receive a revised file after legal review and later receive another operational update. Staff continue to open the same document record while TouteGestion preserves the revision chain.
Review this workflow in the product.
See how governed records, access and lifecycle controls fit your organisation.