Skip to main content

Manager Responsibilities for Workforce Scheduling

Summary​

Managers have verified attendance review responsibilities, but a dedicated manager scheduling workflow is not implemented. Client navigation and routed backend authorization are not fully aligned for shift mutation.

Audience​

Managers, HR administrators, security, product, QA and support.

Reference Content​

Verified responsibilities​

  • HR managers can be offered the Workforce Shifts navigation item when Time Office and shift/settings permissions are present.
  • Department and HR managers can access team attendance navigation according to attendance permissions.
  • Managers may review/approve/reject team attendance under the established access scope.
  • No manager function assigns shifts to a team, publishes a roster or approves an employee shift request.

Authorization boundary​

The protected client route checks module feature and settings-related permissions. The monolith shift controller restricts create/update/delete to administrator roles, while list is authenticated. The extracted Attendance Service currently registers its direct permission policies as authenticated-user requirements. Therefore a visible page or client role is not proof that a mutation is authorized or appropriately scoped.

Business process​

Managers can use attendance evidence that results from shift/policy configuration, but scheduling configuration should be treated as HR administration until the active backend authorization and organizational policy are confirmed.

Limitations​

No team roster, workload/capacity view, understaffing warning, conflict check, manager delegation, approval, bulk assignment or department calendar exists.

Requires confirmation​

The organization’s intended manager role, separation of duties and production permission mappings require confirmation and security review.

Business Evidence Checklist​

  • Business purpose: Define verified manager involvement around shift-derived attendance.
  • Actors: HR managers, department managers, HR administrators and security/support.
  • Business process: Access permitted views, review team attendance and escalate configuration needs.
  • Status transitions: Managers act on attendance states, not schedule publication states.
  • Responsibilities: Managers review scoped attendance without assuming shift mutation authority.
  • Business rules: Client visibility never replaces backend authorization/scope.
  • Integrations: Identity/permissions, employee reporting scope and Attendance.
  • Limitations: No team roster, bulk assignment, approval or coverage view.
  • Requires confirmation: Intended roles and production permission mapping require confirmation.

Source References​

  • UI/salary-ui/apps/client-hrms-portal/src/components/AppLayout.tsx
  • UI/salary-ui/apps/client-hrms-portal/src/utils/ProtectedRoute.tsx
  • Controllers/ShiftsController.cs
  • Services/AccessScopeService.cs
  • microservices/src/attendance-service/Program.cs

See Also​

Keywords​

  • Manager scope
  • Attendance approval
  • Authorization mismatch

Revision Information​

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