> For the complete documentation index, see [llms.txt](https://docs.voiceb.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.voiceb.ai/help-center/getting-set-up/setting-permissions.md).

# Setting permissions

* Assign **Admin** access only to users who need to build or modify agent flows, SIP Trunk settings, or Tools
* Use the **Member** role for marketing, operations, or sales teams who need to track performance and handle leads
* You can change a user's role at any time from the **Organization → Members** section

<div data-with-frame="true"><figure><img src="/files/FA5cuV5CP5xw68TA7dgx" alt=""><figcaption></figcaption></figure></div>

## Setting permissions

{% hint style="info" %}
**VoiceB tip:** Keep your AI agent secure — grant Admin rights only to users directly responsible for configuration and script maintenance.
{% endhint %}

#### 👥 Permission Levels

| **Role**   | **Capabilities**                                                                                                                                                                                                                                    |
| ---------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Admin**  | Full access: configure agents in **Agent Studio**, edit scripts and objections, manage **SIP Trunk** configuration and **Tools**, manage integrations, and manage users — including inviting new users and changing roles between Member and Admin. |
| **Member** | Limited access: view analytics, monitor call outcomes, listen to recordings, and access collected lead data — but cannot edit or configure agents.                                                                                                  |

***

#### 🛠️ What Admins can access

Admins have exclusive access to the platform's configuration areas:

* [**Agent Studio**](https://docs.voiceb.ai/how-to-update-a-voiceb-agent-prompt-and-script) — create and configure agents, edit scripts, objections, and script blocks
* [**SIP Trunk configuration**](https://docs.voiceb.ai/sip-trunk-private-call-routing-for-enterprise-voice-ai) — connect and manage your dedicated enterprise call routing
* **Tools** — configure the tools your agents can call during conversations
* **User management** — invite additional users and change any user's role from Member to Admin (or back)

{% hint style="info" %}
Only Admins can promote a Member to Admin. Grant this role deliberately, since Admins can modify live agent configuration.
{% endhint %}

***

#### 🔐 Best Practices

* Assign **Admin** access only to users who need to build or modify agent flows, SIP Trunk settings, or Tools
* Use the **Member** role for marketing, operations, or sales teams who need to track performance and handle leads
* You can change a user's role at any time from the **Organization → Members** section


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.voiceb.ai/help-center/getting-set-up/setting-permissions.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.