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

# Roles and permissions

> What each organization role can do, and how roles apply to API keys and SSO.

A member's role decides what they can do in the dashboard, and what a full-access API key they create can do.

## Roles

| Role | What it's for |
| - | - |
| Owner | Usually the person who created the organization. Can do everything an admin can, and is the only one who can delete the organization. |
| Admin | Runs the organization: members, billing, API keys and settings, plus everything an operator can do. |
| Operator | Builds and ships agents, and manages secrets, analytics dashboards, exports and credits. |
| Prompter | Builds and tests agents, but can't ship them or change what live calls use. Can't manage secrets, analytics dashboards, exports or credits. |
| Viewer | Sees agents and conversations. Can't change anything. |

## What each role can do

| Action | Owner | Admin | Operator | Prompter | Viewer |
| - | :-: | :-: | :-: | :-: | :-: |
| See agents and conversations | Yes | Yes | Yes | Yes | Yes |
| Create and edit agents, and set development variables | Yes | Yes | Yes | Yes | No |
| Publish, promote and roll back agents | Yes | Yes | Yes | No | No |
| Run experiments and staged rollouts | Yes | Yes | Yes | No | No |
| Delete agents | Yes | Yes | Yes | No | No |
| Attach phone numbers and widgets to agents | Yes | Yes | Yes | No | No |
| Set staging and production variables | Yes | Yes | Yes | No | No |
| Edit disposition drafts | Yes | Yes | Yes | Yes | No |
| Publish, roll back, disable and delete dispositions | Yes | Yes | Yes | No | No |
| Create, edit and delete tools | Yes | Yes | Yes | No | No |
| Add, edit and delete knowledge sources | Yes | Yes | Yes | No | No |
| Write judges and run evaluations | Yes | Yes | Yes | Yes | No |
| Buy phone numbers, send calls and send messages | Yes | Yes | Yes | Yes | No |
| Manage secrets in **Tools > Secrets** | Yes | Yes | Yes | No | No |
| Add charts to analytics dashboards | Yes | Yes | Yes | No | No |
| Export conversations | Yes | Yes | Yes | No | No |
| Buy credits | Yes | Yes | Yes | No | No |
| Manage members, roles and organization settings | Yes | Yes | No | No | No |
| Manage API keys | Yes | Yes | No | No | No |
| Change plans | Yes | Yes | No | No | No |
| Delete the organization | Yes | No | No | No | No |

In **Settings**, only owners and admins see the organization pages, such as **Users**, **Billing** and **API keys**. Other roles see their own account settings.

## Assign roles

Owners and admins add members and change their roles in **Settings > Users**. Through the API, use [Update Organization Members](https://docs.bland.ai/api-v1/patch/org_members.md) to add or remove a member, and [Update Organization Member Permissions](https://docs.bland.ai/api-v1/patch/org_member_permissions.md) to change a role.

* **Default role.** New members start with the organization's default member role unless you pick one when you add them. It's Viewer until an owner or admin changes it under **Settings**, or sets `preferences.default_member_role` with [Update Organization Properties](https://docs.bland.ai/api-v1/patch/org_properties.md). That call replaces the whole `preferences` object, so include the preferences you want to keep. It can be any role except owner.
* **More than one role.** The dashboard gives each member one role. Through the API, a member can hold several, and can do anything any of their roles allows.
* **SSO members.** If you use SSO, a member's groups can replace the role you set. See [Roles and SSO](#roles-and-sso).

### The owner

Each organization has one owner, usually the person who created it. The owner can't be changed or removed in the dashboard or through the API, and can't leave the organization. To transfer ownership, contact support. The previous owner becomes an admin.

## Roles and API keys

A full-access API key acts as the member who created it. Most endpoints that are limited by role check that member's current role. Only owners and admins can create keys, so a full-access key usually has admin access.

* If the member's role changes, their full-access keys change with it.
* If the member is removed from the organization, their full-access keys are deleted.
* A few role limits apply only in the dashboard, so a full-access key isn't held to them. For example, a full-access key can send calls whatever its creator's role.

[Restricted keys](https://docs.bland.ai/api-v1/post/keys-create.md#restricted-keys) and [OAuth clients](https://docs.bland.ai/api-v1/oauth-client-credentials.md) don't use roles. Their permissions decide what they can reach, and they keep working when the member who created them changes role or leaves.

## Roles and SSO

With [SSO](https://docs.bland.ai/enterprise-features/SSO.md), Bland can set each member's role from their groups in your identity provider. Groups can map to admin, operator, prompter or viewer, never owner.

Bland checks a member's groups each time they sign in with SSO:

* If one of their groups maps to a role, Bland sets that role, replacing any role set in the dashboard or through the API.
* If none of their groups maps to a role, an existing member keeps their role, and a new member gets the default member role.

***

Docs for agents: [llms.txt](https://docs.bland.ai/llms.txt)


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