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

# Settings

> Configure project overview, handover agents, notifications, security, API keys, and advanced options

**Settings** (page title **Project Settings**) configures how this project behaves: identity, handover agents, notification email, chat rate limits, API keys, and lifecycle actions.

In the project sidebar, under **Admin**, select **Settings**. Changing settings requires project edit access. Deleting the project needs delete access.

<Info>
  This is **project** settings. Organization name, billing, and phones live under [Organization setup](/docs/organization/setup). Chat agent prompt and channel tools are not configured here — use [Build](/docs/build) and [Deploy](/docs/deploy).
</Info>

## Open Settings

<Steps>
  <Step title="Open your project">
    Sign in and open the project.
  </Step>

  <Step title="Go to Settings">
    Under **Admin**, select **Settings**. Use the tabs: Overview, Handover Agents, Notifications, Security, API Keys, Advanced.
  </Step>
</Steps>

## Overview

Edit core project identity and locale:

* **Project Name** (required)
* **Description**
* **Domain** (industry category)
* **Language**
* **Timezone**

Save when your role allows updates.

## Handover Agents

Configure who can take over live conversations.

### Chat handover agents

Enable project team members as chat handover agents and set their availability schedule (days and hours) when the UI offers it. Only people already on [Team](/docs/admin/team) appear here.

### Voice handover agents

Add named voice handover agents, toggle them on or off, and optionally set a schedule (start/end time and days). Save handover agent settings before leaving the tab.

<Note>
  **Admin → Settings → Handover Agents** is configuration. Day-to-day queue work is in [Operate → Conversations](/docs/operate/conversations) (**My Handover**). Metrics are on [Operate → Handover](/docs/operate/handover).
</Note>

## Notifications

Set the **Notifications Email** — the address that receives project notifications and updates.

## Security

Configure **chat** rate limits to control request volume:

* **Project level** — requests per minute and per hour for the whole project
* **User / lead level** — requests per minute and per hour per user (lead)

Use these to protect capacity when traffic spikes. Values must be at least 1.

## API Keys

Create and manage project API keys for server-side Campaign API access.

<Steps>
  <Step title="Open API Keys">
    On **Admin → Settings**, open the **API Keys** tab.
  </Step>

  <Step title="Create a key">
    Select **Create API key**, name it, and choose the scopes your integration needs (for outbound calls, include Outbound calls / `calls:create`).
  </Step>

  <Step title="Store the secret">
    Copy the key when shown. Do not commit it to source control or expose it in client-side code.
  </Step>
</Steps>

Revoke keys you no longer need from the same tab. Full request auth details: [API authentication](/docs/api-reference/authentication).

## Advanced

### Project status

Activate or deactivate the project:

* **Active** — live and accessible across channels; messages are processed
* **Inactive** — deactivated; users cannot access it and messages are not processed

### Danger zone

**Delete Project** permanently removes the project and associated data (sources, leads, conversations, agent settings). This cannot be undone. Confirm carefully.

<Warning>
  Deleting a project is irreversible. Prefer deactivate if you only need to pause access.
</Warning>

## Related

* [Team](/docs/admin/team)
* [API authentication](/docs/api-reference/authentication)
* [Organization setup](/docs/organization/setup)