> For the complete documentation index, see [llms.txt](https://docs.supademo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.supademo.com/workspace-settings/demo-versioning.md).
# Demo Versioning
***
{% hint style="info" %}
Demo versioning is available on **Growth plans and above**. Want to list, preview, or restore demo versions programmatically? [Try using the Supademo MCP.](https://docs.supademo.com/customize/mcp-server)
{% endhint %}
### **What is Demo Versioning?**
Demo versioning separates your **draft** from your **published demo**. With versioning enabled, edits you make in the editor stay in a private draft — viewers keep seeing the last published version until an authorized publisher hits **Publish**. Every publish saves a restorable version, so your team can iterate safely, review what changed, and roll back at any time.
This is especially useful for larger teams where multiple people edit demos, but only a few people should control what customers actually see.
***
### **Enable demo versioning for your workspace**
Demo versioning is a workspace-wide setting managed by workspace Admins.
1. Open **Workspace Settings** and find the **Demo Versioning** section
2. Turn on **Enable demo versioning**
3. Choose your **Publishing access** (see below)
4. Click **Save** and confirm
When you enable versioning, every existing demo in your workspace receives an initial version. Nothing changes for your viewers — each demo's public or private visibility stays exactly as it was.
***
### **Choose who can publish**
Publishing is always limited to **Admins and Creators** — Viewers can never publish. Beyond that, you can choose between two publishing access modes:
* **All Admins and Creators** — everyone with an eligible role can publish demos.
* **Selected publishers** — only the specific Admins and Creators you designate as **official publishers** can publish. Use the member table to search and select at least one publisher.
{% hint style="info" %}
With **Selected publishers** enabled, new demos won't be published automatically when they're created. An official publisher must review and publish them manually before viewers can see them.
{% endhint %}
You can update the official publisher list at any time from the same settings section — changes apply immediately across the workspace.
***
### **Editing with Versioning Enabled**
With versioning on, the editor always works on the draft:
1. Make changes in the editor as usual — steps, hotspots, annotations, voiceovers, and so on
2. Use **Preview draft** to see your work-in-progress exactly as a viewer would
3. Use **Preview published** to compare against what's currently live
4. When you're ready, click **Publish** to push your draft live and save a new version
Team members who aren't authorized publishers can still edit drafts freely — they just won't be able to publish. The Publish button will indicate that publishing is limited to authorized publishers in the workspace.
***
### **Version History**
Every publish creates a numbered version in the demo's version history. From the version history panel you can:
* **Browse the timeline** of published versions, including who published each one and when
* **Preview any version** to see exactly what viewers saw at that point in time
* **See what changed** between versions
* **Restore a version** to bring its content back into your draft
* **Duplicate from a version** to spin off a new demo based on a past version
***
### **Restoring a previous version**
Restoring brings a past version's content back into your **draft** — it doesn't immediately change what viewers see, and it doesn't delete any of your version history.
1. Open the demo's **version history**
2. Select the version you want to bring back and preview it to confirm
3. Click **Restore** and confirm
4. Review the restored draft, then click **Publish** to make it live
***
### **Turning versioning off**
Workspace Admins can turn demo versioning off at any time. Demos return to the standard publishing flow, where edits go live as you make them. Existing version history is retained but unavailable while versioning is off — turning it back on restores access to previously saved versions.
***
## **FAQs**
#### Who can enable or disable demo versioning?
> Only workspace Admins can manage demo versioning, and the workspace must be on a Growth plan or higher. Other members will see the settings as read-only.
#### What happens to my existing demos when I turn versioning on?
> Every existing demo receives an initial version so it has a starting point in its history. Nothing changes for viewers — public demos stay public, private demos stay private, and the live content is untouched.
#### Can Viewers or non-publishers still edit demos?
> Members can keep editing drafts according to their normal role permissions. Versioning only controls the **publish** step: with "Selected publishers" enabled, only official publishers can push a draft live. Everyone else's edits simply stay in the draft until a publisher publishes them.
#### Do viewers see my edits right away?
> No. With versioning enabled, anyone viewing or embedding your demo sees the latest **published** version. Your draft edits stay private until an authorized publisher clicks Publish.
#### Does restoring a version overwrite my newer versions?
> No. Restoring copies a past version's content into your draft — your version history stays intact. The restored content only goes live once you publish, which saves it as a new version on top of your history.
#### Why can't I click the Publish button?
> Your workspace likely has publishing restricted to selected publishers, and you're not on the official publisher list. Ask a workspace Admin to either add you as an official publisher or publish the demo for you.
#### What happens if I turn versioning off and back on later?
> Turning versioning off returns your workspace to the standard flow where edits go live immediately. Your saved version history isn't deleted — it becomes unavailable while versioning is off, and turning versioning back on restores access to it.
***
### **Benefits**
* **Safe iteration** — Edit freely in a private draft while viewers keep seeing the last published version.
* **Controlled publishing** — Limit who can push changes live with official publishers, so only the right people control what customers see.
* **Full history** — Every publish saves a restorable, numbered version you can browse, compare, and roll back to.
* **Confident rollbacks** — Restore a previous version into your draft without losing any history or disrupting viewers.
* **Team-friendly** — Multiple people can edit at once while publishing stays gated to a trusted few.
***
### **Use Cases**
Multi-Editor Teams
Let several teammates edit the same demos at once while keeping the live experience stable — everyone works in the draft, and only what's published reaches viewers.
Reviewed Releases
Gate publishing to a small group of official publishers so changes are reviewed before they go live, ideal for regulated, high-visibility, or customer-facing demos.
Rollback After a Bad Edit
If a change doesn't land well, restore a previous version into your draft and republish — no lost history and no scramble to rebuild the old content.
Branching From a Past Version
Duplicate a demo from an earlier version to spin off a variation — perfect for seasonal campaigns, A/B tests, or persona-specific edits without touching the original.
***
> ✨ **The Result:** Your team iterates on demos safely — edits stay private, only trusted publishers go live, and any previous version is one click away from being restored.