Leave rules
Two settings, and one of them matters more in India than almost anywhere else.
Before you start
- You need the
tenant.settings.managepermission. - The Leave module must be switched on.
Steps
- Go to Settings → Leave.
- Set:
| Setting | What it does | Default |
|---|---|---|
| Week off days | Which days are not working days | None |
| Allow backdated requests | Whether somebody can apply for leave already taken | Yes |
- Save.
Set your week-off days
An unconfigured workspace counts calendar days. It does not assume Sunday is off.
That is deliberate. A six-day week is common in India, and assuming Sunday is a week-off would quietly hand an extra day of leave to every business that works seven days. Guessing either way is wrong, so nothing is guessed.
If you work Monday to Saturday, set Sunday. If you close on Sunday and alternate Saturdays, set Sunday and handle the Saturdays as leave.
Backdating is allowed by default because sick leave is almost always applied for afterwards.
What this affects elsewhere
- How many days a request costs. The server counts the days from the two dates and your week-off setting. The number is never taken from the person applying — a client-supplied figure would be a self-service entitlement.
- Balances — allocated, used and pending.
- Attendance — approved leave marks those days "on leave".
Things worth knowing about leave
- A day is in exactly one balance column. Submitting moves days into pending; approving moves them pending → used; rejecting or cancelling moves them back. They are not independent totals.
- Overlaps are refused. Two live requests covering one day would deduct it twice and leave two answers to "was this person in".
- Nobody decides their own request.
- Only the applicant withdraws. An approver who wants it gone rejects it, which is recorded as a decision somebody made rather than as the applicant changing their mind.
- Unpaid leave is never refused for balance. A type that tracks no balance is exactly what somebody reaches for once they have used everything else.
- A type needing no approval is approved on submission, and the record shows that nobody decided it — so the history does not imply a manager signed it off.
What you cannot change later
Nothing here is permanent.
Not available yet. A screen to add, rename or retire leave types, or change an allocation. Leave types are set up when your workspace is created. Ask your administrator.
Not available yet. Multi-step approval, and leave that accrues monthly or carries forward. Allocation is the type's annual figure for the calendar year.
If it does not work
| What you see | What it means | What to do |
|---|---|---|
| A request costs more days than expected | Week-off days are not set | Set them — an unconfigured workspace counts calendar days |
| Nobody can file a request at all | This workspace has no leave types | Ask your administrator to run the leave-type seeder |
| "Overlaps an existing request" | Another live request covers one of those days | Cancel the other one first |
| A manager cannot approve | It is their own request | Someone else must decide it |