Draft Preview and Publishing
Save Studio changes, review the draft player, and publish completed updates
Studio keeps working changes separate from the published project. Use Save Project to store edits in the draft, View Draft to review the draft player state, and Publish when the reviewed changes should become available outside the editor.
Use Save Project when the current Studio changes should be stored in the project draft. Saving keeps the work available for review and continued editing, but it does not make the changes live for viewers.
When there are no unsaved Studio changes, Save Project remains disabled.
Use View Draft to open the draft player state outside the editing canvas. This is the review step for checking scene playback, dynamic content, interactions, and flow behavior before publishing.
Canvas playback is useful for checking the current scene while editing. View Draft is the broader review because it loads the project as a draft player experience.
Use Publish after the draft has been saved, reviewed, and approved. Publishing moves the reviewed project state into the viewer-facing publishing path.
Studio keeps Publish separate from Save Project so draft work and published updates remain distinct.
Draft and Publish Workflow
What to Check Before Publishing
Before publishing Studio changes:
Confirm the right scenes appear in the intended order.
Check dynamic text, media, colors, visibility, and timing with representative data.
Review connector behavior for buttons, inputs, timeline branches, links, and submitted forms.
Open Flow Map and test every connected branch that can affect the viewer path.
Use Platform simulation when the result depends on viewer data, URL parameters, CRM values, live controls, or catalog records.
Confirm stakeholders have reviewed the draft player state when approval is required.
Publishing affects the project state outside the editor. Keep unfinished scenes, incomplete branches, and experimental connector changes in draft until they have been reviewed.
Last updated