> ## Documentation Index
> Fetch the complete documentation index at: https://docs.helpalive.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Publish Agent changes with the draft workflow
> Stage every Agent change as a draft, preview it on the Test tab, and publish all at once. Drafts never reach end users until you ship them.
Every change you make to the Agent — Train sources, Personalization, Appearance, Configuration — is staged as a **draft** until you publish. Drafts never reach end users until you ship them.
## How it works
When you have unsaved changes, a **draft banner** appears at the top of every Agent tab. From any tab you can:
1. **Preview** your changes on the **Agent → Test** tab.
2. **Publish** to push everything live all at once.
3. **Discard** to revert your draft and stay on the current published version.
## What's drafted
| Surface | Drafted? |
| ------------------------------------------------------------------ | -------- |
| **Train** — knowledge sources (URLs, files, pasted text) | Yes |
| **Personalization** — tone, length, custom answers, guidance rules | Yes |
| **Appearance** — colors, position, welcome message, layout, logos | Yes |
| **Configuration** — visibility, rate limits | Yes |
Things that are **not** drafted (changes apply immediately):
* API keys
* Privacy actions (DSAR, suppression)
* Team membership
* Allowed domains
## Publishing
Click **Publish** in the draft banner. A confirmation dialog shows you which sections are about to change:
* Knowledge sources added, re-crawled, or removed.
* Personalization fields edited.
* Appearance fields edited.
* Configuration fields edited.
Publish is **admin-only**. Non-admins see the banner but cannot publish. The action is logged with the actor, the timestamp, and a snapshot of what changed.
## What happens when you publish
1. Your drafted changes are checked for errors.
2. If everything looks good, your changes go live all at once — no partial updates ever reach your users.
3. New or updated knowledge sources become available to the Agent at the same moment.
4. Running Agent widgets pick up the new settings on their next refresh.
If something looks wrong with your draft, nothing changes. Your users keep seeing the previous version until you fix it.
## The Test tab
The **Agent → Test** tab is your safety net. It runs against your **draft** settings:
* Draft tone and custom answers (Personalization).
* Draft knowledge sources, including ones you haven't published yet.
* Draft Appearance and content.
A "Previewing draft" badge makes sure you never confuse it with what your real users are seeing.
Use it as the last step before every publish.
## What your users see
Your users only ever see published content. This means:
* A draft URL you just crawled — invisible to users until you publish.
* A custom answer you haven't approved — invisible to users until you publish.
* An appearance change you haven't shipped — invisible to users until you publish.
There's no way for draft content to reach your users without an explicit publish.
## Common workflows
1. **Agent → Train → Add source** → enter URL or upload file.
2. Wait for the source to finish indexing (status flips to `ready`).
3. Open **Agent → Test**, ask a question that should be covered.
4. Verify the answer is grounded in the new source.
5. Click **Publish** in the draft banner.
1. **Agent → Appearance → Content** → edit the welcome message.
2. Open **Agent → Test** and verify the new message renders.
3. Click **Publish** in the draft banner.
Click **Discard** in the draft banner to revert all unsaved changes back to the published version.
## Next steps
Find what to write next, ranked by user demand.
Manage your knowledge sources.