People · Approval
Turn a task into an approval gate
On the People tab, open Approval and switch on Enable approval. The task now requires explicit sign-off before it counts as complete. Set the mode (any approver or all approvers), the rejection behavior (send back for rework), the list of approvers, and optional requirements and timeout.
The approval settings
- Mode (ANY / ALL)
- ANY: one approver is enough. ALL: every listed approver must approve. Use ALL for segregation of duties.
- Rejection behavior
- What happens on a reject, typically Sent back for rework so the assignee fixes and resubmits.
- Approvers
- The specific people (or group) who can approve. Keep approvers distinct from the doer for real separation.
- Requirements
- Optionally force a comment or a signature on approval, so the decision is documented and attributable.
- Approval timeout
- Auto-escalate or act if an approval is not answered within a set time, so decisions do not stall.
For compliance-sensitive steps, combine ALL-approver mode with a required comment or signature. You get a documented, attributable decision baked straight into the audit trail.
Common questions
What is the difference between required and approval?
A required field just has to be filled for the task to complete. An approval adds a second person who must explicitly sign off on the completed task before the Flow proceeds.
Can an approval require a signature?
Yes. Under requirements you can demand a signature on approval, which is the basis for legally meaningful sign-offs. The signature is captured and stored on the record.
What happens when an approver rejects?
The rejection behavior decides. The default sends the task back for rework, so the assignee addresses the feedback and resubmits for another review.
