> For the complete documentation index, see [llms.txt](https://docs.spara.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.spara.com/agents/channels/configuring/saving-and-publishing.md).

# Saving & Publishing

Every Spara channel has two states at any given time: a **draft** and a **published version**. They work independently: your team edits and tests the draft while leads only ever interact with the published version.

<figure><img src="/files/99xgYjkhSGZVR3D1YRno" alt=""><figcaption><p>Version History lists every published version, so you can restore any one to roll back.</p></figcaption></figure>

## Drafts

Any change you make in the editor (to the instructions, abilities, or configuration) is saved to the draft. Drafts are private. They do not affect live conversations until you explicitly publish.

To save changes to your draft, click **Save draft** in the editor header. You can save as often as you like. The draft persists between sessions, so you can make changes over multiple sittings before publishing.

**Testing always uses the draft.** The built-in [Testing](/agents/channels/configuring/testing.md) interface and [Simulations](/agents/channels/configuring/testing.md#simulations) always run against the current draft, so you can validate changes before going live.

## Publishing

When you're satisfied with your draft, click **Publish** in the editor header. Publishing makes the draft the new live version, and all new conversations immediately use the updated channel.

Each channel has exactly one published version at a time. The previously published version is retained in Version History.

{% hint style="info" %}
**Chat channels** require at least one activation trigger on any non-default channel before publishing. If a non-default channel has no triggers, the publish button will show an error.
{% endhint %}

## Version History

Click **Version History** in the editor header to see a list of all previously published versions, newest first. Each entry shows who published it and when.

Select any version to preview its instructions. Click **Restore** to create a new draft from that version. Restoring does not publish; it gives you a draft to review and test before going live again.

## Unpublishing

To pause a live channel without deleting it, click **Unpublish**. Unpublished channels are not shown to leads. If the one you're unpublishing is the default for its channel, Spara will prompt you to confirm, since incoming traffic will have no channel to handle it until you publish a replacement.

## FAQ

### Do saved drafts affect live leads?

No. Saving a draft never affects live conversations. Only publishing changes what leads see.

### What happens if I publish and then notice a bug?

Open Version History, select the previous version, and click **Restore**. This creates a draft from the old version. Publish it to roll back immediately.

### Can multiple people edit the same draft?

Yes, but changes are not merged; the last save wins. Coordinate with your team to avoid overwriting each other's edits.


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.spara.com/agents/channels/configuring/saving-and-publishing.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.