Draft System User Setup

Name of the field	Description	Mandatory	Input	Data type	Minimum length	Maximum length	Validation	Comments	Need data from program/state
Name*	The name of the user who wants access to the system.	Mandatory	User	String	2	2000
Mobile No.*	Mobile number of the user.	Mandatory	User	Numeric	2	15	Length validation- Specific to Impel	Current HRMS specs are designed for Indian phone number formats and would need updates.	Yes
Father/Husband's Name*	Name of the user's husband or father.	Mandatory	User	String	2	2000			Yes
Gender*	Gender of the user being registered.	Mandatory	User	String	2	64			Yes
Date of Birth*	Date of birth of the user being registered.	Mandatory	User	Date	10	10		Date of birth cannot be in the future.	Yes
Email	Email ID of the user being registered.	Optional	User	String	8	64			Yes
Correspondence Address*	Address of the user being registered.	Mandatory	User	String		256			Yes
ULB*	ULB assigned to the user where the user is supposed to perform tasks assigned to him/her.	Mandatory	User	String		256			Yes
Role*	Role assigned to the user to enable him/her to carry out his/her tasks and access the required data and services.	Mandatory	User	String		256	Every user must have at least 1 role assignment.		Yes
Employment Type*	The employment types indicate the type of contract which he/she holds with the organisation. This indicates whether he/she is a permanent employee or a contract employee for a short period. Select the relevant employment type: 'Permanent', 'Temporary', “DailyWages” and 'Contract'.	Mandatory	User	String		256			Yes
Current assignment	The current assignment type is to indicate whether the employee is currently assigned to a particular department and designation. A user can be also be assigned multiple assignments to perform his/her function.	Mandatory	User	String		64			Yes
Status*	The status indicates the type of status which he/she holds, whether employed or not within the organisation.	Mandatory	User	String		256			Yes
Hierarchy *	The hierarchy indicates the hierarchy type for the boundary to which he/she is assigned.	Mandatory	User	String		256			Yes
Boundary Type *	The boundary type indicates assigning a city to his/her role within the organisation. A user can be assigned multiple boundary types to perform in different functions. Example: City, zone, block, and locality.	Mandatory	User	String		256			Yes
Boundary *	The boundary indicates assigning a particular city to his/her role wherein they perform the role function of the application for the particular city. A user can be assigned multiple boundaries to perform in a different location. Example: City name, and tenant zone.	Mandatory	User	String		256	User must be assigned to atleast 1 boundary.	Project boundary must take precedence over user boundary assignment.	Yes
Assigned from Date*	The assigned from date indicates the date from which his/her role is assigned to perform the role function assigned.	Mandatory	User	Date		10			Yes
Department*	The department indicates the particular department to which his/her role is assigned to.	Mandatory	User	String		256			Yes
Designation*	The designation indicates a particular designation that is assigned to his/her role.	Mandatory	User	String		256		Not required for HCM.	Yes