Glossary · 6 · Quality, risk and governance
Action approval gate (AI agent)
Also known as: Approval gate, Human approval step, Confirmation step
German: Freigabeschritt für Agentenaktionen
An action approval gate is a point in an AI agent’s workflow where a proposed action of a defined class — typically irreversible, high-impact or outside routine limits — is held until an authorized person reviews and approves it, with the decision recorded.
- Intermediate
- Technical project managers
- Technical writers
- Developers
In one sentence
An action approval gate holds an AI agent’s high-impact or irreversible action until an authorized person approves it — and records who decided.
Example
A purchasing agent drafts orders freely, but orders above EUR 10,000 and any order to a new supplier wait in an approval queue for the buyer.
Explained in context
This term is a station of a mini course
- When an AI agent crosses the line: detect, contain and restore operationsStation: Approval gates for irreversible actionsStart the course
Context cards connect this term with others to answer one question. Also in British English and German.
How it applies
- Gate classes, not every step: Gates belong where an action can't be undone or costs a lot when wrong: deleting, paying, publishing, sending to many recipients, changing a recipe or setpoint, starting a fleet update. Gating everything produces rubber-stamping.
- The approver sees the action, not the chat: Show what will change, where, and what the agent based it on. OWASP warns that agents can exploit human trust (ASI09); a gate that only shows the agent's own summary invites approval of a manipulated action.
- Recorded decision: Who approved what, when, on which evidence — this record is part of the audit trail and is what restoration and reporting rely on later.
- Relation to the AI Act: For high-risk AI systems, human oversight requires that people can decide not to use the output, override it and interrupt the system. A gate is one way to make that real; naming it doesn't establish compliance.
- In OT and on machines: The gate for a setpoint or recipe change sits where operators already release changes — in the HMI or under management of change, not in a chat window.
Why it matters on your learning path
- Technical writers: Write the approver's instructions: what to check before approving and when to refuse.
- Technical marketers: “Human approval for critical actions” is a concrete, checkable promise.
- Technical project managers: Define the gate classes and the approvers before go-live.
- Developers: Make the gate a hard stop in the orchestration, not an optional prompt.