Approval rules

Rotaleave routes every leave request to the right people in one of two ways.

The default: managers approve

With no policy configured, requests follow a cascade based on where the person sits:

1. their team’s managers,
2. then their department’s managers,
3. then any manager in the organisation.

For most teams this is all you need — it’s the “Managers approve (recommended)” option in the setup wizard.

Approval policies

When you need explicit control — named approvers, multiple sign-offs, different rules per department — build a policy. Policies exist at three scopes, and the most specific one wins:

• Organisation — Settings → Approval policies (admin-only). This is the org default, “used when a department/team has no policy of its own.”
• Department — the “Approval policy” section on each department’s settings page.
• Team — likewise on each team’s page.

How a policy is built

A policy is a sequence of levels, approved in order:

• Each Level card holds one or more approvers picked from your managers and admins.
• Within a level, approvers are alternatives (“or”) — and when a level has several, a “Needed: N of M” dropdown sets how many of them must approve (a quorum).
• + Add level (then) chains another level that only starts once the previous one passes.

So “either shift supervisor, then the ops director” is two levels; “any 2 of 3 partners” is one level with Needed: 2 of 3.

Click Save policy when done, or Remove policy to fall back to the cascade. Requesters see multi-level progress on their pending requests, and approvers see “Level 2 of 3” style badges on the Approvals page.