Approval workflows
Configurable approval chains for every request type — leave, spend, purchases, HR changes — with levels, escalation and a permission-gated force-approve for genuine emergencies.
Everything that changes money, time or records in Zaffre Axon runs through an approval chain: leave and attendance changes, salary advances and loans, purchases and petty cash, HR actions like transfers and increments. Chains configure per request type — and where it matters, per employee group — with as many levels as the decision deserves.
Approvers act where they already are: in the app, on mobile, or from actionable cards in the team chat with Approve and Reject buttons. Every decision records who, when and in what order, so the trail reads like a story instead of a mystery.
For the genuine emergency there is force-approve — a separately permissioned action that records itself loudly. The exception exists, but it is never invisible.
How it works
- 1
Define levels
Approval levels and chains per request type, and per group where needed.
- 2
Requests route
Submissions enter their chain automatically and notify the right approver.
- 3
Approve anywhere
In-app, mobile or chat cards — decisions post back instantly.
- 4
Audit the trail
Every step keeps actor, timestamp and order; exceptions are flagged as exceptions.
Frequently asked questions
- Can approval chains differ by request type?
- Yes — each type carries its own chain, and leave chains can additionally differ per employee group.
- Can managers approve from their phone or chat?
- Yes. Requests appear in the mobile app and as actionable chat cards; a tap approves or rejects with the decision recorded.
- What if an approver is unavailable in an emergency?
- Force-approve exists as a separately permissioned action, prominently logged, so the business can move without the control disappearing.
- Is there a record of who approved what?
- Every request preserves its full decision history — actor, order and timestamps — for audits and disputes.