> For the complete documentation index, see [llms.txt](https://support.docstudio.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.docstudio.com/admin-panel/users-and-user-roles/role-management.md).
# Role Management
This guide explains how to manage roles in the system, including how to create, edit, and configure roles and their permissions.
Use the **Roles** page to manage corporate user roles and their permissions.
Roles exist on two levels:
1. **Account**
2. **Mailbox**
### Roles page
Use the **Roles** page to browse roles, search by name, and filter by permissions.
### System roles
The system includes default roles that cannot be deleted:
{% columns %}
{% column %}
* **Account Owner** (account permissions)
* **Mailbox Owner** (mailbox permissions)
{% endcolumn %}
{% column %}
{% endcolumn %}
{% endcolumns %}
{% hint style="info" %}
A corporate account administrator manages the company account in the **Admin panel**. **Corporate Account Admin** — is a user who has access to the company's account, in which a verified and active domain is registered.
{% endhint %}
### Create role
1. Open the **Roles** page.
2. Click the button.
The role editor opens.
Use **Back to Roles** to return to the roles list.
3. In **Role information**, set:
* **Name**
* **Description** (optional)
* **Role level**
The role level affects the permissions list in **Role permissions**.
4. In **Role permissions**, select the permissions to include in the role.
* account permissions — [Account Permissions](/user/user-access-and-permissions/account-permissions.md)
* mailbox permissions — [Mailbox Permissions](/user/user-access-and-permissions/mailbox-permissions.md)
5. Use permission groups to expand or collapse the list.
6. Click **View all** to expand or collapse all groups.\
— Optional: Enable **Select all permissions** to select all permissions across all groups\
— Optional: Click **View only selected** to show only the selected permissions.
7. Click the button.
The role appears in the roles list.
In **Permissions**, click to see all permissions assigned to the user.
### Edit a role
{% hint style="info" %}
System roles cannot be edited.
{% endhint %}
1. In the roles list, click the **Settings** icon next to the role.
2. Update role details and permissions.
3. Click the button.
You cannot change the role level when editing.
To delete a role, click the button, then confirm the action.
### Copy a role
1. In the roles list, click the **Copy** icon for the role.
2. A new role is created with the same level and permissions.
3. Set a role name and update permissions as needed.
4. Click the button.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://support.docstudio.com/admin-panel/users-and-user-roles/role-management.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
button.
The role editor opens.
Use **Back to Roles** to return to the roles list.
3. In **Role information**, set:
* **Name**
* **Description** (optional)
* **Role level**
The role level affects the permissions list in **Role permissions**.
4. In **Role permissions**, select the permissions to include in the role.
* account permissions — [Account Permissions](/user/user-access-and-permissions/account-permissions.md)
* mailbox permissions — [Mailbox Permissions](/user/user-access-and-permissions/mailbox-permissions.md)
5. Use permission groups to expand or collapse the list.
6. Click **View all** to expand or collapse all groups.\
— Optional: Enable **Select all permissions** to select all permissions across all groups\
— Optional: Click **View only selected** to show only the selected permissions.
7. Click the 
button.
The role appears in the roles list.
In **Permissions**, click 
to see all permissions assigned to the user.
### Edit a role
{% hint style="info" %}
System roles cannot be edited.
{% endhint %}
1. In the roles list, click the **Settings** 
icon next to the role.
2. Update role details and permissions.
3. Click the 
button.
You cannot change the role level when editing.
To delete a role, click the 
button, then confirm the action.
### Copy a role
1. In the roles list, click the **Copy** 
icon for the role.
2. A new role is created with the same level and permissions.
3. Set a role name and update permissions as needed.
4. Click the