Version History
Every time changes are saved to a form (Welcome Page, Message Page, Form Pages, etc.), a new version is created. Versions are numbered sequentially (e.g., v270, v271, v272...) and listed in the Version History panel, most recent at the top.
Each version entry shows:
- Version number (e.g., v273)
- LIVE tag — marks the version currently published and visible to end users
- Saved — who saved this version and when
- Published — who published this version and when (if it was ever published)
- Preview icon (eye) — view this version without making it live
- Restore icon (branch) — revert the form to this version's content
Use the All / Published tabs at the top of the panel to filter between every saved version or just the ones that have gone live.
Save vs. Publish vs. Revert
- Save — saves your current changes as a new version. This does not affect what end users see. The page shows an "Unpublished changes" indicator until you publish.
- Publish — takes the current saved version and makes it live for end users. This is the only action that changes what's live.
- Revert — discards your unsaved changes and returns the editor to the last saved version.
- Restore (in the version list) — takes an older version and makes it the current draft, creating a new version with that older version's content. You'd then still need to Save/Publish to make it live.
How saving and publishing work across multiple admins
- Versions are sequential regardless of who makes the change. If Admin A saves changes, that creates version 123. If Admin B then saves changes (even without A ever publishing), that creates version 124.
- Version 124 automatically carries forward everything from version 123, plus Admin B's changes — unless Admin B restores an earlier version or edits the form to undo those changes.
- Any admin with access can choose which version to publish, regardless of who saved it. Publishing isn't restricted to "your own" changes.
- Only one version can be LIVE at a time. Publishing a version makes it live and supersedes whatever was previously live.
Example scenario: Admin A saves changes but doesn't publish (v123). Admin B then makes and saves additional changes (v124, which includes A's changes plus B's). Admin B publishes v124. The live site now reflects both A's and B's changes — not just B's — because B's version was built on top of A's.