Update notice
❗ Note: This article has been updated to reflect upcoming changes to Version History and the Audit Trail, expected to go live on October 21, 2026. Until then, you may still see the See full history option in your workspace.
For easing the transition period, clicking the Version History will automatically redirect you to the Audit Trail.
Who Is This For?
Authors / Owners – validating edits before promoting state
Reviewers / Approvers – confirming changes and decision history
QA / Managers – investigating actions and ensuring compliance evidence
How to Do It?
Step 1: Compare versions to see what changed
Use Compare to identify differences between the current version and an earlier one.
Open the document, then select the three-dots menu in the top bar.
Click Compare.
Choose the earlier version to compare against the current version.
Review highlighted differences (e.g., content, state changes, role assignments).
❗ Compliance reminder: Always verify tracked changes and metadata before approvals to ensure the record reflects the intended edits.
📎 Reference: Navigating the Document Page
Step 2: Open and analyze the Audit Trail
Trace every action taken on the document for full accountability.
From the three-dots menu, select Open Audit Trail.
Sort by column headers or apply filters to focus on specific activity types.
Use this view to see who did what, when, and what changed.
Review version history in the Audit Trail
In the Audit Trail, select Filter and choose the event Version created.
Review the list of version events. The state of each version is shown (for example, Released for training).
Select a version event to review the version differences, plus the change summary and justification where they exist for that version. By clicking on the object a side panel with all executed changes will open.
Select View this version to open that specific version.
If you have the right permissions, you can revert to the selected version. Reverting creates a new version with the content of the version you selected.
💡 Tip: Regular audit events, such as assignments, stay separate from version-change events. Filtering by Version created shows only version changes. For example, assigning a training record on the document does not create a new version.
❗ Compliance reminder: The Audit Trail is a controlled quality record. Use filters to locate evidence for inspections and investigations; do not work from downloaded copies as your source of truth.
📎 Reference: Searching and Filtering Records
Step 3: AI-Powered Summary
The AI-Powered Summary feature automatically generates a concise summary of document changes, streamlining the review process. This is available starting from the second version (V2) of a document.
Steps to Generate an AI-Powered Summary:
Before sending a new version of the document for approval, select Generate Summary to create an AI-powered summary of the recent changes.
Review, edit, and format the summary as necessary.
The summary will highlight key modifications, approvals, and actions, allowing for a quicker understanding of the document's evolution.
Tips
💡 Start with the Audit Trail filtered by Version created to locate the right prior version, then use Compare for line-by-line differences.
💡 Capture screenshots or export views (where applicable) for audit packages to show exactly what was reviewed.
💡 If an action is missing from the Audit Trail, check your permissions and confirm you’re viewing the correct document.