> For the complete documentation index, see [llms.txt](https://docs.tpi.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tpi.dev/guide/ac-user-management/users.md).
# Users
**Path: AC User Management > User**
In this section, you can find instructions on how to manage the users of the system, including creating, updating, deleting, and searching the users.
### Create Users
1. Click **Create** to access the user creation page.
2. Fill in the data or make selections as instructed below. The fields marked with “\*” are required.
* **Username**\***:** The account the user uses to log in to the system.
* **Display name**\***:** The name of the user using the system.
* **Password**\* **/ Confirm password**\***:** The password the user uses to log in to the system.
{% hint style="warning" %}
Password not limited to letters and numbers, up to 128 characters.
{% endhint %}
* **email**\***:** After the user is created, related information will be sent to the E-mail the user registered.
* **Organization:** Organization that the user belongs to.
* **Status**\***:** Determines whether the user can log in to the system.
{% hint style="warning" %}
If the status was not changed to *Active*, this account will not be able to log in to digiRunner.
{% endhint %}
* **Role****\*****:** Roles selected; it represents the system permissions that this account has access to.
{% hint style="info" %}
The highest level of permission is the system administrator, **ADMIN**.
{% endhint %}
3. Click on the icon next to **Organization** to display a tree diagram of organizations, and select the organization that the user belongs to.
4. Change the status to **Active**.
5. Click on the icon next to **Role** to display the list of roles, and select the roles that the user can have. You can also choose the roles from **Role Mapping**.
{% hint style="info" %}
If the wrong role was selected, click on the  icon to delete it.
{% endhint %}
6. After creating the user, the system will send a “*user account created*” email.
### Search Users
To search for user related information, Keyword Search can be used to search for user information, or click on the icon to search for roles and organizations.
### Update Users
1. Search for the user to modify, and click on theicon to access the **Update** page.
{% hint style="warning" %}
By default, when the account is entered incorrectly more than three times, the account is blocked by the system. To modify the number of password errors and change the user status to **Active**, go to **Client Management** > **API Client** >  > **Status**. You can also check **Reset password** under the **Password** tab to reset the user's password.
{% endhint %}
{% hint style="warning" %}
Those marked with “\*” are required to make changes.
{% endhint %}
2. If **Reset password** is selected, the system will send a change password email to the user; the user can log in to the system using the password included in the email and go to **My Profile** to change the password.
3. If the user has **Failed login attempts**, **Reset password attempts** can be selected, and the system will reset the failed login attempts of the user.
4. Modify the desired fields, and click **Update** to save and exit.
### Delete Users
If this user account is no longer used, it can be deleted from this page.
1. Search for the user account to delete, and click on the  icon to proceed.
2. Click **Delete** to delete the user and exit.
### View Users
Search for the user to view, and click on theicon to proceed.
{% hint style="info" %}
The information on the **Details** page is read-only.
{% endhint %}
---
# 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:
```
GET https://docs.tpi.dev/guide/ac-user-management/users.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.