# Maintain a Company Bot

This guide is for Owners and Admins who run Company Bots. At the end you know how to see how a bot does, change it safely, undo a change, and switch it off.

## 1. See how a bot does

Select **Bots** in the Console sidebar. The list shows the status of each bot (Draft, Live, or Paused), when it was last used, and two badges:

- **Unpublished changes**: the draft differs from the live bot.
- **Failed runs**: a run of the bot failed in the last 24 hours.

Open a bot to see its **Overview**. It shows what the bot can reach, its settings, and **Metrics** for a period you choose: runs, success rate, failed runs, and sessions.

A run is one execution from a [trigger](/triggers). A session is one conversation.

## 2. Read sessions

Open a bot and select the **Sessions** tab. To see every bot, open **Bots**, then **Sessions**.

1. Filter by bot, time, source, and status.
2. Select a session to read its **Transcript**.

The source of a session is Chat, Preview (a test), Trigger, or API. Use sessions to find questions the bot answers badly, then fix the instructions or add knowledge.

You see the Company Bot sessions of everyone in the organization. Personal bot chats of other people stay hidden until you take access for 2 hours. See [Privacy](/privacy).

## 3. Change and republish

A change to the draft does not touch the live bot. People keep talking to the published version until you publish.

1. Open the bot and select **Edit**.
2. Change a section and select **Save**. Sections with changes that are not published show **Unpublished changes**.
3. Select **Test draft** and check the result. Test runs the saved draft.
4. Select **Publish**. Check the items in **Acknowledge capabilities** if the Console asks.

After you publish, chats that are already open use the new version from their next message.

Some settings apply when you save and need no publish: **Who can use this bot**, **In Chat**, the category, and tags.

## 4. Roll back

Every publish is kept. To go back to an earlier version:

1. Open the bot and select the **Changes** tab.
2. Under **Published states**, find the version and select **Copy into draft**.
3. The editor opens with that version as the draft. Check it, then select **Publish**.

Copying into the draft does not change the live bot. Only Publish does. Below the states, **Audit** lists who changed the bot and when.

## 5. Keep a Knowledge Base current

A Knowledge Base is a set of pages that bots read. Open **Knowledge**, then a Knowledge Base.

- **Pages**: read, edit, add (**New page**), move, or delete a page. Each change is one revision.
- **History**: see every revision. Select **Revert revision** to undo it, or restore a single page.
- **Agent**: a chat with the curator. Ask it to add, fix, or reorganize pages, for example "Find pages without a summary and add one."
- **Settings**: name, description, and the refresh interval. A running chat checks for changes after that time.

Knowledge changes are live at once. You do not publish the bot.

A bot with **Read & write** access to a Knowledge Base can update the pages itself. Then the knowledge grows from what people tell the bot. What one person says can reach everyone who uses the bot. Give write access only where that is fine.

## 6. Pause a bot

Pause a bot to take it out of use without deleting it. A paused bot is hidden in Chat, its triggers stop, and it does not answer in Slack or Teams.

- Open the bot and select **Pause** at the top of the editor.
- Or use the row action **Pause** in the Bots list.

Select **Resume** to bring it back. Pause and Resume do not publish anything.

## Next

- [Set up your organization](/guides/set-up-organization) covers members, groups, and Slack or Teams.
- [Knowledge](/knowledge) and [Skills](/skills) explain what a bot can read.
- [Triggers](/triggers) run a bot on a schedule.
- [Console](/console) lists the pages and roles.