Skip to main content

Attendance UI Navigation and Access

Summary​

Attendance routes require an authenticated tenant user; navigation and route access are additionally filtered by module features and permission hints.

Audience​

  • Users, frontend developers, administrators, QA engineers, and support engineers

Confirmed paths are the shared Attendance route, its punch subroute, Shift settings, weekly-off settings, and Attendance report. Deep links pass through the same guard. The guard validates a client token, tenant-bound user context, required password change, module feature, and any matching permission hint; unavailable routes render the unauthorized experience.

The layout distinguishes employee, manager, and admin audiences using source-defined roles and permission features. Backend enforcement is separate and not proven by menu visibility. The base Attendance path has no explicit route-rule entry, so its effective access depends on authentication, navigation visibility, audience switching, and API enforcement—Requires confirmation for direct deep links.

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/EssPages.tsx

See Also​

Keywords​

  • Attendance UI
  • React
  • User workflow

Revision Information​

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