A leave request nobody answers is worse than a rejected one — the person cannot plan. Auto-decision settles requests that have been pending too long, in a direction you choose.
1. How it works
A scheduled job looks for leave that has been pending longer than the configured number of days and settles it. The result is recorded as a system decision, not as a person's judgement.
| Setting | Meaning |
|---|---|
| Enabled | Off by default. Nothing happens until you turn it on |
| Days | How long a request may stay pending before it is settled |
| Action | Approve or reject once the time is up |
2. Choosing a direction
Approve suits organisations where leave is a notification rather than a negotiation, and silence means yes. Reject suits the opposite: nothing is agreed unless somebody agrees to it.
Either is defensible. What is not defensible is leaving requests pending indefinitely and letting people guess.
3. Site configuration
Set it under Admin Settings. It applies everywhere unless a project overrides it.
4. Per-project overrides
A project can override the site setting under Project Settings — useful where one team's leave genuinely needs a positive decision and the rest of the organisation is happy with silence.
5. Advance warning
Approvers are emailed before a request auto-settles, so the deadline is not a surprise. If nobody acts, the request settles and everyone is told what happened and why.