Skip to main content

HR Administration for Shifts and Work Calendars

Summary

HR administration spans three current UI locations: Shift Management, employee profile administration and Holidays/Weekly Off Policy. There is no unified scheduler console.

Audience

HR administrators, managers, product, QA, support and security reviewers.

Reference Content

Verified responsibilities

AreaHR actionBoundary
Shift ManagementAdd, edit and delete shift definitionsRouted compatibility behavior differs on delete
Attendance PoliciesCreate/update daily-hour thresholds, grace, overtime and shortfall settingsPolicy is distinct from shift assignment
Employee profileSelect one fixed shift or no fixed shiftCompatibility model; not effective-dated UI
Holiday settingsMaintain holidays and select company weekly-off daysCompany-level, not employee/shift-specific
AttendanceReview operational results and corrections according to permissionsSchedule publication is absent

Administrative sequence

Define policies before relying on attendance calculations; define shifts before assigning them; confirm affected employee links before deletion; maintain weekly offs/holidays; then review attendance and payroll outcomes. The direct extracted assignment foundation requires a supported administrative consumer that is not present in the inspected React application.

Business controls

Shift and assignment mutations generate audit/timeline evidence in the extracted service. Monolith CRUD uses authorization checks but does not expose the same lifecycle audit model in the inspected sources. Tenant scoping is required throughout.

Limitations and requires confirmation

No bulk assignment UI, schedule import/export, effective-date correction, assignment end/deactivate action, employee notification or approval exists. Production ownership, change-control practice and segregation of duties require confirmation.

Business Evidence Checklist

  • Business purpose: Maintain shift, policy, employee-link and work-calendar configuration.
  • Actors: HR administrators, authorized managers and downstream attendance/payroll owners.
  • Business process: Configure policies/shifts, link employees, maintain calendar and review outcomes.
  • Status transitions: Extracted configuration supports active/inactive state; UI workflows are CRUD-oriented.
  • Responsibilities: HR validates data and affected employees before change.
  • Business rules: Valid shift, calendar and authorization boundaries apply.
  • Integrations: Employee, Attendance, Leave, Payroll and Gateway routing.
  • Limitations: No unified scheduler, effective assignment UI, bulk work or notifications.
  • Requires confirmation: Ownership, change control and segregation of duties require confirmation.

Source References

  • UI/salary-ui/apps/client-hrms-portal/src/pages/hr/PayrollFeaturePages.tsx
  • UI/salary-ui/apps/client-hrms-portal/src/pages/Labor.tsx
  • Controllers/ShiftsController.cs
  • Controllers/WeeklyOffsController.cs

See Also

Keywords

  • HR administration
  • Shift settings
  • Weekly-off policy

Revision Information

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