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

# Workspace Settings

> Manage workspace members, API keys, telephony, and app integrations.

Workspace settings control team access, API access, and integrations that affect the whole Ringg AI workspace.

***

## Workspace Members

Use **Workspace Members** to invite teammates and control what they can change.

### View Members

1. Click **Workspace Members** in the left sidebar under **More**.
2. Review the member list.

The table shows each member's name, email, permission level, owner status, and invitation status.

### Invite a Member

1. Click **Invite Member**.
2. Enter the teammate's email address.
3. Choose the permission level.
4. Send the invitation.

### Permission Levels

| Permission      | Use It For                                                                 |
| --------------- | -------------------------------------------------------------------------- |
| **View & Edit** | Teammates who create or update assistants, campaigns, numbers, or settings |
| **View Only**   | Teammates who only need to review history, analytics, or configuration     |

### Remove a Member

1. Find the member in the table.
2. Click **Remove User**.
3. Confirm the removal.

<Note>
  You cannot remove the workspace owner from the workspace. Transfer ownership first if ownership needs to change.
</Note>

***

## API Key

Use **API Key** when engineers need to connect Ringg AI to your product, CRM, website, or data systems.

### Copy the API Key

1. Click **API Key** in the left sidebar.
2. Click the eye icon only if you need to reveal the key.
3. Click the copy icon to copy it.
4. Send it to the developer through your company's approved secret-sharing process.

The API key is sent as the `X-API-KEY` header in Ringg AI API requests.

```http theme={null}
X-API-KEY: $RINGG_API_KEY
```

<Warning>
  Treat the API key as a secret. Do not paste it into public tickets, docs, chat channels, frontend code, screenshots, or emails.
</Warning>

### Regenerate the API Key

Click **Regenerate** only when you intentionally want to rotate the key.

Regenerating immediately invalidates the old key. Coordinate with developers before rotating so existing integrations do not break.

### Open API Docs

Click **Docs** to open the Ringg AI API reference.

***

## Integrations

Click **Integrations** in the left sidebar.

Integrations connect Ringg AI to telephony providers and workflow tools.

***

## Your Telephony

Use **Your Telephony** when your company wants to use its own provider numbers.

1. Open **Integrations**.
2. Click the **Your Telephony** tab.
3. Click **Add New**.
4. Choose the provider, such as Twilio, Exotel, or Plivo.
5. Enter the provider credentials.
6. Click **Save**.
7. Open **Numbers** and confirm the provider numbers appear.

<Note>
  If you do not connect a custom telephony provider, Ringg AI uses the default Ringg AI telephony setup.
</Note>

***

## Zapier

Use **Zapier** when business users want to connect Ringg AI to other apps without a custom backend.

Common examples:

<CardGroup cols={2}>
  <Card title="Google Sheets to Ringg AI" icon="table">
    Start a Ringg AI action when a new row appears in a sheet.
  </Card>

  <Card title="Shopify to Ringg AI" icon="shopping-cart">
    Start customer calls for new orders or delivery updates.
  </Card>
</CardGroup>

To connect:

1. Open **Integrations**.
2. Go to **Zapier**.
3. Click **Sign up** or **Log in**.
4. Choose Ringg AI and the app you want to connect.
5. Follow Zapier's setup steps.

<Tip>
  Zapier may ask for the Ringg AI API key. Use the same secret-handling rules as any backend integration.
</Tip>

***

## Webhook Setup Handoff

Webhooks send call results to another system automatically. Business users usually decide what should happen; developers usually configure the endpoint.

Give developers:

| Item                          | Why They Need It                                                                 |
| ----------------------------- | -------------------------------------------------------------------------------- |
| Business goal                 | Example: send completed call results to CRM                                      |
| Assistant name and `agent_id` | Webhook subscriptions are configured for an assistant                            |
| Events needed                 | Examples: call status, recording, transcript, analysis, all processing completed |
| Destination system            | CRM, support tool, data warehouse, Google Sheets, or another backend             |
| Receiver URL owner            | The team that owns the webhook endpoint                                          |
| API key                       | Needed to configure the subscription through the API                             |

Developers can follow [Webhook setup](/webhooks/initial-setup).

***

## Developer Handoff

For workspace-level setup, send developers:

| Item                               | Use                                                           |
| ---------------------------------- | ------------------------------------------------------------- |
| Workspace API key                  | Server-side API authentication                                |
| Telephony provider                 | Confirms whether calls use Ringg AI telephony or BYOT         |
| Workspace members with edit access | Confirms who can change production settings                   |
| Number list                        | Helps map caller IDs to campaigns and products                |
| Webhook requirements               | Defines what post-call data should be delivered automatically |

Ask developers to store the API key in a secret manager and to tell you before they regenerate or rotate it.