Skip to main content

Onboarding and Employee Provisioning UI

Purpose​

Starts onboarding for accepted offers, tracks onboarding status, collects employee-provisioning input, and completes the handoff.

Talent → Onboarding; protected onboarding route.

Intended users and preconditions​

Recruiter/HR workspace users. Final HR ownership and Employee permissions require confirmation. An accepted offer must be available. Completion requires the source-defined employee, organization, joining, and pay-mode fields.

Main components​

Metrics, accepted-candidate queue, status actions, onboarding form, checklist, organization lookups, provisioning action, and completion references.

Fields, columns, and sections​

The form includes employee/contact, organization, reporting, joining, employment, credential-entry, pay-mode, bank/KYC, document, and notes fields. Sensitive field values must not be captured in documentation or support evidence.

Filters and actions​

Create/start onboarding, mark in progress, edit collected data, and complete Employee provisioning.

Validation​

The UI requires employee code, login email, joining date, department, designation, and the relevant pay input. Backend eligibility and provisioning rules remain authoritative.

UI states​

  • Loading: Accepted-candidate loading is explicit.
  • Empty: An explicit no-accepted-offers state and select-a-record state are rendered.
  • Success: Completion stores returned references and reloads workspace state.
  • Error: Start and completion failures render page errors while retaining operator context.

Permission behavior​

Only coarse Recruitment route access is confirmed. Credential, bank/KYC, compensation, and Employee provisioning actions lack distinct UI permission evidence.

API dependencies​

Uses compatibility workspace, move-to-onboarding, onboarding-status, and onboarding-completion calls. Completion synchronously invokes Employee Service.

Employee code supports deterministic retry behavior in the backend. Login provisioning and manager mapping are not confirmed by the Recruitment-to-Employee integration; the UI field presence is not proof of downstream account creation.

Screenshot placeholder​

Capture only sanitized, non-production data after product and privacy review. No screenshot is embedded in this Draft page.

Onboarding and Employee flow​

Source References​

  • UI/salary-ui/apps/client-hrms-portal/src/pages/hr/RecruitmentOnboardingPage.tsx
  • microservices/src/recruitment-service/Application/Commands/OnboardingCommands.cs
  • microservices/src/recruitment-service/Infrastructure/EmployeeServiceClient.cs

Summary​

This Draft page summarizes source-backed Recruitment behavior and explicitly marks incomplete governance or implementation.

Audience​

Recruitment stakeholders, product, engineering, QA, support, operations, architecture, security, and implementation partners as applicable to this page.

Overview​

Use the source-backed sections above as the authoritative scope. Unsupported behavior remains Requires confirmation or Not implemented.

See Also​

Keywords​

  • Recruitment
  • Hiring lifecycle
  • Draft documentation

Revision Information​

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