> 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-user.md).
# Editing a user
## Editing a user
**Menu path:** `Administration -> System -> Users`
Editing a user allows you to change account data, login availability, assigned locations, roles and attributes. These changes may affect which data and functions the user can access in the backend.
### When to use
Use this procedure when the user's scope of duties, work location, descriptive data, login status or information required by operational processes changes, for example cashier number or tax identifier.
### Steps
1. Open `Administration -> System -> Users`.
2. Search for the user on the list.
3. Select the correct record.
4. Click `EDIT`.
5. Change data in the appropriate form sections.
6. Check the `Locations`, `Roles` and `Attributes` tabs if the request concerns user access or user data.
7. Click `SAVE`.
8. Search for the user again and check whether the change has been saved.
### Basic and advanced data
In basic data, you can check the login, login availability, forced password change and system information about user activity. Forced password change applies to backend login, not POS login. For service desk requests, it is especially worth checking:
* whether the user has `Log-in available` set,
* whether a password change has been forced for backend login,
* when the last activity occurred,
* whether the last failed login was recorded.
Advanced data is used to store descriptive information, for example first name and surname. Its scope may depend on the client's configuration.
### Locations tab
On the `Locations` tab, you can add or remove locations available to the user. If the user cannot see data for a given location or cannot switch to the correct location, this tab is one of the first places to check. Location defines where the user can work, but it does not grant separate permissions for that location.
### Roles tab
On the `Roles` tab, you can assign one or many roles to the user. Roles define the scope of functions, operations and data available to the account. Roles apply to the account as a whole. It is not possible to assign a role separately for each location on one account, for example `Shop manager` for one location and `Cashier` for another. If a user has multiple roles, the system treats them as a set of permissions assigned to the account. Access to editing and assigning roles may depend on the permission hierarchy. The user performing the change may not see all roles in the system. For example, a `Shop manager` should not be able to assign an administrator role to a user if they do not have the appropriate permissions themselves. If the expected role is not visible, check the permissions of the person performing the change or forward the request to an administrator.
### Attributes tab
On the `Attributes` tab, you can complete additional user data if it is required in the given implementation. Attributes are defined by the Aquila team based on the client's needs.
For example, if a cashier's tax identifier must appear on a receipt in a given country, an administrator or authorised user can complete the appropriate attribute on the cashier account.
### Change history tab
The `Change history` tab allows you to check the history of changes made to the user account. It is useful when analysing requests where it is necessary to determine when roles, password, locations or other account data were changed.
### What to watch out for
* Changing a role may change the scope of functions available to the user.
* The list of roles available for assignment may be limited by the permissions of the person editing the account.
* Changing locations affects the available data context, but does not create a separate role for that location.
* For backend login issue requests, check login availability, forced password change and account status.
* When changing attributes, make sure their meaning is consistent with the implementation configuration.
### Related pages
* [Searching for users](/aquila-store-user-manual/users-and-permissions/searching-for-users.md)
* [Adding a user](/aquila-store-user-manual/users-and-permissions/adding-a-user.md)
* [Creating a role](/aquila-store-user-manual/users-and-permissions/creating-a-role.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-user.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.
