Support Portal

Submit a ticket My Tickets
Welcome
Login  Sign up

Entitlement Setup - Creating an entitlement element

Who this guide is for


System Administrators – Requires ‘System Admin’ role, Entitlements, and Absence Types of permissions


Overview

Create a new entitlement element within an entitlement pot so you can calculate, track, and carry over leave precisely (e.g., annual leave, sick leave).


How Entitlement Elements Work

An entitlement element is a component inside an entitlement pot. Elements define how leave is accrued, displayed, and carried over. You can later map absence types to draw down from a specific element for accurate balance management.

How to Set Up a New Entitlement Element

  1. Open Entitlements (Global)
    • Go to Admin tools > Admin panel > Global > Entitlements.
    • Click Edit on the relevant entitlement pot.

  2. Add a new element
    • Click + Add new entitlement element.

  3. Complete the element form
    Name – enter a clear, descriptive name (e.g., “Annual Leave – Core”).
    Enabled – set to Yes to make the element active, or No if you wish to enable on a Template OR User
    Sort index – set display order within the pot (lower = higher in the list).
    Carry Over and Expiry – expand to configure rules (see below).
    Allow manual carry over to – select one or more destination elements that admins can choose when manually carrying over.
    Automatically carry over to – select the element that receives automatic carry over at year-end (if used).
    Maximum carry over amount (hours) – enter limit in HH:MM.
    Maximum carry over amount (days) – enter limit in days.
    Carry over expires (into this element) – choose the element that receives any expiring carried balance (if applicable).

  4. Save
    • Click Save (top of page).


Additional Information
• Key terms
Entitlement pot: A user’s overall balance container (e.g., Holiday).
Entitlement element: A sub-balance with its own carry-over/expiry rules.
• Permissions
Requires ‘System Admin’ role and Entitlements to create/edit elements. Mapping absence types requires Absence Types permission.
• Best practices
– Use clear naming and a consistent Sort index to keep views tidy.
– Configure Automatic carry over for standard flows; enable Manual carry over only when admins must choose destinations.
– Define either hours or days carry-over caps to avoid conflicting limits.
• Warnings
Warning: Template and User settings can override Global rules.
Warning: Changes affect entitlement calculations immediately after you click Save.
• Tip: Use the search function within the platform to quickly find features or settings.

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.