AI agent permissions and approvals: how to let agents act safely
An agent's permissions are a job description written in advance. The platforms differ less in whether they offer approvals than in where those approvals apply and what record they leave.

Contents
Letting an agent act is a delegation, and delegation in a company usually comes with limits: a spending authority, a list of who signs what, a record of what was done. The same three controls apply to AI agents. What varies between platforms is how precisely each can be set, and whether it holds in every place the agent works.
Why the controls matter
Security bodies and incident data point the same way. OWASP lists excessive agency among the top risks for AI applications and traces it to three causes: excessive functionality, excessive permissions and excessive autonomy. Its recommended mitigations are least privilege, complete mediation and human approval for high-impact actions1. IBM's 2025 study found that 13% of organisations reported a breach of an AI model or application, and that 97% of those lacked proper AI access controls2. NIST's AI Risk Management Framework organises the same work into four functions: govern, map, measure and manage3.
The three controls
1. Scope: what the agent can reach. Which records and which tools. The narrowest useful scope is the safest. Some platforms make this hard: Lindy notes that connecting a tool enables all of its actions at once, and that one guardrail covers every account under an integration4.
2. Approval: what waits for a person. Expressed as a rule the company sets, not a judgement the agent makes. The strongest rules are written in business terms, such as a purchase order over $15,000 or a credit over $500, which is how OpenLazarus describes its per-teammate limits5.
3. Record: what is logged, and where. Every action, against the record it touched, readable by the people accountable for it.
How the platforms implement approval
| Platform | Where approval is set | Where the reviewer answers | Notable limit |
|---|---|---|---|
| OpenLazarus | Limits per AI teammate65 | Inside the company's system | Staff roles not documented publicly |
| Relevance AI | Each agent-to-tool or agent-to-agent link7 | Task view; escalation by Slack or email | RBAC and audit logs on Enterprise |
| n8n | All tools or selected tools8 | Chat, Slack, Teams, email, WhatsApp and more | Audit logging on Enterprise |
| Lindy | Per integration4 | Buttons in the Slack thread | Applies in shared Slack threads only |
| Zapier Agents | Per tool9 | Messaging app; Human in the Loop step by email or Slack10 | Product and billing in transition |
| Dify | Human Input workflow node11 | Web app or email | Times out after three days by default |
| Copilot Studio | Multistage approvals in agent flows12 | Teams, Outlook, Power Automate | Preview, not for production use |
Two details deserve attention. Lindy's guardrails do not apply in its web app, Slack direct messages or text messages4, so a request made in those channels is not held for approval. And Copilot Studio's multistage approvals, though the most elaborate, are still a preview feature12; its strength lies in tenant-wide governance (data policies, Purview audit logs, Entra identities for agents) rather than in per-action approval13.
Where the log lives
An approval is only as useful as the record it leaves. Audit logs are an Enterprise feature at Relevance AI, Lindy, n8n and Dify14151617, start on the Team plan at Zapier with six months of retention18, and run through Microsoft Purview in Copilot Studio13. Where an agent acts in another company's app, the agent platform's log and the app's own history are separate, and reconciling them is the reviewer's job. OpenLazarus logs every teammate action in the same system that holds the records5.
A permissions plan for a first agent
- Write the job description: the records the agent may read, the records it may change and the tools it may use.
- Set approval on every write and every external message for the first two to four weeks.
- Define the thresholds that will keep approval permanently: money, terms, dates promised to customers, anything above a set value.
- Test every channel the agent works in, and confirm the approval rule applies in each.
- Name the approvers and a backup, and decide what happens if no one answers. Dify's default, for example, is a three-day timeout followed by a separate branch11.
- Review the log weekly, then relax rules only for actions with a clean record.
The end state looks like a well-run finance team: the agent acts freely below a limit, a named person approves above it, and the log answers the question "who did this, and on whose authority" for every record.
Questions buyers ask
What is human-in-the-loop for AI agents?
A step where the agent prepares an action and waits for a person to approve, reject or correct it before it runs. OWASP recommends it for high-impact actions.
Should every AI agent action need approval?
Not for long. Start with approval on every action that writes or sends, then remove the requirement for actions that have proved reliable and are easy to undo. Keep approval permanently for money, terms and anything sent outside the company above a set value.
Which no-code agent platforms have audit logs?
Most offer them only on top plans. Audit logs are Enterprise-only at Relevance AI, Lindy, n8n and Dify, start on the Team plan at Zapier and run through Microsoft Purview in Copilot Studio. OpenLazarus logs every teammate action where staff can see it.
Sources
- LLM06:2025 Excessive Agency. OWASP Gen AI Security Project. Accessed 8 Nov 2026.
- IBM report: 13% of organizations reported breaches of AI models or applications, 97% of which reported lacking proper AI access controls. IBM Newsroom, 30 Jul 2025. Accessed 8 Nov 2026.
- AI Risk Management Framework. NIST. Accessed 8 Nov 2026.
- Integrations. Lindy Docs. Accessed 8 Nov 2026.
- AI for wholesale and distribution: orders, stock, suppliers. OpenLazarus. Accessed 8 Nov 2026.
- Questions about OpenLazarus (FAQ). OpenLazarus. Accessed 8 Nov 2026.
- Approvals and escalations. Relevance AI Docs. Accessed 8 Nov 2026.
- Human-in-the-loop for tools. n8n Docs. Accessed 8 Nov 2026.
- Zapier Agents is now AI by Zapier. Zapier. Accessed 8 Nov 2026.
- Add approval steps to your agent’s instructions. Zapier Help Center, 1 Oct 2026. Accessed 8 Nov 2026.
- Human Input node. Dify Docs. Accessed 8 Nov 2026.
- Multistage and AI approvals in agent flows. Microsoft Learn, 15 Oct 2026. Accessed 8 Nov 2026.
- Security and governance in Copilot Studio. Microsoft Learn, 24 Sep 2026. Accessed 8 Nov 2026.
- Pricing. Relevance AI Docs. Accessed 8 Nov 2026.
- Pricing. Lindy. Accessed 8 Nov 2026.
- n8n plans and pricing. n8n. Accessed 8 Nov 2026.
- Dify pricing. Dify. Accessed 8 Nov 2026.
- Zapier pricing. Zapier. Accessed 8 Nov 2026.
Updated 8 Nov 2026: First published.