The job of this console
Publish a working week for a population, attach timezone and start, and let leave and attendance inherit. Change with care mid-year; preview day counts.
HRMS · Admin · Shift
Shift Policies
Define working-week calendars (workdays, start time, timezone) that leave day-counting and attendance can inherit.
Scroll to Flowcharts for setup and assignment. Related: Legal calendars & working days.
Working-week calendars
Workdays, start time, timezone — inherited by leave and attendance
Shift policies define working-week calendars that leave day-counting and attendance can inherit. They are not a shift-bid marketplace unless that module is separately enabled.
Admin → Shift policies
Route
/admin/shift-policies
Org flag shiftPoliciesEnabled
HR Admin · Org Admin
Seat at the table
HR administrators. Employees see the effect on leave and attendance; they do not author the week here.
The working rhythm
Open policies, edit workdays and timezone, save, assign as the product allows, then prove a leave span and an attendance week.
Moments that bring you here
A 4.5-day week. A new geography. After leave counted a Sunday. Night-shift start times confusing the matrix.
ⓘ
Inherited by time engines
Leave and attendance read these calendars. Do not maintain a second working-week in a spreadsheet.
Interactive data flow
Working-day resolver chain — shift assignment, holidays, jurisdiction calendars, and leave day count validation.
Flowcharts
Each diagram auto-plays steps when it scrolls into view. Use Play / Pause, or click a step to jump.
1 — Create a shift policy
From empty catalog to an active primary shift used by the org.
flowchart TD
A[Open Shift policies] --> B[New shift policy]
B --> C[Set workdays + times]
C --> D[Save ACTIVE]
D --> E[Used by leave / attendance]
- 1Open Shift policiesAdmin → Shift policies with shiftPoliciesEnabled on.
- 2New shift policyCreate with code, name, timezone, and Mon–Sun workday toggles.
- 3Set workdays + timesPick ISO weekdays that count and optional start/end times.
- 4Save ACTIVEActive policies appear in the catalog; one is typically primary.
- 5Used by leave / attendanceWorking-day resolver can fall back to team/shift schedule when no override exists.
2 — When shift affects leave days
Priority chain: employee override → jurisdiction → team/shift → Mon–Fri.
flowchart TD
Emp[Employee leave] --> Res[Working-day resolver]
Res --> O{Employee override?}
O -->|Yes| WD[Use override]
O -->|No| J{Jurisdiction?}
J -->|Yes| WD2[Use jurisdiction]
J -->|No| S[Team / shift policy]
S --> WD3[Workdays from shift]
WD --> Hol[Minus holidays]
WD2 --> Hol
WD3 --> Hol
- 1Employee leaveApply or submit triggers day count for that employee.
- 2Working-day resolverSingle service used by leave create/submit/promote.
- 3Employee override?Personal working-day rule wins if assigned.
- 4Jurisdiction?Country/region pattern from leave jurisdiction assignment.
- 5Team / shift policyFalls back to shift/work schedule when configured.
- 6Minus holidaysHoliday calendar keys exclude non-working public days.
Overview
Admin → Shift policies stores organization shift calendars. Leave day counting may use these when no employee or jurisdiction override exists. Enable via Application Config / menu access.
How to use
1. Enable the module
Confirm shift policies are enabled for the organization.
2. Create the primary shift
Match your standard work week (e.g. Mon–Fri 09:00).
3. Align leave calendars
Map holiday locations and jurisdictions so leave excludes the right days.
4. Verify with a test leave
Apply a range spanning a weekend and confirm day count.