Allowances

Allowances show how much leave a user can take for each configured time-off type.

What Affects Allowance

Allowance inputs

Max days per year

The annual limit configured on the time-off type.

Counts toward allowance

If disabled, approved and pending requests do not reduce remaining balance.

Join date

Allowance can be pro-rated for people who joined during the year.

Tenure rules

Types can require minimum tenure before eligibility.

Cooldown

Types can enforce a period before the same type is used again.

Status

Approved requests count as taken. Pending requests stay separate, but they also reduce remaining balance.

Remaining Balance

Remaining balance is calculated as:

allowed days - approved days that count toward allowance - pending days that count toward allowance

Pending requests reduce remaining balance so managers can see likely future impact before approval.

For users who start during the year, allowance can be reduced proportionally based on their effective start date. This keeps new members from receiving a full-year allowance when policy says otherwise. Pro-rating only applies to the first applicable year.

Exceeded Limits

Requests can create warnings when a user goes over an allowance. The warning is a planning signal; the approval policy still determines whether managers can approve the request.

Unlimited Allowances

Some time-off types have no cap, such as sick leave. These still track usage, but there is no remaining allowance to deplete when Counts toward allowance is off.

If an uncapped type is configured with Counts toward allowance on, its days draw from the shared allowance while adding 0 days to the allowed total. Supervisible warns admins about this setup in the type editor because it can intentionally or accidentally reduce the user's PTO balance.

Sensitive Types

Sensitive types can hide details such as reason or type name from people without access. They still reduce availability when approved.