> 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/sandbox/specifications/user-manual/employee-management-user-manual/create-new-employee.md). # Create New Employee 1. Navigate to **Employee Management >> Create Employee** on the left panel.

2. Fill in the employee details on the form. Refer to the table below for input reference details.

Field	Mandatory (Y/N)	Description
Name	Y	Name of user (“employee”) to be created
Mobile Number	Y	Mobile number of employee. This needs to be unique. For demo purposes, you can use any mobile number you like as long as it is not shared by another HRMS employee.
Gender	Y	Gender of Employee
Date of Birth	Y	Dd-mm-yyyy format
Email ID	Y	Email ID of employee. This needs to be valid and unique, and will be used for OTP verification.
Correspondence Address	Y	Address of employee. Enter any address here for demo purposes.
Employee Type	Y	Choose whether the employee is permanent, contract, etc.
Date of Appointment	Y	DD-MM-YYYY
Hierarchy	Y	This represents the boundary hierarchy, and can be either revenue or admin. If you have not created a boundary hierarchy and are using the default, you can select either revenue or admin from the dropdown
Boundary Type	Y	Choose “City” if you are going with default boundary configurations.
Boundary	Y	Select your organization name from the drop-down if you are going with default boundaries.
Role	Y	Select a role based on what permissions you want this employee to have. A summary of roles is given below.
Assigned From Date	Y	The date from which employee has been in the assigned designation
Assigned To Date	Y	NA if “Currently Assigned here” is checked. Otherwise, assign any date after “Assigned From Date”. Please note that an employee has to have at least one current assignment.
Department	Y	The department to assign the employee to
Designation	Y	Designation of the employee. Select any department and designation for demo purposes.

3. Click on **Submit** to create the employee record. Click on **Go back to home page** button to navigate to the home page. Refer to the [Role-Action Mapping table](#role-action-mapping) for details on assigned roles and permissions linked to each role.

## Role-Action Mapping Below is a list of roles that an employee can be assigned, along with the permissions associated with the role:

Role	Actions
Superuser	All actions associated with Sandbox & its products
Admin	Employee Management + All Complaints actions (including dashboards)
Employee	View Inbox (list of complaints)
Complaints-Admin	All Complaints actions (including dashboards)
Assigner	File Complaint, Assign Complaint, Reject Complaint, Reassign Complaint
Resolver	Resolve Complaint

### Default Employees To save a Sandbox user the trouble of creating employees, the module has 2 employee roles pre-created for you to use.

Employee ID	Employee Role	Permissions
Assigner@demo.com	Assigner	File Complaint, Assign Complaint, Reject Complaint, Reassign Complaint
Resolver@demo.com	Resolver	Resolve Complaint

--- # 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://docs.digit.org/sandbox/specifications/user-manual/employee-management-user-manual/create-new-employee.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.