> 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/editing-a-role.md).
# Editing a role
## Editing a role
**Menu path:** `Administration -> System -> Roles`
Editing a role allows you to change its name, description and permission set. Changing a role affects all users who have that role assigned, so before saving it is worth making sure that the scope of the change is consistent with the expected process.
### When to use
Use this procedure when the scope of duties of users assigned to the role changes, when the role description needs to be clarified, or when a service desk request indicates a missing or too broad permission.
### Steps
1. Open the `Roles` screen.
2. On the roles list, select the role to change.
3. Click `EDIT`.
4. In the `General data` section, change the name or description if needed.
5. Go to the `List of rights` tab.
6. If needed, use `Search right` to find a permission by name or part of the name.
7. Select the correct permission on the list.
8. In `Status of entitlement`, set `Yes` or `No`.
9. Click `SAVE`.
### Searching for rights
On the `List of rights` tab, you can use `Search right`. Entering part of a name, for example `inv`, helps quickly find permissions related to a given area without manually going through the whole tree.
Permission names are descriptive and should indicate as clearly as possible which function they concern. If you still cannot find the expected permission, check whether you have the appropriate access scope to edit the given role or consult the change with an administrator.
### Important fields
| Field | Description |
| --------------------- | ---------------------------------------------------------------------------------- |
| Name | Role name later visible on the roles list and when assigning the role to a user. |
| Description | Role description, scope of duties or role purpose. |
| List of rights | Tab with a tree of categories and permissions. |
| Search right | Field for searching permissions by name or part of the name. |
| Status of entitlement | Setting that defines whether the role should have the selected permission. |
| Rights copying | Tab used to copy permissions from another role if you want to use it as a pattern. |
### What to watch out for
* Changing a role affects all users who have it assigned.
* Before making the change, make sure you understand the impact on production users.
* If you change only the role description, also save the change with `SAVE`.
* If the role is used as a pattern for other roles, first check whether the change will not affect the permission copying process.
* If you cannot see a permission or role, the reason may be missing permissions of the person performing the change.
### Related pages
* [Creating a role](/aquila-store-user-manual/users-and-permissions/creating-a-role.md)
* [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/editing-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.
