# User Roles

### Introduction

A user role defines permissions for users to perform a group of tasks. In a default application installation, there are some predefined roles with a predefined set of permissions. Each role has a certain number set of tasks it is allowed to perform and these roles are Super Admin, Trade License Approver, Data Entry Admin and Trade License document verifier etc.

### Data Table

<table><thead><tr><th width="113">Sr. No.</th><th>Code*</th><th>Name*</th><th>Description</th></tr></thead><tbody><tr><td>1</td><td>TL_APPROVER</td><td>TL Approver</td><td>Trade License Approver</td></tr><tr><td>2</td><td>GRO</td><td>Grievance Routing Officer</td><td>Grievance Routing Officer</td></tr><tr><td>3</td><td>CSR</td><td>Customer Support Representative</td><td>An employee who files and follows up complaints on behalf of the citizen</td></tr></tbody></table>

{% hint style="info" %}
Data given in the table is sample data for reference.
{% endhint %}

### Procedure

#### Data Definition

| Sr. No. | Column Name | Data Type    | Data Size | Is Mandatory? | Definition/ Description                                                                                      |
| ------- | ----------- | ------------ | --------- | ------------- | ------------------------------------------------------------------------------------------------------------ |
| 1       | Code        | Alphanumeric | 64        | Yes           | A unique code that identifies the user role name.                                                            |
| 2       | Name        | Text         | 256       | Yes           | The Name indicates the User Role while creating an employee a role can be assigned to an individual employee |
| 3       | Description | Text         | 256       | No            | A short narration provided to the user role name                                                             |

#### Steps to fill data

1. Download the data template attached to this page.
2. Have it open and go through all the headers and understand the meaning of them by referring 'Data Definition' section.
3. Make sure all the headers, its data type, field size and its definition/ description is understood properly. In case of any doubt, please reach out to the person who has shared this document with you to discuss the same and clear out the doubts.
4. Identify all different types of user roles on the basis of ULB’s functions.
5. Start filling the data starting from serial no. and complete a record at once. repeat this exercise until the entire data is filled into a template.
6. Verify the data once again by going through the checklist and taking care of each and every point mentioned in the checklist.

### Checklist

The checklist is a set of activities to be performed once the data is filled into a template to ensure data type, size, and format of data is as per the expectation. These activities have been divided into 2 groups as given below.

#### Common Checklist

This checklist covers all the activities which are common across the entities.

| Sr. No | Checklist Parameter                                                               | Example                                                                                                                         |
| ------ | --------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------- |
| 1      | Make sure that each and every point in this reference list has been taken care of | [Checklist](/local-governance/deploy/configure-digit/configuring-master-data-templates/module-setup/common-config/checklist.md) |

#### Entity Specific Checklist

This checklist covers the activities which are specific to the entity.

| Sr. No. | Activity                                           | Example                                                              |
| ------- | -------------------------------------------------- | -------------------------------------------------------------------- |
| 1       | The Code should be alphanumeric and unique         | TL\_APPROVER, GRO                                                    |
| 2       | The Name should not contain any special characters | <p>TL Approver : \[Allowed]</p><p>#TL Approver! : \[Not allowed]</p> |

### Attachments

{% file src="/files/-MJ0e2jDsRY5jxuF4kUq" %}
Configuration Data Template&#x20;
{% endfile %}

{% file src="/files/-MJ0e2jEUGU3TNVOs5Hf" %}
Sample Data
{% endfile %}


---

# Agent Instructions: 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:

```
GET https://docs.digit.org/local-governance/access/local-governance-stack/hrms/hrms-data/user-roles.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.