Approval workflows
Require approval on any request type, from one approver or an ordered chain. Approvers decide from their portal, and while they are away, a colleague they choose can decide for them.
Single approvers and approval chains
Turn on approval for a request type and list the approvers in the order they decide. Each approver is asked only after the one before approves, and a denial at any step closes the request.
- With no chain listed, each request goes to a single approver automatically
- Agents can also send any open request to an approver they choose
- When the last approver approves, the request goes back to the desk
Deciding and delegating
Approvers get an email and decide from the Approvals page of their portal, where the request's details sit beside the decision.
- Before time off, an approver can forward their approvals to a colleague for a date range
- Approvers can open a confidential request they are asked to decide
SLAs and automations around approvals
Time spent waiting on an approver does not have to count against the desk's SLA, and your rules and systems can act on each decision.
- New workspaces start with SLA policies that pause the clock while a request waits on approval
- The Approval decided trigger starts automation rules
- Webhooks send an approval.decided event to your own systems
More in Approvals
Audit log
Submitting, deciding, delegating and cancelling an approval are each recorded with who did it and when.
Reminders
From the Approvals page, an agent can send a waiting approver a reminder or reassign the approval to someone else.
Force-resolve
A manager can resolve a request that is still waiting. Any pending approval is denied and an internal note records why.
Approvals for any team
Hardware purchases, access requests, expenses and contract reviews all use the same workflow.
Included in every plan.See pricing →
Questions about Approvals
- Can several people approve at the same time?
- No. Approval chains are sequential: each approver is asked after the one before approves. Parallel approval is not supported.
- What happens when an approver is on vacation?
- From the Approvals page, they forward their approvals to a colleague for a date range. While the delegation is active, every approval routed to them goes to that colleague.
- Does waiting on approval count against our SLA?
- Not by default. The starting policies pause the clock while a request waits on approval. Remove that pause status from a policy if you want the clock to keep running.
Documentation
- Approvals & delegationRequire approval per request type, from one approver or an ordered chain of approvers. An approver can delegate to a named user for a date range.
- AutomationsBuild rules on a drag-and-drop canvas from six triggers and twelve actions, with an Else path for requests that do not match the conditions. Route, tag, notify, and call webhooks.
- SLAs & business hoursSet first-response and resolution targets in hours for each policy. Add a weekly business-hours schedule, a holiday calendar, optional pause statuses, and escalations that act at a threshold.
Related
- Requests and portalIntake forms, the employee portal and the agent queue
- AutomationsIf and Else rules on a drag-and-drop canvas
- SLAsResponse and resolution targets on business hours
- Approval workflowsApproval before access is granted, hardware is ordered, or onboarding completes, with delegation and an audit log entry per decision.
- Finance request managementPurchase requests, budget and expense approvals, vendor onboarding, and PO sign-off, each with an audit log entry.
Try it with your own data
Create a workspace and set it up with your own teams, request types and settings.

