Asset Route Reference
Summary
Asset Management exposes exactly two frontend routes: an admin route under HR Operations and an employee self-service route. A legacy hash path redirects to the admin route. Route guards apply prefix-based visibility rules; they gate what a user sees, not what the backend authorizes.
Audience
Frontend developers, QA engineers, and support engineers who need to know which screen a user reaches, and under what visibility gates.
Reference Content
Routes
| Route | Audience | Page | Nav key | Module feature | Permissions | Roles |
|---|---|---|---|---|---|---|
/hr-operations/assets | Admin | HrOperationsAssetsPage | asset-requests | hr-operations | hr-operations | hr-admin, it-asset-admin |
/assets | Employee (ESS) | EssAssetsPage | ess-assets | (self-service) | Asset.ViewSelf, hr-operations | employee |
Legacy redirect
| Legacy path | Target |
|---|---|
Hash asset | /hr-operations/assets |
Guarding note
Route access is enforced by ProtectedRoute prefix rules, which evaluate visibility and feature gates only. These are not backend authorization checks; API authorization is covered separately in the Permissions Matrix. Employee self-service reads are further narrowed to the caller's own records by the gateway's labor-id composition, not by a route guard.
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/pages/hr/HrOperationsPage.tsx
Related Articles
See Also
Keywords
asset routes, navigation, redirect, route guard, self-service
Revision Information
- Status: Draft
- Last reviewed: 2026-07-17
- Review cycle: Quarterly