> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/health/v1.5/hcm-product-suite/health-products/digit-hcm-app/user-manual/common-functions/user-management.md).
# User Management
An illustrative guide to using the User Management Module
The ability for supervisors/managers to create and manage users and team assignments for their respective boundaries through the user interface.
## User Roles
| User Roles | Scope of Action | Role Description |
| -------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------- |
| System administrator |
a. Create, search, update, and deactivate user accounts.
- Create, search, update, and deactivate other system administrator accounts.
b. Create, assign, update, and delete role assignments.
c. Create, assign, update, and delete campaign assignments.
| A system administrator is a super user, who has complete access to all the features that the product includes. |
| Supervisors |
a. Create, search, update, and deactivate user accounts (except system admin).
b. Assign/update/delete role assignments.
c. Assign/update/delete campaign assignments.
| Supervisors are responsible to monitor and guide the teams during the campaign and ensure that the targets are met effectively. |
| Helpdesk user |
a. Create, search, update, and deactivate user accounts (except system admin).
b. Assign/update/delete role assignments.
c. Assign/update/delete campaign assignments.
| Helpdesk users are the support team established to provide assistance throughout the campaign. |
## Using the User Management Module
A landing page must be available to the user to access all available modules.
#### Search Page
A user must be able to search for an existing employee using search parameters (name, mobile number, username).
#### Create New Employee
Users must be able to create new users by providing the following details. Refer to the section on specifications.
#### Assign Campaigns
#### View and Edit Screen
Allow users to reset the password. Allow users to edit existing information or add information to an existing employee. Refer to the section on specifications for validations and conditions.
#### Deactivate Employee Screen
Refer to the section on specifications for validations and conditions.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.digit.org/health/v1.5/hcm-product-suite/health-products/digit-hcm-app/user-manual/common-functions/user-management.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
.png)
.png)
.png)
.png)
.png)
.png)