Versioning

Overview

Your project uses a versioning system to help you safely manage changes. Every time you save changes to your project, a new version is automatically created.

Draft vs Published

Versions exist in two states:

• Draft - Working versions where interviews are recorded as test/preview intervies

• Published - The live version that your users interact with

How Versioning Works

When your project is still testing, each save automatically becomes the Active version. Once published, new saves create versions which don't go live automatically. It's important to note that you should hardly ever need to make changes to a published project, but just in case we've got that scenario covered.

Scenario: You've made a few edits to your project and it's still testing in draft mode

V3 (draft) <= Currently active (interview link loads this version) 
V2 
V1 

Action: Make changes + save The active version is automatically bumped up

V4 (draft) <= Currently active (interview link loads this version) 
V3 
V2 
...more versions 

Action: You're happy with the project and launch it. The project is published

V4 (published) <= Currently active (interview link loads this version) 
V3 
V2 
...more versions 

Action: You decide to make some more changes + save A new version (V5) is created, but the active version is not changed

V5 
V4 (published) <= Currently active (interview link loads this version) 
V3 
...more versions 

Action: you decide you like your changes and decide to publish V5

V5 (published) <= Currently active (interview link loads this version) 
V4 
V3 
...more versions 

Key difference: Publishing "locks" your live version, protecting users from seeing work-in-progress changes until you're ready.

Version History

You can view your complete version history in the Assistant=>Versions tab. Click any version to view it. You can restore or publish previous versions using the three-dot menu.