> 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/copying-rights-from-another-role.md).
# Copying rights from another role
## Copying rights from another role
**Menu path:** `Administration -> System -> Roles`
Copying permissions allows you to use an existing role as a pattern for a new or edited role. It is useful when a new role should be similar to an existing one, but later requires adjustment of selected permissions.
### When to use
Use this function when you want to speed up role configuration and start from a ready permission set, for example the `Cashier`, `Shop Manager` or `Treasury` role.
### Steps
1. Open a role in add or edit mode.
2. Go to the `Rights copying` tab.
3. In `Pattern of rights`, select the existing role whose permissions should be used as a pattern.
4. Click `COPY`.
5. After copying, go to the `List of rights` tab.
6. Check and adjust the permission settings.
7. Click `SAVE`.
### What copying does
Copying transfers the permission set from the selected pattern role to the role currently being created or edited. This does not mean that the role is ready for use without review. After copying, always check the `List of rights` tab and make sure the role has not received permissions that are too broad or too narrow.
### What to watch out for
* Copying permissions does not replace administrator verification.
* Do not copy roles with broader permissions if the new role should have a limited scope.
* The list of roles available in `Pattern of rights` may depend on the permissions of the person performing the change.
* If the expected pattern role is not visible, check the permissions of the person performing the change or consult the configuration with an administrator.
### Related pages
* [Creating a role](/aquila-store-user-manual/users-and-permissions/creating-a-role.md)
* [Editing a role](/aquila-store-user-manual/users-and-permissions/editing-a-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/copying-rights-from-another-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.
