> 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/mgramseva/introducing-mgramseva/enablement-toolkits/setting-up-services/create-user-api.md).

# Create User API

## Overview

This page provides a comprehensive guide on using the CreateNovaildate API to create users with specific roles based on their responsibilities within the system. Adjust the parameters and roles as needed for your specific requirements.

## Steps

The [CreateNovaildate](https://web.postman.co/workspace/My-Workspace~9f040a08-ea42-45f5-8e7b-4e79ceae42c7/request/24183907-95666725-c68a-42fb-a891-678f6d4eb01b) API allows users to create a new user with specified details that include username, name, gender, mobile number, activation status, user type, tenant ID, and password. Refer to the [Request Parameters](#request-parameters) details available below. 

Additionally, users can be assigned specific roles based on their responsibilities.

### Request Parameters

1. **username (string):** User's unique username.
2. **name (string):** Full name of the user.
3. **gender (string):** Gender of the user.
4. **mobileno (string):** User's mobile number.
5. **active (boolean):** User's account status (true for active, false for inactive).
6. **type (string):** It will be EMPLOYEE only.
7. **tenantid (string):** User's tenant ID.
8. **password (string):** User's password.
9. **Roles:** Roles determine the permissions and responsibilities assigned to a user. 

The available roles are as follows:

#### Roles for Sarpanch

* COLLECTION\_OPERATOR
* EXPENSE\_PROCESSING
* BULK\_DEMAND\_PROCESSING
* DASHBOARD\_VIEWER
* GP\_ADMIN

#### Roles for Secretary

* EXPENSE\_PROCESSING
* BULK\_DEMAND\_PROCESSING
* DASHBOARD\_VIEWER
* GP\_ADMIN
* COLLECTION\_OPERATOR

#### Roles for Revenue Collector

* COLLECTION\_OPERATOR
* DASHBOARD\_VIEWER

#### Roles for Division User

* HRMS\_ADMIN
* DIVISION\_ADMIN

#### Roles for State User

* HRMS\_ADMIN
* STATE\_ADMIN

To assign roles to a user, include the desired roles in the `roles` section of the request.

PROFILE\_UPDATE role is available for every user to update existing roles.


---

# 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/mgramseva/introducing-mgramseva/enablement-toolkits/setting-up-services/create-user-api.md?ask=<question>&goal=<user_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.