Settings, Access, Approval Policies. Thresholds that route a request to the right approver by its value. You need weight 60 or above, and write access is limited to org admins plus finance and HR leads - if you are read-only you get a banner saying so rather than a save that fails.
What Is Actually Enforced
This is the first thing to know, and the surface states it against each type:
| Type | Status |
|---|---|
| Expenses | Enforced - submissions route through these tiers |
| Leave | Partially enforced - a flow exists but does not consult the tiers yet |
| Commission | Partially enforced |
| Discounts | Not yet enforced |
| Salary Advance | Not yet enforced |
| Hiring | Not yet enforced |
| Procurement | Not yet enforced |
| Refunds | Not yet enforced |
Keep in mind
Tiers you set for a "not yet enforced" type are stored and take effect when enforcement for that type ships. They do nothing today. Configure them if you want the policy recorded; do not rely on them to stop anything.
How A Tier Works
A tier is a value band plus one routing decision. A request falls into the band its value lands in, and goes to whoever that tier names.
Each tier has:
- Name - what it is called in the approval queue.
- Minimum and maximum value - the band. Leave the maximum empty for "and above".
- Who approves - one choice, below.
- Requires attachment - forces a receipt or document before submission.
- Escalation hours - how long before an unanswered request escalates.
Who Approves
One dropdown, one choice per tier:
| Option | Routes to |
|---|---|
| Auto-approve | Nobody. Passes straight through. |
| Any Staff (25+) | Anyone on the payroll |
| Any Senior (40+) | Senior and above |
| Any Manager (60+) | Manager tier |
| Any Dept Head (80+) | Department head tier and above |
| Admin / CEO (90+) | Organisation admins |
| Head of a department | The head of a specific department |
The weight numbers refer to role weight - see Roles. This is the direct link between the two surfaces: raising someone's weight changes what they can approve, whether or not you intended it.
Building A Set Of Tiers
Work upward, and leave no gaps.
- Pick the type at the top.
- Set the scope - which hub, and which currency. Leave hub empty for organisation-wide.
- Add the lowest tier. Small amounts, often auto-approve or any manager. Start the minimum at zero.
- Add the next tier. Its minimum should be exactly where the previous maximum ended.
- Continue upward, raising the approver at each step.
- Leave the top tier's maximum empty so nothing can exceed your bands.
- Save.
A worked example for expenses, in the hub's currency:
| Tier | Band | Approver | Attachment |
|---|---|---|---|
| Petty | 0 to 100 | Auto-approve | No |
| Standard | 100 to 1,000 | Any Manager (60+) | Yes |
| Significant | 1,000 to 10,000 | Any Dept Head (80+) | Yes |
| Major | 10,000 and above | Admin / CEO (90+) | Yes |
Caution
Gaps and overlaps both cause problems. A request whose value falls in a gap has no tier to route to. Check that each tier's minimum equals the one below it's maximum before saving.
Scope: Hub And Currency
Tiers can be set per hub and per currency, because a threshold that is trivial in one jurisdiction can be significant in another. The currency options derive from your base currency and the selected hub's currency.
Set organisation-wide tiers first, then add hub-specific ones only where the amounts genuinely need to differ. Every extra scope is another set to keep current.
Attachments And Escalation
Requires attachment is worth switching on for anything above the smallest band. It is much easier to require the receipt at submission than to chase it at reconciliation.
Escalation hours stops requests dying in someone's queue while they are on leave. Set it to something shorter than your patience - 48 hours is common for expenses.
Common Questions
A request is not going to anyone. Its value probably falls in a gap between tiers. Check the bands cover the full range with no holes.
I set tiers for discounts and nothing changed. Discounts are not yet enforced. The tiers are stored for when they are.
Someone can approve more than they should. Their role weight is higher than you think. Approval routing tests weight, so check the role before changing the tier.
Do these apply to every hub? Only if you left the hub scope empty. A tier set against a specific hub applies to that hub alone.
Did this answer your question?
No, ask a person