Keep people in control
Require two people for the riskiest calls
Make the most consequential actions a shared decision rather than one person's.
Ask for up to five different people to approve each call to a tool your organization gates.
What this changes for your team.
Beside Require approval on an integration's tools, Approvers needed sets how many different people must approve each call - up to five. The call waits until that many have approved; any one of them can reject it, which stops it at once, and the same person never counts twice. Approvers are whoever the domain's approval policy admits, and when a call runs on one person's own credentials that person must be among them.
How it works in practice.
- 01
Open the integration's Tool approvals, require approval on the tool, and choose how many approvers it needs.
- 02
Each approval is recorded as it arrives; the inbox shows the progress, for example 1 of 2 approvals.
- 03
The call runs only once the last approval lands; a rejection or the deadline ends it without running.
What you can plan around.
What to expect, including limits that matter to your team.
The required count is fixed when the call pauses, so changing it later never alters a decision already in progress.
Every approval is an audit row of its own, and the final one names every approver.
An agent or flow that calls the gated agent cannot stand in for one of the people.
Bring one real process
See how Yekar.AI fits the way you work.
Start with a job your team already owns, plus the tools and decisions around it.
Get started