Skip to content

Documentation

Approvals & delegation

Require 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.

Where
Admin → Settings → Request types · Portal → Approvals · Request detail → Approvals
Permission
ACT_ON_APPROVALS · MANAGE_REQUEST_TYPES
Updated
October 2026

Overview

Make a request type need approval from one approver or from an ordered chain of approvers.

In a chain, each approver is asked only after the one before approves. A denial at any step closes the request.

Agents can also send any open request to an approver they choose.

Parallel approvals, where several people decide at the same time, are not supported.

An approver can delegate to a named user for a date range. While the delegation is active, every approval routed to the approver goes to the delegate.

The service level agreement (SLA) clock pauses during approval only if the matching SLA policy lists Waiting on approval as a pause status. Pause statuses are set per policy.

A new workspace starts with four SLA policies, one per priority. All four pause on Waiting on requester and Waiting on approval.

Step by step

  1. 01

    Require approval on a request type

    Turn on approval for a request type and list who decides, in order.

    • Each approver is asked only after the one before approves
    • Empty chain: each request goes automatically to a single approver
    • That approver is the first eligible employee, or an admin if there is none
    • Active delegations are honored either way
    1. Admin → Settings → Request types
    2. Open the type → turn on Approval required
    3. Approval chain → add approvers in the order they should decide
  2. 02

    Set delegation

    Send the approvals routed to you to someone else for a date range.

    • While the delegation is active, every approval routed to you goes to your delegate
    • Delegation applies across the whole organization; it cannot be limited to a team
    1. Portal → Approvals → Forward
    2. Choose the delegate
    3. Choose the date range
  3. 03

    Decide an approval

    Approvers find the request in their inbox and on the Approvals page in the app, then approve or deny it.

    • Each decision writes an audit entry
    • Approving the final step returns the request to In progress or Waiting on requester, if it was in one before
    • Otherwise the request goes to Triaged
    • Denying at any step closes the request
  4. 04

    Run automations on decisions

    Run actions when a decision is recorded, with the Approval decided trigger.

    • The rule fires on both approve and deny
    • Conditions cannot branch on the outcome
    1. Admin → Settings → Automations → New automation
    2. Trigger → Approval decided

Good to know

  • When a manager force-resolves a request, any approval still pending on it is denied.
  • To keep the SLA clock running during approval for urgent work, give that priority its own SLA policy with no pause statuses.