Skip to main content

Employee details and fields

The details form is the heart of the master data. It appears in full on the Standard View at /Entities/HRM/Employee/{id}, and in the Details tab inside the 360 view. Fields are grouped into collapsible sections.

Header fields​

From the top of the page, without scrolling into the form:

FieldDescription
ActiveWhether the record is enabled for daily operations
DataConfidentialityWho can view the record
EntityStatusLifecycle status — required
EntityTypeEmployee classification — required

1) Names and display identity​

FieldDescription
First / middle / last name (English)English name parts — required
First / middle / last name (Arabic)Arabic name parts — required
Display nameComposed automatically from first and last name

2) General information​

FieldDescription
Birth date (birthDate)Employee date of birth
Personal email (personalEmail)Non-operational email; must be valid if entered
Mobile (mobile)Personal contact number
NationalityEmployee nationality
MaritalMarital status
GenderEmployee gender
BloodGroupBlood group when needed for medical purposes

3) System information​

FieldDescription
Application user (AppUsr)Link to a system user account — locked after creation
Work email (workEmail)Operational email — locked after creation
After the first save

Application user and work email become read-only. Any later correction needs an administrative path outside direct edit on the form.

4) Hiring information​

FieldDescription
Start / end dateVisible assignment period; end cannot precede start
Join / exit dateActual join and exit dates; exit cannot precede join
DirectManagerDirect operational supervisor
WorkShiftWork shift
GradeJob grade
JobJob title
BranchWork branch
DepartmentOrganizational department
MedicalInsuranceMedical insurance link or data
ResumeSourceHow the candidate/employee was sourced
CurrencyCompensation currency
Working hoursApproved working hours for the record

5) Address​

Records the residence or approved contact address (country, city, state, street, zip code as shown in the interface).

Form validations​

  1. End date ≥ start date
  2. Exit date ≥ join date
  3. Email format is valid when filled
  4. Type and status are required in the header

If a validation error appears, complete the missing field and save again.

How to save​

  1. Edit the required fields
  2. Select Save Changes
  3. For operational follow-up, open /Entities/HRM/Employee/360/{id}

Best Practices​

Fill department, job, and manager from the first week

Structure reports and payroll runs weaken if hiring fields stay empty after the actual assignment.

Currency is not for display only

Salary and cost amounts are read in the record currency. Set it early so payroll comparisons do not mix.