Skip to main content

Onboarding & Offboarding

Summary

HR Suit implements two separate lifecycle paths. Recruitment moves an accepted offer through Pending or In Progress onboarding and completes an Employee handoff. HR Operations implements employee resignation, manager/administrator decisions, rollback, and a manual post-last-working-day access-revoke action. These paths are Transitional because compatibility routing changes completion behavior and no single coordinator owns all downstream readiness or clearance.

Audience

Employees, managers, recruiters, HR administrators, product owners, engineering, QA, support, security, and architecture reviewers.

Overview

Use this section to understand verified business behavior and its current boundaries. It does not define policy or certify production readiness.

Documentation map

Business architecture

Maturity and exclusions

Implemented behavior is described as implemented only at its verified boundary. IT provisioning, an onboarding-owned approval workflow, automatic asset assignment/return, automatic checklist enforcement, automatic leave or attendance activation, final settlement, exit interview, knowledge transfer, archival policy, and legal compliance certification are Not implemented or Require confirmation.

Source References

  • microservices/src/recruitment-service/Application/Commands/OnboardingCommands.cs
  • microservices/src/employee-service/Domain/Employees/Employee.cs
  • Controllers/HrOperationsController.cs
  • microservices/src/gateway-api/Program.cs
  • UI/salary-ui/apps/client-hrms-portal/src/pages/hr/RecruitmentOnboardingPage.tsx
  • UI/salary-ui/apps/client-hrms-portal/src/pages/hr/HrOperationsPage.tsx

See Also

Keywords

  • Employee onboarding
  • Employee offboarding
  • Lifecycle coordination

Revision Information

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