> For the complete documentation index, see [llms.txt](https://help.blings.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.blings.io/apps/blings-studio/flow-preview-and-publishing.md).

# Draft Preview and Publishing

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.

{% tabs %}
{% tab title="Save Project" %}

<figure><img src="/files/wTMWlq1p9aWEO7VnRlsG" alt="Studio view mode with View Draft and Publish controls in the project bar"><figcaption></figcaption></figure>

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.
{% endtab %}

{% tab title="View Draft" %}

<figure><img src="/files/ejWQrAAE9ZZVm79dJil8" alt="Studio project bar with Save Project, View Draft, and Publish controls"><figcaption></figcaption></figure>

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.
{% endtab %}

{% tab title="Publishing" %}

<figure><img src="/files/ejWQrAAE9ZZVm79dJil8" alt="Studio project bar with Save Project, View Draft, and Publish controls"><figcaption></figcaption></figure>

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.
{% endtab %}
{% endtabs %}

## Draft and Publish Workflow

{% stepper %}
{% step %}

### Save the Project

Use Save Project when the current Studio edits should be stored in the project draft.
{% endstep %}

{% step %}

### Review the Draft

Use View Draft to check the draft player state outside the editing canvas.
{% endstep %}

{% step %}

### Confirm Flow Map

Open Flow Map and verify the selected lineups, scene order, condition branches, and A/B test paths.
{% endstep %}

{% step %}

### Test With Platform Simulation

Use Platform's Simulate Personas area to validate the same flow with representative viewer data.
{% endstep %}

{% step %}

### Publish Completed Changes

Publish when the draft has been reviewed and the project should expose the updated configuration.
{% endstep %}
{% endstepper %}

## 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.

{% hint style="info" %}
Publishing affects the project state outside the editor. Keep unfinished scenes, incomplete branches, and experimental connector changes in draft until they have been reviewed.
{% endhint %}

{% content-ref url="/pages/o3Uq9AhtjBVAMsxuyMFA" %}
[Flow Map basics](/apps/blings-platform/flow-map.md)
{% endcontent-ref %}

{% content-ref url="/pages/VkH17x1J2SH1VmvzEgwU" %}
[Simulation](/apps/blings-platform/simulation.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.blings.io/apps/blings-studio/flow-preview-and-publishing.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.