> 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/adding-new-user.md).

# Adding New User

The Create New User menu functions to add a new user to the system in a specific branch.\
This feature can only be accessed by admins who have branch access rights. Its purpose is to ensure that only legitimate users associated with that branch can access the system.

### A. New User Addition Form

<figure><img src="/files/f819c8ec60b69931d38a0b8eec4906611f2cb678" alt=""><figcaption><p>Figure 1 New User Addition Form</p></figcaption></figure>

**Explanation of Each Part of the Form:**

1. Username

* Used as the main login identity for the user in the system.
* Must be unique and not previously used by another user.
* Example: testing.
* Tip: Use a combination of names and numbers if there are many users in one branch (for example: testing01).

2. Email

* Email is used for notifications, password resets, and official communication.
* Must be in a valid format (example: <testing@gmail.com>).
* This field is required to activate email-based security functions (for example, account confirmation).

3. Mobile Number

* The mobile number is used as the primary verification and contact method.
* Writing format: use the country code +62 followed by the active number without the leading 0.\
  Example: +6288377893903.
* Note: The system will validate whether the number has already been registered or not.

4. &#x20;Account Type

* Determines the type of account being created.
* Common available options:
* Client Branch: used for users under a specific client's organizational structure.
* Corporate: used for users who have access to all branches.

5. Reference

* Refers to the branch name or organizational entity to which the user belongs.
* This field is automatically filled based on the access rights of the admin creating the user.
* Example: BOOKING API TEST CORPORATE CGK.
* Note: Admins cannot add users outside the branches they are responsible for.

6. Role

* Determines the user's access level and responsibilities in the system.
* Examples of available roles:
* admin\_client\_branch: has full access to all menus in that branch.
* client\_user: has limited access, can only view certain data.
* The role selection must be adjusted to the user's job function so that access rights violations do not occur.

7. Save Button

* After all data has been filled in correctly, click Save in the top right corner.
* The system will display a success notification if the user is created successfully.
* Note: If there are fields that have not been filled in or the format is incorrect (for example, an invalid email), the system will reject the save and display an error message.

### B. New User Creation Process Flow

1. The admin opens the User Management page.
2. Click the Create User button in the top right corner.
3. Fill in all data according to the form above.
4. Click Save to complete the process.
5. The system adds the new user and automatically displays Active status.

<br>

<br>


---

# 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/adding-new-user.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.