Approvals and approvers

An approval pauses a sensitive action until a designated person signs off. Use approvals when an action — like issuing a purchase order above a spend threshold — needs a second set of eyes before it proceeds.

How approvals work

When an action meets the conditions you’ve set, Fiddle holds it in a pending approval state instead of completing it. The assigned approver is notified, reviews the request, and either approves or rejects it.

State	Meaning
Pending	Waiting for an approver to act; the action is on hold
Approved	Approver signed off; the action proceeds
Rejected	Approver declined; the action is blocked with a reason

Approvers

An approver is a user you authorize to review requests. You can name a single approver or several — when more than one is set, you decide whether any one of them or all of them must approve.

The person who triggers an action usually cannot approve their own request. Assign at least one other approver so requests don’t get stuck.

Where approvals apply

Common gated actions include issuing high-value purchase orders, releasing work orders, and shipping above a credit limit. Each approval is tied to a condition you define, so routine work is never slowed down — only the requests that match your rules.

Next steps

Ready to put one in place? See set up an approval workflow.