> 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/searching-for-users.md).
# Searching for users
## Searching for users
**Menu path:** `Administration -> System -> Users`
The `Users` screen consists of the `Filter` section and the `Data` section, where the user list or search results are displayed.
### When to use
Use this procedure when you want to find a user before editing, locking, unlocking or checking the assigned role.
### Steps
1. Open `Administration -> System -> Users`.
2. In the `Filter` section, complete the selected criteria.
3. Click `FILTER`.
4. Check the results in the `Data` section.
5. Select the correct user if you want to perform another operation.
### Available criteria
| Field | Description |
| ----------------- | ----------------------------------------------------------------------------------------- |
| Shop | User location. The value can be selected from a list or through the location list screen. |
| Second name | User surname or part of the surname. |
| Pattern of rights | Role assigned to the user. The list is created based on roles. |
| Status | User status, for example `Active` or `Inactive`. |
### What to watch out for
* Locked users are not visible on the active users list.
* To find a locked account, set status to `Inactive`.
* If a user cannot see a function, check their role, location and login availability.
### Related pages
* [Editing a user](/aquila-store-user-manual/users-and-permissions/editing-a-user.md)
* [Locking a user](/aquila-store-user-manual/users-and-permissions/locking-a-user.md)
* [Unlocking a user](/aquila-store-user-manual/users-and-permissions/unlocking-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/searching-for-users.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.
