> 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/deleting-a-role.md).
# Deleting a role
## Deleting a role
**Menu path:** `Administration -> System -> Roles`
A role can be deleted only when it is no longer needed and is not used in the system. Before deleting it, make sure the role is not assigned to users and does not act as a pattern for other configurations.
### When to use
Use this procedure when a role was created incorrectly, is a duplicate or is no longer needed in the organization's process.
### Steps
1. Open the `Roles` screen.
2. Select the role on the list.
3. Click `DELETE`.
4. In the message `Do you want to delete selected role?`, click `Yes` to confirm deletion or `Cancel` to stop the operation.
5. Check whether the role is no longer visible on the list.
### What to watch out for
* Do not delete a role if it is assigned to users.
* Do not delete a role if it is used as a pattern for copying permissions.
* If in doubt, first check users who use the role.
* If the role should no longer be used, but there is a risk of dependencies, it is safer to first remove it from users and verify the process with an administrator.
* Deletion requires confirmation of a system message.
### Related pages
* [Editing a role](/aquila-store-user-manual/users-and-permissions/editing-a-role.md)
* [Copying rights from another role](/aquila-store-user-manual/users-and-permissions/copying-rights-from-another-role.md)
* [Searching for users](/aquila-store-user-manual/users-and-permissions/searching-for-users.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/deleting-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.
