Documentation / Assets / Documents
Revisions
How document records connect to revision history in TrialStack and how teams keep changes traceable over time.
Documents are the governed assets. Revisions are the controlled change history that lets teams compare, restore, and understand how those assets evolved.
In the product
The tab keeps revision packages, version ranges, and revision templates visible beside the source document.
Why it matters
- a document has changed and the team needs a reviewable history
- a previous state needs to be compared or restored
- operators need to separate the current document from its revision trail