Skip to main content

Profile and Organization Setup

Initial Employee information​

Employee creation supports employee code, first and last names, display name, email, phone, optional department, designation, reporting manager, gender, and employment details. Employment details support employment type, work location, joining date, confirmation date, and date of birth. A created Employee starts Active and receives creation/timeline evidence.

Employee code and first name are required by the create command; email is part of the command and validated by the Employee model. Tenant-scoped uniqueness and organization-reference validation are enforced by Employee validators. Personal identity values, address, bank accounts, education, experience, emergency contacts, skills, document references, and notes are separate profile mutations rather than required Employee creation fields.

Department and manager assignment​

Department, designation, and manager are optional in the Employee domain. The onboarding UI makes department and designation mandatory and manager optional. Employee Service prevents self-management on later manager changes. No organization hierarchy beyond these references should be inferred.

Work location and employment​

Work location exists in Employee employment data and Employee search, but the Recruitment onboarding UI does not collect it and the extracted provisioning client sends no work location. Employment type is collected by the UI; the extracted compatibility completion does not forward it into the provisioning command and the provisioning gateway defaults the Employee request when absent. Direct/Hourly is a monolith compatibility pay/attendance mode, not an Employee-service employment-status taxonomy.

Transitional gaps​

The monolith completion can apply numeric organization references, manager, employment/pay mode, and login data. The extracted Employee service uses different reference types, and current Recruitment provisioning passes department and designation as absent and does not resolve the numeric manager. Organization assignment parity therefore Requires confirmation.

Source References​

  • microservices/src/employee-service/Domain/Employees/Employee.cs
  • microservices/src/employee-service/Application/Commands/EmployeeApplicationCommands.cs
  • microservices/src/employee-service/Application/Validators/EmployeeCommandValidators.cs
  • microservices/src/recruitment-service/Infrastructure/EmployeeServiceClient.cs
  • microservices/src/recruitment-service/Application/Compatibility/CompatCommands.cs
  • Controllers/RecruitmentController.cs
  • UI/salary-ui/apps/client-hrms-portal/src/pages/hr/RecruitmentOnboardingPage.tsx

Revision Information​

  • Status: Draft
  • Last reviewed: 2026-07-20
  • Review cycle: Quarterly