Skip to main content

Onboarding & Offboarding Feature Flags and Routing Switches

Summary

Three independent control layers affect lifecycle behavior: tenant/user module features in the client, gateway switches selecting extracted or compatibility services, and a Recruitment approval-workflow switch. No standalone onboarding/offboarding UI experiment flag was verified.

Audience

Product, support, QA, security and architecture teams.

Reference Content

ControlEffectOperational risk
Recruitment module visibilityShows protected Recruitment navigation and permits route evaluationHidden UI does not disable backend capability
HR Operations visibility/permissionsAllows evaluation of the protected Exit routeExit has no verified current menu entry
Recruitment gateway routingSends the compatibility-shaped UI surface to extracted Recruitment or monolith compatibilityCompletion semantics and accepted fields can differ
Employee gateway routingSelects extracted Employee or monolith handling for employee-owned routesIdentifier shape and persistence behavior differ
Recruitment approval workflowDelegates requisition approval behavior when enabledNot an onboarding approval workflow

Routing changes must be governed as compatibility changes, with pre-change contract tests, tenant-scope checks and rollback planning. The same browser path is not evidence of the same backend implementation.

The UI’s module-feature data comes from signed-in user context and platform entitlement behavior. Exact environment values, infrastructure configuration, change commands and tenant-specific settings are outside this public reference and Require confirmation through authorized configuration management.

Source References

  • UI/salary-ui/apps/client-hrms-portal/src/components/AppLayout.tsx
  • UI/salary-ui/apps/client-hrms-portal/src/utils/ProtectedRoute.tsx
  • microservices/src/gateway-api/Program.cs
  • microservices/src/recruitment-service/Program.cs

See Also

Keywords

  • Feature switch
  • Routing mode
  • Module entitlement

Revision Information

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