Leave Navigation and Access

Summary

Leave entry points are filtered in navigation and guarded at route rendering, with employee, manager, and admin menu variants pointing to the same Leave path.

Audience

Portal users, administrators, frontend developers, QA, and support.

Overview

The menu supplies audience and role hints, but actual menu inclusion also depends on module features and permissions. /leave requires the time-office module feature and a Leave route feature. /settings/holidays requires time-office and a settings-related route feature. Exact identifiers remain source implementation details and are not a final business role catalog.

The ESS API client adds available authentication, tenant, user, and employee context to requests. The legacy shared client performs its own configured context behavior. Deep links pass through the same ProtectedRoute. Missing authentication redirects; a disallowed feature renders Unauthorized. Backend tenant and authorization enforcement remains authoritative.

Manager/team scope is visible in menu intent and parts of the legacy page, but final extracted-service authorization parity is Requires confirmation.

Source References

• UI/salary-ui/apps/client-hrms-portal/src/App.tsx
• UI/salary-ui/apps/client-hrms-portal/src/components/AppLayout.tsx
• UI/salary-ui/apps/client-hrms-portal/src/utils/ProtectedRoute.tsx
• UI/salary-ui/apps/client-hrms-portal/src/ess/essApi.ts

Related Articles

• Leave UI
• Leave API

See Also

• Leave business documentation
• Leave technical documentation

Keywords

• Leave UI
• Leave Navigation and Access
• Workforce management

Revision Information

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