> ## Documentation Index
> Fetch the complete documentation index at: https://chatbase.co/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# How Backstage approvals and auto mode work

> How Backstage asks for approval before changing your AI agent, what auto mode lets it change without asking, and how it tests a fix before publishing.

Backstage never changes your AI agent without your say-so. By default, every change it proposes appears on an approval card that you approve or reject, and with auto mode you can let it make changes in areas you choose without asking each time. When Backstage fixes a problem on its own initiative, it always tests the fix first and rolls it back if the fix fails.

## How approval works

Any change, such as updating instructions, adding a source, or deleting an Action, opens an approval card in the chat. You review each change and approve or reject it on its own before anything is applied.

* **Text changes**, such as instructions, show a side-by-side diff.
* **Settings changes**, such as the model or temperature, show a before and after table.

Approved changes to instructions, Actions, Procedures, and channel settings go into your [draft](https://chatbase.co/docs/user-guides/chatbot/versions.md), the same as changes you make in the dashboard. Customers keep talking to the live AI agent until the draft is published.

**Example**

> **You:** Make the tone friendlier, but keep answers short.
>
> **Backstage:** Drafts new instructions and shows the old and new text side by side, with **Approve** and **Reject** on the change.

On [Slack and iMessage](https://chatbase.co/docs/user-guides/chatbot/backstage/backstage-on-slack-and-imessage.md#approving-changes), you approve with buttons, reactions, or a reply such as "yes" or "reject".

## Auto mode

With auto mode on, Backstage can change your AI agent without asking you to approve each edit. Changes you ask for are made right away, and improvements Backstage proposes are tested before they're published.

### Turn on auto mode

**1. Open Backstage**

Open Backstage on any AI agent.

**2. Choose what Backstage may change**

Click the gear icon next to **Auto mode**, select the areas Backstage may change without asking, and click **Save**.

**3. Turn it on**

Turn on the **Auto mode** toggle.

Auto mode applies to the current chat only. Turn it off at any time with the toggle, or by telling Backstage in the chat.

### What auto mode changes

You choose which of these areas Backstage may change without asking:

* Instructions and model
* Appearance
* [Procedures](https://chatbase.co/docs/user-guides/chatbot/procedures/procedures-overview.md)
* [Widgets](https://chatbase.co/docs/developer-guides/widgets/overview.md)
* Added knowledge (text and Q\&A)

When you explicitly ask for a change in a selected area, Backstage makes it right away, without running tests. There's no approval card for each edit, and no re-approving when you tweak the same change again.

Anything outside the selected areas, such as editing Actions or deleting sources, still asks for your approval first.

> [!NOTE]
>
> Changes to instructions, appearance, Procedures, and Widgets still wait for you to publish. Added knowledge works differently: Backstage shows you a preview of the text or Q\&A and asks you to confirm, and once you confirm it's added to your Data Sources, with no publish step.

Auto mode doesn't change billing. It only decides which changes need an approval card. See [Backstage limits and credits](https://chatbase.co/docs/user-guides/chatbot/backstage/limits-and-credits.md).

## How Backstage fixes a problem

When Backstage sees your AI agent answering wrong, whether in conversations, a knowledge gap, or a failed [test](https://chatbase.co/docs/user-guides/chatbot/tests.md), it proposes an improvement. Unlike changes you ask for, improvements are always tested before they go live. Once you approve the improvement, Backstage:

**1. Measures the problem**

Runs test conversations against the live AI agent to measure the problem.

**2. Makes the change in its own draft**

Applies the fix in a separate draft. Your draft and the live AI agent stay untouched.

**3. Tests the change**

Runs the same tests on the changed AI agent.

**4. Publishes or rolls back**

If the change passes without making your saved tests worse, Backstage publishes a new version. If it fails, Backstage rolls it back and tries again, up to **3 times**, then tells you what it tried.

You can watch the tests run in the chat and cancel at any time.

> [!NOTE]
>
> While an improvement is running, **Publish** and **Restore** are paused on the dashboard, so two changes never collide.

The test conversations use your monthly [test credits](https://chatbase.co/docs/user-guides/chatbot/tests.md#test-credits) first, then message credits. Each published improvement is a normal [version](https://chatbase.co/docs/user-guides/chatbot/versions.md#version-history), so you can restore the previous one if you change your mind.

### Changes you ask for versus improvements

| | Changes you ask for | Improvements Backstage proposes |
| - | - | - |
| Tested before going live | No | Always |
| Approval (auto mode off) | One card per change | Once, before the tests start |
| With auto mode on, in a selected area | Made right away, no card | Still tested before publishing |
| Where the change goes | Your draft | A separate draft, published as a new version if it passes |

## Auto mode on Slack

Auto mode works the same way from [Slack](https://chatbase.co/docs/user-guides/chatbot/backstage/backstage-on-slack-and-imessage.md#connect-slack). Approvals and results arrive in the thread, and replying **"stop"** cancels a running improvement.

## Frequently asked questions

> [accordion] Can Backstage change my AI agent without asking?
>
> Only in the areas you select for auto mode, and only in the chat where auto mode is on. Everything else, such as editing Actions or deleting sources, shows an approval card first.

> [accordion] Does auto mode publish my changes?
>
> Changes to instructions, appearance, Procedures, and Widgets still wait for you to publish. Knowledge Backstage adds is previewed, then added once you confirm, with no publish step. Improvements Backstage proposes are published as a new version only after they pass their tests.

> [accordion] Can I approve some changes and reject others?
>
> Yes. Each change on an approval card has its own approve and reject controls, so you can keep one and drop another.

> [accordion] What if an improvement makes things worse?
>
> Backstage publishes an improvement only if it passes without making your saved tests worse. If it fails, Backstage rolls it back and tries again, up to 3 times, then tells you what it tried. You can also cancel at any time.

> [accordion] Does auto mode cost more?
>
> No. Auto mode only decides which changes need approval. Tests Backstage runs use test credits first, with or without auto mode.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.