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

# User Management

The User Management menu functions to display and manage the list of users connected to a specific branch.\
Admins can view the list of active users under that branch, along with important information such as username, email, phone number, role, and account status.

Important Note: This feature only displays users mapped to one branch. Users from other branches will not appear in this list.

### A. Main User Management Page

<figure><img src="/files/a76dc1e8c3e951c217bc671710ba42dce0719f25" alt=""><figcaption><p>Figure 1 Main User Management Page</p></figcaption></figure>

**Explanation of Each Column in the Table:**

1. User ID: Shows each user's unique identity in the system.\
   Example: 102725.
2. Username: Displays the username used to log in to the system.\
   Example: client.test
3. Email: The email address registered for the account. The email is used for notification and password reset purposes.\
   Example: nurulhud9630…@domain.com.
4. Phone Number: The phone number registered to the user account. This number can be used for verification or internal communication.\
   Example: 628158597221
5. Account Type: Shows the user's account category.&#x20;
   1. In this example, all users have the Client type because they are registered as part of the corporate client branch.
6. Reference: Displays the name of the branch or entity where the user is registered.\
   Example: BOOKING API TEST CORPORATE CGK.
7. Role: Explains the user's access level and responsibilities within the system.\
   Example: Admin Client Branch → means the user has access rights to manage data at the branch level.
8. Account Status: Indicates whether the user's account is active or inactive.
   1. Active: The user can log in and access the system.
   2. Inactive: The user's access is restricted or has been deactivated by an admin
9. "Create User" Button: The red button in the upper-right corner is used to add a new user to the same branch.

### B. System Operation and Limitations:

1. Displayed Data:
   1. Only users mapped to the active branch will appear in the table.
   2. The system does not display cross-branch users to maintain data security between branches.
2. Search and Filter:
   1. Use the Search field at the top to find users by username or user ID.
   2. Use the Filter to narrow down users by status or specific role.
3. Access Rights Management:
   1. Admins can only view and manage users within their own branch.
   2. Adding and deleting users is done through the Create User button or each account's settings page.


---

# 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.lionparcel.com/guides/guides-en/features/data-management/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.
