> 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/unlocking-a-user.md).
# Unlocking a user
## Unlocking a user
**Menu path:** `Administration -> System -> Users`
Unlocking restores the user's ability to log in, provided the account should work again in the backend or on POS. It can be done in two ways: directly from the users list or by editing the account and changing `Log-in available` to `Yes`.
### When to use
Use this procedure when an account has been locked and the user should receive system access again.
### Method 1: unlocking from the users list
This method is the fastest when you want to restore access without opening account details.
1. Open the `Users` screen.
2. In the `Filter` section, set `Status` to `Inactive`.
3. Click `FILTER`.
4. Select the user on the list.
5. Click `UNLOCK`.
6. In the message `Do you confirm user unlocking?`, click `Yes` to confirm unlocking or `Cancel` to stop the operation.
7. Check the user on the active users list.
### Method 2: unlocking by editing the user
This method is useful when, together with unlocking, you also want to check locations, roles, attributes or other account data.
1. Open the `Users` screen.
2. Search for the user. If the account is locked, set `Status` to `Inactive` in the filter.
3. Select the correct record.
4. Click `EDIT`.
5. In basic data, change `Log-in available` to `Yes`.
6. Click `SAVE`.
7. Check whether the user is visible on the active accounts list.
### What to watch out for
* Both methods lead to restoring the account's login availability.
* After unlocking, check whether the user has the correct role and location.
* If the user still cannot log in, check `Log-in available`, password, location and assigned roles.
* For service desk requests, confirm whether the issue concerned locking, password, location or permissions.
### Related pages
* [Locking a user](/aquila-store-user-manual/users-and-permissions/locking-a-user.md)
* [Editing a user](/aquila-store-user-manual/users-and-permissions/editing-a-user.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/unlocking-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.
