> 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/how-to-grant-account-permissions.md).
# How to Grant Account Permissions
This document explains how to grant account permissions by creating an account-level role and selecting the required permissions.
Account permissions are granted through roles. Create an **Account** role, select the permissions you need, and then assign the role to users.
### Create role
{% columns %}
{% column %}
1. Open Roles in the Admin panel.
2. Click the button.
3. Fill in the role details and select permissions.
4. Click the button to save changes.
To review the full list of permissions, see [Account Permissions](/user/user-access-and-permissions/account-permissions.md)
{% hint style="info" %}
Account invitations are sent using the account **Email notifications language**. For example, if the account language is Dutch, invited users receive the invitation email in Dutch.
{% endhint %}
{% endcolumn %}
{% column %}
{% endcolumn %}
{% endcolumns %}
### Role editor fields
1. **Name —** Enter a role name.
2. **Account/Mailbox —** Switch between account-level and mailbox-level roles.
3. **Description** — Add a short note to explain the role.
4. **Filters —** Use **View all** or **View only selected** to control the permissions list.
5. **Select all permissions —** Checkbox that allows you to select all permissions across all groups.
6. **Action buttons**:
* Click the button to save changes.
* Click the button to close the editor without saving.
* Click the button to delete the role.
---
# 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/how-to-grant-account-permissions.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 to save changes.
* Click the 
button to close the editor without saving.
* Click the 
button to delete the role.
---
# 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/how-to-grant-account-permissions.md?ask=