> For the complete documentation index, see [llms.txt](https://docs.aohwv.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aohwv.dev/administration/user-management.md).

# User Management

Manage the users who have access to AOH Sync, control their lock status, assign them to permission groups, and administer API keys.

![The User Management screen showing the Users tab with an Application Users table. Columns include Name, Email, Group, Additional Roles, Status, Joined date, and Actions. Summary cards at the bottom show Total App Users (1, with 1 active and 0 locked) and Active API Keys (0, none expiring soon).](/files/NcaruxCSzZKzWHsbGX6j)

*The User Management screen. Users are automatically registered on first login. The summary cards at the bottom show totals at a glance.*

## What you can do here

| Action             | What it does                                                                      |
| ------------------ | --------------------------------------------------------------------------------- |
| **Users** tab      | View all users who have logged in, their group assignments, status, and join date |
| **Groups** tab     | View and manage the permission groups available in your organization              |
| **API Keys** tab   | Create and manage API keys for programmatic access to AOH Sync                    |
| **Audit Logs** tab | Browse a log of user-level administrative actions                                 |
| **Recovery** tab   | Access recovery options for locked or inaccessible accounts                       |
| **Edit Group**     | Change the permission group a user belongs to                                     |
| **Lock / Unlock**  | Immediately suspend or restore a user's access to AOH Sync                        |
| **Refresh**        | Reload the user list to reflect recent logins or changes                          |

## Application Users

Users are automatically registered the first time they log in with their organization credentials. You do not need to manually provision users — AOH Sync creates their record on first login.

Each user row shows:

* **Name** and **Email** — the identity used to log in
* **Group** — the permission group currently assigned to the user
* **Additional Roles** — any roles granted outside the group assignment
* **Status** — **Active** (green) or locked
* **Joined** — the date of first login

## How to use it

{% stepper %}
{% step %}
**Find the user**

Open the **Users** tab. Use the table to locate the user by name or email. Click **Refresh** if you expect a recently logged-in user to appear.
{% endstep %}

{% step %}
**Assign or change the user's group**

Click **Edit Group** in the user's row. Select the appropriate permission group and save. The user's effective permissions update immediately.
{% endstep %}

{% step %}
**Lock a user if needed**

Click **Lock** in the user's row to immediately revoke their access. A locked user cannot log in until you unlock them. Click the same button (shown as **Unlock** when locked) to restore access.
{% endstep %}
{% endstepper %}

## Related

* [Access Management](/administration/access-management.md) — define and manage permission groups
* [Roles & Permissions](/core-concepts/roles-and-permissions.md) — understand how groups and roles work
* [Audit & Status Logs](/administration/audit-and-status-logs.md) — review activity across your organization


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.aohwv.dev/administration/user-management.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.