Skip to main content

Authentication and Access Troubleshooting

Symptoms​

Recruitment menu is absent, a protected route redirects, or the unauthorized view appears.

Scope​

Client authentication, tenant portal context, feature visibility, and coarse route guards.

Cause​

Likely causes​

  • No client session is present.
  • User context is not a tenant user.
  • Recruitment feature evidence is absent.
  • Dashboard role/feature check differs from general route visibility.

Safe diagnostic steps​

  1. Confirm protected versus public route category.
  2. Confirm the session and tenant context exist without copying credentials.
  3. Compare menu visibility with direct route behavior.
  4. Record the unauthorized/redirect category and safe correlation evidence.

Resolution​

Safe resolution​

Restore access only through approved identity, tenant, role, or entitlement administration. Do not alter browser storage as a bypass.

Validation​

Reauthenticate normally and verify menu plus protected route; separately verify API authorization expectations.

Evidence to collect​

Collect the time window, environment category, affected operation, expected/actual status category, safe record reference, correlation reference where available, dependency/error category, and recent approved change. Exclude personal data, resumes/documents, interview notes, tokens, offer/compensation values, credentials, bank/KYC data, secrets, and configuration values.

Escalation​

Escalate session/identity issues to Identity/security; tenant/feature issues to Platform/tenant administration; route/menu inconsistency to frontend and Recruitment owners.

Source References​

  • UI/salary-ui/apps/client-hrms-portal/src/utils/ProtectedRoute.tsx
  • UI/salary-ui/apps/client-hrms-portal/src/components/AppLayout.tsx
  • microservices/src/recruitment-service/Program.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