> For the complete documentation index, see [llms.txt](https://docs.aquiladynamics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aquiladynamics.com/aquila-store-user-manual/users-and-permissions/creating-a-role.md).
# Creating a role
## Creating a role
**Menu path:** `Administration -> System -> Roles`
A role defines a set of permissions that can be assigned to a user. A new role can be created from scratch or by copying permissions from an existing role.
### When to use
Use this procedure when a new access scope is needed, for example for a new position, team or process.
### Steps
1. Open `Administration -> System -> Roles`.
2. Click `ADD`.
3. In the `General data` section, enter the role name.
4. Enter the description or scope of duties.
5. Save the basic data.
6. Go to the `List of rights` tab.
7. If needed, use `Search right` to find a permission by name or part of the name.
8. Select a category and a specific permission.
9. In `Status of entitlement`, select whether the role should have the permission.
10. Save the changes.
### Searching for rights
On the `List of rights` tab, you can use `Search right` to find the correct permission faster. Enter a name or part of a name, for example `inv`, and the system narrows the list to matching items.
Permission names are descriptive and should indicate as clearly as possible which function they concern. Thanks to this, it is usually not necessary to know the full structure of the permission tree to find the right item.
### Important fields
| Field | Description |
| --------------------- | ------------------------------------------------------------ |
| Name | Role name later visible as a permission template. |
| Description | Role description, scope of duties or role purpose. |
| List of rights | Tree of categories and permissions available in the system. |
| Search right | Field for searching permissions by name or part of the name. |
| Status of entitlement | `Yes` or `No` setting for the selected permission. |
### What to watch out for
* Do not use overly generic role names if roles have different access scopes.
* After creating a role, test it on a test or control user if such a process exists.
* Grant only the permissions needed for the work of a given user group.
### Related pages
* [Copying rights from another role](/aquila-store-user-manual/users-and-permissions/copying-rights-from-another-role.md)
* [Adding a user](/aquila-store-user-manual/users-and-permissions/adding-a-user.md)
---
# 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://docs.aquiladynamics.com/aquila-store-user-manual/users-and-permissions/creating-a-role.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.
