Employee Navigation and Access
Summary
Employee Management is reachable from the People navigation group and through two protected routes.
Audience
- HR administrators, frontend developers, QA engineers, support engineers, and security reviewers
Purpose
Describe only the confirmed client-side navigation, route guard, tenant-session, and unauthorized behavior.
Employee page navigation
Confirmed behavior
- The Employees menu item points to
/employees, is grouped under People, and declares workforce,labor, and HR-oriented navigation metadata. - Both
/employeesand/laborrender the same component. - Missing authentication redirects to the tenant-aware login destination.
- Forced password change redirects before Employee rendering.
- A session without tenant identity is cleared and redirected to the separate platform portal flow.
- Failed feature checks render the Unauthorized page; there is no Employee-specific 404 route in
App.tsx. - Direct deep links work through React routing when the host serves the SPA fallback; hosting fallback behavior Requires confirmation.
Permission boundary
Frontend navigation metadata is not API authorization. The monolith controller requires authentication, narrows list/detail access with an access-scope service, and requires tenant-wide access for mutation. The extracted service names Employee policies, but its current registration only requires authentication for those policies. Final role-to-permission governance Requires confirmation.
Source References
UI/salary-ui/apps/client-hrms-portal/src/App.tsxUI/salary-ui/apps/client-hrms-portal/src/pages/Labor.tsxUI/salary-ui/apps/client-hrms-portal/src/utils/ProtectedRoute.tsxUI/salary-ui/apps/client-hrms-portal/src/components/AppLayout.tsxControllers/LaborController.csmicroservices/src/employee-service/Api/Endpoints.cs
Related Articles
See Also
Keywords
- Employee route
- route guard
- tenant access
Revision Information
- Status: Draft
- Last reviewed: 2026-07-15
- Review cycle: Quarterly