Leave Configuration

Flowcharts

Each diagram auto-plays steps when it scrolls into view. Use Play / Pause, or click a step. Matching nodes highlight as the narration advances.

flowchart TD
  A[Enable flags] --> B[Publish policy]
  B --> C[Holidays and working days]
  C --> D[Balances / jurisdiction]
  D --> E[Employee applies]
  E --> F[Manager approves]
  F --> G[Attendance and timesheet]
          

flowchart TD
  F1[1. App Config flags] --> F2[2. Create jurisdiction]
  F2 --> F3[3. Template to draft policy]
  F3 --> F4[4. Simulate / Policy Test Lab]
  F4 --> F5[5. Publish version]
  F5 --> F6[6. People holidays + calendar key]
  F6 --> F7[7. Working-day rules]
  F7 --> F8[8. Opening balances or accrual]
  F8 --> F9[9. Prove apply and approve]
          

flowchart TD
  J[Jurisdiction] --> T[Template]
  T --> D[Draft version]
  D --> S[Simulate]
  S --> P[Publish]
  P --> R[Accrual and eligibility]
          

flowchart TD
  L[Leave create or submit] --> R[LeaveWorkingDayResolver]
  R --> O{Employee WDR override?}
  O -->|Yes| P[Resolved workdays]
  O -->|No| J{Employee jurisdiction?}
  J -->|Yes| JW[Jurisdiction / country WDR]
  JW --> P
  J -->|No| TW[Team-default WDR]
  TW -->|Hit| P
  TW -->|Miss| FB[Work schedule / shift / Mon-Fri]
  FB --> P
          

flowchart TD
  AP[Published policy] --> AJ[Accrual job]
  AJ --> BL1[Balance ledger credit]
  HR[HR adjust / import] --> BL2[Balance ledger]
  BL1 --> UI[Visible on Leave Management]
  BL2 --> UI
          

flowchart TD
  A[Apply] --> V[Overlap + working days]
  V --> S[Submit / reserve]
  S --> D{Approve or Reject?}
  D -->|Approve| B[Debit balance]
  B --> P[Promote TaskActivity]
  P --> T[Attendance sync if flagged]
  D -->|Reject| Rel[Release pending + comment]
          

Overview

Leave has two halves: configure once (this page) and use every day (Leave Management). Complete the configuration layers below before asking employees to apply.

1. Org & role flags — turn the module on in Application Config.
2. Global Policy Center (preferred) — jurisdictions, templates, versioned policies, publish, simulate.
3. Classic leave policies (fallback) — type catalog and simple entitlements when Global Leave is off.
4. Holidays & legal calendars — People holidays + calendar key assignments.
5. Working days — team / country / employee weekly-off patterns (not hard-coded Sat/Sun).
6. Employee leave config — opening balances / adjustments, OB template download, dry-run bulk import; optional employee jurisdiction assign.

Admin screen map

Required org & role flags

Org (org.json → HRMS)

• leaveAdditional.leaveManagementEnabled — master switch for native leave.
• leaveAdditional.globalLeavePoliciesEnabled — Global Policy Center runtime.
• leaveAdditional.leaveEnhancementsEnabled — enhancements (overlap, coverage, analytics).
• leaveAdditional.leaveBlockNonWorkingDayLeave — reject leave ranges with no working days.
• leaveAdditional.leaveAutoSyncToAttendance — approved leave → attendance LEAVE / HALF_DAY.
• approvalDelegation.approvalDelegationEnabled — leave in delegation scopes.

Role (role.json)

• hrmsModules.leavesEnabled, attendanceEnabled, timesheetEnabled, holidaysEnabled
• adminModules.leavePoliciesEnabled, globalLeavePoliciesEnabled, delegationEnabled
• CRUD: leaves.*, leavePolicies.*, holidays.*

Global Policy Center

Primary console: Admin → Leave admin → Global Policy Center. See flowchart 3 above.

1. Jurisdictions — country/region dimensions used in resolve and holiday/working-day scope.
2. Templates — apply a country baseline into a draft team policy.
3. Policies / versions — type entitlements, accrual, carry-forward.
4. Simulate / employee preview — dry-run before publish.
5. Publish — activates for accrual and eligibility.
6. Holiday calendars — assign location keys (e.g. IN, IN-KA) per jurisdiction.

Holidays & legal calendars

Source of truth: People → Holidays, filtered by active holiday calendar assignments.

1. Create holidays with a Location key (e.g. ["IN-KA"]).
2. Assign that key to a jurisdiction in Global Policy Center → Holiday calendars.
3. Optionally publish Legal Calendars to sync blocking holidays into People holidays.

Working days (team / country / employee)

Weekly offs are not hard-coded to Saturday/Sunday. Configure under /admin/leave/working-day-rules. See flowchart 4 above.

• Team default — rule with no jurisdiction.
• Country / region — rule linked to a jurisdiction; assign the employee to that jurisdiction.
• Employee override — assign an existing rule to one employee (highest priority).

Employee leave config & accrual

Canonical admin page: Admin → Employee leave config (/admin/employee-leave-config). This is the only UI surface for opening-balance cutover and per-employee adjustments. Accrual / carry-forward / comp-off expire jobs credit from the published Global Leave policy after go-live. See flowchart 5 above.

Page user flow (matches the live UI)

1. Confirm leaveManagementEnabled and leave admin role access; select the team in the header filter so employees load.
2. Read the KPI / insight strip (low balance, pending days) for the selected employee.
3. Bulk cutover — open the Opening balance template panel (or header Download OB template). Template rows are one per employee × PL/CL/SL (by location). entitlementAmount and amount are blank — fill from ZingHR / HR export only (do not invent balances).
4. Validate with POST /api/v2/admin/data-import/leave-balance?userTeamId={team}&actorId={you}&dryRun=true (body may also include "dryRun": true). Fix reportCsv failures, then re-POST with dryRun=false.
5. Single employee — select the person, review balance cards, use Adjust balance (opening entitlement and/or +/− available days) with a reason. Adjustments of 5+ days require a second confirmer employee id.
6. Prove end-to-end on Leave Management / People → Leaves: apply → Approvals approve.

Scenario guides

• Set employee leave opening balances — page walkthrough.
• Bulk import leave opening balances (dry-run then live) — cutover path.

How leave days are calculated

• Working week — employee override → jurisdiction → team → schedule/shift → Mon–Fri.
• Holidays — People holidays matching assigned calendar keys.
• Half-day — 0.5 when the single day is a working day.
• Server trust — create/submit recalculate numberOfDays.

Configuration use cases