Version Control and audit history logs allow you to systematically track document changes, maintain comprehensive version history, and ensure compliance with regulatory standards, such as ISO 9001.
You can maintain detailed, immutable records of who made changes and when actions occurred. You can then easily export or share those records with external stakeholders or auditors.
Users: You must be an Administrator to enable Version Control.
Please contact our support team if you would like to trial this feature.
Version control can be enabled by an Admin from the organization settings page.
This lets you track version numbers and history on Workflows, Pages, Files and Forms.
You can choose between material and non-material changes when publishing updates to Workflows, Pages, Files and Forms.
The explanation of changes is mandatory since it will be added to the revision history table (more on this below).
Material changes will increase the version number by 1, and non-material changes will increment it by 0.1.
You can add reference Ids to the names of any Workflows, Pages, Files or Forms in your organization.
Click the settings cog when you’re in edit mode, and you can set the reference ID.
Reference IDs will show with the version number in your Library (shown below), in Reports (when you select the version columns) and in the editor focus bar.
Note: There’s a character limit of 100 characters on reference IDs.
Activity logs on Workflows, Files, Pages and Forms have a date range selector and an export function.
You can review up to one year at a time. For example, you can look at the last year or the year before, but not both of those years at the same time.
Export your data as a CSV file using the button shown above.
Note: You can view activity logs on Completed Workflow runs.
You can access revision history tables from the meatball menu on any Workflows, Files, Pages and Forms.
The table shows the version number, prefix (if used), who made revisions, when and the description of changes.
For Workflows, Pages, and Files, you can restore to a previous version from this table. Export the details via CSV to share with an auditor.
Note: Forms do not have the Restore action in the Revision History table. You can still view, export, and compare Form revision history.
For Files, each earlier published version in the Revision History table also has a View link (the current version doesn’t need one because it’s already displayed in the file viewer). Click a View link to open that version in the file viewer. A bar at the bottom of the viewer shows which version you are viewing and provides a View current version button to return to the latest version.
When you print a document or workflow, or save it as a PDF, the history table is displayed in a table at the bottom of the document.
For Pages, Workflows, Forms and Files, you can compare revisions to see exactly what changed.
In the Revision History table, a Compare link appears on every row except the current version. Click it to open an inline word-level diff that highlights the differences between that version and the current one. Use the From and To pickers in the comparison view to select any two published versions to compare.
If a Page has an unpublished draft, the meatball (…) menu in the editor shows a Compare with published option. This opens the same word-level diff view, so you can review your pending edits before publishing.
When discarding a Page draft, the discard dialog shows how many changes will be lost (for example, “This draft has 5 changes since version 1.0”). Click View changes in the dialog to review what will be discarded before confirming.
The comparison highlights the specific words that changed within each edited paragraph, rather than flagging entire blocks as different. Tables are compared row by row, making it easier to spot removed or changed content in table-heavy pages. Non-text content, including images, files, embeds, and workflow links, also appears in the comparison view.
When a Workflow has an unpublished draft, the meatball (…) menu in the editor shows a Compare with published option. This opens a task-grouped comparison view. Changes are organized by task and include:
The comparison loads fresh every time you open it, so it always reflects the latest edits.
The conditional logic editor also has its own Compare with published button in the editor header. Click it to open a logic-only comparison view that shows only your conditional logic rule changes. If you have unsaved rule edits, the view notes that those changes are not yet reflected in the comparison.
You can also compare versions from the Revision History table. Each published version except the current one has a Compare link. Click it to open a task-by-task comparison view with From and To pickers, so you can select any two published versions to compare.
Note: Comparing workflow versions requires edit access. The Compare column in the Revision History table is visible only to workflow editors. If you access Revision History as a reader (for example, from the Library row menu), the table does not include the Compare column.
When discarding a draft, the discard dialog shows how many changes will be lost (for example, “This draft has 5 changes since version 1.0”). Click View changes in the dialog to review what will be discarded before confirming. This discard comparison also works for Pages.
Some items are not versioned and do not appear in the comparison at all. App integrations (such as HubSpot, Jira, and Airtable), webhooks (including Zapier, Make, and Power Automate), incoming webhooks, and scheduled runs are saved on the workflow and take effect immediately rather than when you publish. The workflow name and sharing settings are also not versioned.
When a Form has an unpublished draft, a Compare with published button appears in the form editor’s top bar. Click it to open a comparison view organized by step, showing which form fields changed and what differs.
You can also open the comparison from the Revision History table. Access it via the Settings drawer in the form editor or from the Library row menu, then click the Compare link on any previous version.
When discarding a draft, the discard dialog shows how many changes will be lost (for example, “This draft has 5 changes since version 1.0”). Click View changes in the dialog to review what will be discarded before confirming.
When a File has an unpublished draft, the meatball (…) menu in the file editor shows a Compare with published option. This opens a text-based comparison view that highlights word-level differences between the draft and the current published version.
You can also compare versions from the Revision History table. Each published version except the current one has a Compare link. Click it to open the comparison view with From and To pickers, so you can select any two published versions to compare.
When discarding a draft, the discard dialog shows how many changes will be lost (for example, “This draft has 5 changes since version 1.0”). Click View changes in the dialog to review what will be discarded before confirming.
File comparison is text-based. When no text can be compared, the comparison view explains why:
You can track material and non-material changes by setting up webhooks in your organization’s integrations area.
Note: You’ll need to be an Admin to create webhooks.
This enables you to run a training workflow when a policy or procedure has significantly changed, for example.
Help us improve this help center.
