Policies & stages

How policies, stages, and routing modes shape a workflow.

A policy is the reusable blueprint for approving a kind of request. It is scoped to a target model (e.g. a document type) and made of ordered stages.

Stage modes

Each stage declares how its assignees combine:

• any_of — one approval completes the stage.
• all_of — every assignee must approve.
• in_order — assignees act one after another.

SLAs & escalation

A stage may carry an SLA window. If it lapses, pending assignments escalate to a fallback role so work never silently stalls.

Conditional routing

Policies can carry rules that adapt the stages per request — auto-approve, skip a stage, or add a stage — based on the request’s data. This keeps one policy flexible instead of many near-duplicates.

Delegation & external approvers

Approvers can delegate during leave (scoped and time-bounded), and a stage can route to people outside the org through a single-use magic link plus a one-time code.