Skip to main content

Recruitment Navigation and Access

Confirmed access evidence

The shared guard requires a client token, tenant-scoped user context, the Recruitment module feature, and matching client feature evidence for protected Recruitment prefixes. The menu has recruiter/HR-oriented role and audience hints. The dashboard adds its own role-or-feature check. Public routes bypass the shared guard.

UI visibility is not authoritative API authorization. The backend policy catalog is empty and Recruitment endpoint groups do not apply explicit authorization policies. Hiring-manager and interviewer scoping, ownership rules, and Platform entitlement enforcement therefore require confirmation.

Unauthorized and unavailable behavior

Missing authentication redirects to tenant entry or landing. Invalid tenant/super-admin context is cleared and redirected to the appropriate portal boundary. Missing route feature evidence renders the unauthorized page. Report panels can render individual sources as unavailable and offer retry.

Public-token boundary

Public feedback and offer routes use a route token to look up a record. Generation, authentication strength, expiry, revocation, replay protection, and support ownership are not established by frontend source.

Source References

  • UI/salary-ui/apps/client-hrms-portal/src/App.tsx
  • UI/salary-ui/apps/client-hrms-portal/src/utils/ProtectedRoute.tsx
  • UI/salary-ui/apps/client-hrms-portal/src/components/AppLayout.tsx
  • UI/salary-ui/apps/client-hrms-portal/src/dashboard/DashboardPages.tsx

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