> 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.md).

# Users and permissions

## Users and permissions

This chapter describes working with user accounts, roles and permissions in the Aquila Flex backend. It is intended for administrators, service desk teams and selected operational roles, for example a `Shop manager`, if they have been granted permissions to manage users in a given implementation. Changes made in this area affect the ability to log in, function visibility and the scope of operations available to users. This chapter describes two main areas:

* `Administration -> System -> Users` - managing user accounts,
* `Administration -> System -> Roles` - managing roles and permissions.

### What this chapter contains

| Page                             | Purpose                                                         |
| -------------------------------- | --------------------------------------------------------------- |
| Module overview                  | Which functions are included in the users and permissions area. |
| Searching for users              | How to find a user on the list.                                 |
| Adding a user                    | How to create a new account.                                    |
| Editing a user                   | How to change data for an existing account.                     |
| Locking a user                   | How to deactivate an account.                                   |
| Unlocking a user                 | How to restore an account to work.                              |
| Creating a role                  | How to create a new role and grant permissions.                 |
| Editing a role                   | How to change the description or permissions of a role.         |
| Copying rights from another role | How to use an existing role as a template.                      |
| Deleting a role                  | How to delete a role if it has not been used.                   |

{% hint style="warning" %}
Changes in roles and permissions may affect user access to functions, documents, reports and operations. Before changing a role or permissions, make sure you understand the required access scope.
{% endhint %}


---

# 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.md?ask=<question>&goal=<user_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.