> 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/complaints-management/access/configurator-management-guide/people.md). # People ## Overview This section covers everyone connected to the system. It covers who's an employee and what they do, how departments and roles fit together, and who actually has a login to the system, separate from who's simply on the employee roster.

Item	What it does
Employees	This is your employee roster (HRMS). Note that this is not necessarily login access. An employee can exist here without having a working login, and vice versa.
Org Chart	A read-only visual view built from the same Department/Designation data in Employees
Users	This contains records of every Citizen login account.

## Manage Employees ### Employees The Employees sub-section opens to a table containing employee information. The data contains:

Column	Description
Employee Code	System-generated unique ID assigned automatically when the employee is created
Name	Full name of the employee
Mobile	Registered Mobile Number
Status	Employment status of the individual (Inactive, Employed, Suspended, Retired, Terminated)
Department	The department of their latest assignment
Designation	Job title of their latest assignment
Active	Whether login/account is currently enabled

To create a new employee, click on the “Create” button. This expands a section where you can fill in the required information to create an Employee. This involves:

#### Tenant Selects which city/ULB this employee is being created under. This needs to be mandatorily selected. #### Employee Info

Field	Mandatory	Basis
Name	Mandatory	Name of the employee
Mobile Number	Mandatory	Mobile number
Email	Optional	Email of the employee
Gender	Optional	Gender of the employee
Date of Appointment	Optional (defaults to current date/time if left blank)	Date of appointment - This can either be a date in the past or one in the future for future appointees.
Employee Type	Optional (defaults to PERMANENT if left blank)	Valid values: PERMANENT, TEMPORARY, CONTRACT, DEPUTATION.
Employee Code	Mandatory	Unique identifier for an employee
Date of Birth	Optional	Date of birth
Employee Status	Optional	Valid values include EMPLOYED, RETIRED, INACTIVE

#### Roles The role assigned to the user for the purpose of determining what action permissions this user is able to do. This is a drop-down list, and the applicable value can be selected. Refer to the Domain Ontology document for more information on the different roles. #### Assignments This is where an employee can be mapped to a department and a designation. You can also set your reporting manager. Note that this does not factor into SLA’s - This is strictly for maintaining an org chart. #### Jurisdictions Using the jurisdiction dropdown, set the areas that the employee is responsible for. You have the option to click on “Add Jurisdiction” () to assign multiple geographic areas to an employee. #### Account Password As an admin, you can set the initial password for an employee to perform first-time login. ### Org Chart For your selected account/tenant, you can find your organisation chart in this section. Note that this is purely for visual comprehension.

### Users This sub-section shows the records of citizens who have a login in the system. Upon clicking the **Create** button, you can create a new user by filling in their Name and Mobile Number to begin with.

--- # 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/complaints-management/access/configurator-management-guide/people.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.