Onboarding & Offboarding Navigation
Summary
Recruitment exposes menu entries for Offers, Onboarding and Recruitment Reports. Exit is registered as a protected HR Operations route but has no verified item in the current application menu definition.
Audience
End users, QA, support and security reviewers validating how users reach lifecycle pages.
Reference Content
| Destination | Visible entry | Access observation |
|---|---|---|
| Recruitment dashboard | Dashboard menu | Recruitment roles; links to onboarding, offers and reports |
| Offers | Talent menu | Recruitment module and permission checks |
| Onboarding | Talent menu | Recruitment module and permission checks |
| Recruitment Reports | Talent menu | Recruitment module and permission checks |
| Exit | No verified menu item | Protected HR Operations route; direct or external navigation is required in current source |
| Public offer response | Opaque candidate link | Public shell; the action link itself must be treated as sensitive |
The Onboarding page provides links back to the Recruitment dashboard and across to Offers and Candidates. Offers provides the “Move to Onboarding” transition only for accepted offers. Legacy HR Operations routing maps the exit destination to the current protected page.
Menu visibility is a convenience control, not authorization. The protected-route layer and backend policies remain decisive.
Source References
UI/salary-ui/apps/client-hrms-portal/src/App.tsxUI/salary-ui/apps/client-hrms-portal/src/components/AppLayout.tsxUI/salary-ui/apps/client-hrms-portal/src/utils/ProtectedRoute.tsx
Related Articles
See Also
Keywords
- Navigation
- Protected route
- Talent menu
Revision Information
- Status: Draft
- Last reviewed: 2026-07-20
- Review cycle: Quarterly