When to use an approval workflow
Use an approval workflow when an event should pause for a decision before the next action. Examples include:
Review a purchase order before it advances.
Approve a payment request before sending payment.
Require a second review above an amount limit.
Review vendor onboarding information before continuing.
Available recipes and actions depend on the products enabled for the workspace.
Create a flow from a recipe
Select Flows in the workspace navigation.
Select New Flow, or press N while you are not typing in a field.
Choose a released recipe from Start a new flow.
Available recipes can include Purchase Order, Payment Request, Send Payment Approval, and Vendor Onboarding Review. Saturation creates an editable copy of the recipe for your workspace.
Each flow starts with a Trigger block. Select it to review the event that starts the flow and, when available, limit it to selected projects.
Add rules and approval steps
Use the block palette to build the path after the trigger.
Condition routes a run by amount, project, vendor, or another supported field.
Approval requests a decision.
Wait pauses the run for a set duration.
Notify sends a message.
Send Payment sends an approved request when the trigger and workspace support it.
End completes or rejects the run.
Connect the output of one block to the next block on the canvas. Connect both the approved and rejected outputs of an Approval block so each decision has an intentional result.
For a sequential review, connect one Approval block's approved path to another Approval block. This keeps the order visible on the canvas.
Configure approvers
Select an Approval block, then configure:
Approvers: Choose specific workspace members, Any Admin, or Any Editor. A role choice includes that role or higher.
Requirement: Choose Any approver, All approvers, or At least N approvers.
Auto-approve submitter: Leave this on to count an eligible submitter automatically. Turn it off when the submitter must make a separate decision.
Path labels: Rename the approved and rejected paths when terms such as Signed off and Sent back are clearer for the team.
With Any approver, the first response decides the step. With All approvers, every approver must approve and one rejection rejects the request. At least N approvers completes the step after the required number approves.
Route requests by amount or other criteria
Add a Condition block before the Approval block when different requests need different reviewers. Create a path for each rule, then connect each path to its approval step.
The Approval block also shows an Amount thresholds editor marked Preview only. Those bands do not change live approvals yet. Use Condition blocks for active amount routing.
Publish the flow
Review the trigger, block settings, and connections.
Select Publish for a new flow or Save changes for an active flow.
Review the publish check. Select a listed problem to return to that block.
Publish after all blocking problems are resolved.
The editor shows Active when the published flow has no unpublished changes. New trigger events start runs against the active flow. Publishing does not create approval tasks for records that were submitted before the flow became active.
Review and decide approval tasks
Approvers work from Tasks in the workspace navigation.
All Tasks shows the workspace's open approval requests.
For me shows the open requests the current user can decide.
Select a row to review its purchase order, payment, or flow run. Choose Approve or Reject. A rejection reason is optional and is recorded with the decision. You can also select several actionable rows and use the bulk approval controls.
Tasks contains open requests only. After a decision removes the request from the open queue, use the source record's activity or the flow run for history.
Monitor flow runs
Open Flows and select Runs to review executions. Open a run to see its current step and path. Use filters, search, and the date range control to narrow the list.
If a run is waiting, confirm that the Approval block has an eligible approver and that the approver still has access to the workspace. If a flow cannot publish, open each problem in the publish check and complete the missing configuration or connection.
FAQs
Can I require approval from both a department lead and an admin?
Yes. Put both in one Approval block with All approvers, or use two connected Approval blocks when the reviews must happen in order.
Can viewers or commenters approve?
No. The approver picker excludes roles that cannot act on approval tasks.
Can an owner override an approval from the flow editor?
No. Decisions are made from the open task or the source record's approval controls. The flow editor defines the path but does not bypass an active approval step.
What should I do after a rejection?
Review the recorded reason on the source record, correct the request, and use that record's available resubmit action. The exact action depends on whether the request is a purchase order, payment, or onboarding review.