Expense UI Navigation and Access

Summary

Both Expense routes are wrapped by the authenticated portal route component. Navigation visibility uses audience, module-feature, permission, and role metadata, but visibility and API authorization are separate controls.

Navigation paths

Entry	Intended users from navigation metadata	Visibility evidence
Self Service Expenses	Employee	Self create/view permission candidates
Workforce Expenses	HR administrator, HR manager, department manager	View/approve permission candidates and role candidates

The HR Operations route has a feature/permission rule. The ESS route is authenticated but Expense-specific direct-route parity requires confirmation. Component behavior also distinguishes employee-only presentation using locally stored role data; this is presentation logic, not proof of API authority.

No dedicated Finance navigation entry or manager queue exists.

Screenshot placeholder: capture only the two Expense navigation entries and authorized route result.

Requires confirmation

Direct-route permission parity, canonical role vocabulary, Finance access, manager authority, and compatibility authorization governance require 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

Related Articles

• Expense UI documentation
• Expense business documentation
• Expense API documentation

See Also

• Expense technical documentation
• Expense module

Keywords

• Expense UI
• Navigation and Access

Revision Information

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