> For the complete documentation index, see [llms.txt](https://info.edusuite.asia/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://info.edusuite.asia/product-guide-k12/admin-home/users-module/user-setup/user-roles.md).
# Users
This feature allows users to manage all the web user accounts in the system.
## Access and Navigation
To access this module, go to **Users** > **User Setup** > **Users**
If you cannot view the link from the list, check the privilege assigned to your account or role.
{% hint style="danger" %}
Contact your school’s system administrator to request view or edit access if you cannot access the rights management screen.
{% endhint %}
## Import New Users via CSV file
Using the import feature significantly reduces the time and effort required to create user accounts individually.
* Click **Import** on the upper right portion
* It will prompt the required data for a successful import:
* **Email -** must be unique
* **Contact Number -** must be numbers only ex. 09XX XXX XXXX
* **Roles -** define the set of privileges assigned to a user, determining what actions they can perform and what information they can access. These roles should be selected from predefined User Roles and can include multiple roles separated by a "|" for flexibility and comprehensive access control
A template is also provided where these data can be encoded.
## Create a New User
This function is specifically designed for creating non-student and non-faculty users. Users such as guardians, students, or faculty members should be created through their respective modules: the Student module for students and the Faculty module for faculty members.
However, once created, **all users**, including students and faculty, can be managed from this module. This centralized management ensures administrators have a unified view and control over all user accounts, streamlining updates, role adjustments, and other administrative tasks.
* To manually create a user, click **+ New User**
* Fill out the necessary details:
* **First, Middle, Last Names**
* **Email -** must be unique
* **Contact Number -** must be numbers only ex. 09XX XXX XXXX
* **Roles -** define the set of privileges assigned to a user, determining what actions they can perform and what information they can access. These roles should be selected from predefined User Roles and can include multiple roles separated by a "|" for flexibility and comprehensive access control
* Click **Add User** once done
## Edit a User
To edit, click the **Pencil** button of the user and modify the contents as needed. Click **Save Changes** once completed
## Reset a User's Password
* Click **Reset Password**
* It will prompt you to confirm the action. Click **Yes**
* The user will receive an **email notification** containing the link to change the password. Kindly ensure that the notification for the **Reset Account Authentication** is enabled
## Sort and Search Users
To search, click the M**agnifying Glass** icon in the upper-right corner of the page, enter a keyword, and press Enter. The relevant search results will then be displayed.
To sort, click the **Arrow Down A-Z** icon in the upper-right corner of the page and select a sorting option:
* Email
* First Name
* Last Name
* Middle Name
The sorted results will be displayed accordingly.
---
# 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://info.edusuite.asia/product-guide-k12/admin-home/users-module/user-setup/user-roles.md?ask=&goal=
```
`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.