> 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/locking-a-user.md).
# Locking a user
## Locking a user
**Menu path:** `Administration -> System -> Users`
Locking a user removes the account's ability to log in. It can be done in two ways: directly from the users list or by editing the account and changing `Log-in available` to `No`.
### When to use
Use this procedure when the account should no longer be used, for example after a position change, end of cooperation, temporary access suspension or a security incident request.
### Method 1: locking from the users list
This method is the fastest when you want to lock an active account without opening user details.
1. Open the `Users` screen.
2. Search for an active user.
3. Select the correct record on the list.
4. Click `LOCK`.
5. In the message `Do you confirm user locking?`, click `Yes` to confirm the lock or `Cancel` to stop the operation.
6. After confirmation, the account is no longer available for login and is not visible on the active users list.
### Method 2: locking by editing the user
This method is useful when, together with locking, you also want to check or change other account data.
1. Open the `Users` screen.
2. Search for the user.
3. Select the correct record.
4. Click `EDIT`.
5. In basic data, change `Log-in available` to `No`.
6. Click `SAVE`.
7. Check whether the user is no longer available on the active accounts list.
### How to find a locked account
1. In the `Filter` section, set `Status` to `Inactive`.
2. Click `FILTER`.
3. Check the list of inactive users.
### What to watch out for
* Both methods lead to locking the account's login availability.
* Before locking, make sure the account is not needed for current operations.
* If the user should work again, unlock the account instead of creating a new one.
* For audit purposes, it is usually better to lock the account than to remove the history of links.
### Related pages
* [Unlocking a user](/aquila-store-user-manual/users-and-permissions/unlocking-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/locking-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.
