Skip to content
Olympusx AIOlympusx AIOlympusx AI documentation

Human approval

Human approval puts a person between an agent and an action you do not want it to take alone. You mark the tools that need a decision; when an agent asks for one, Olympusx AI holds the call, and an Admin or Reviewer approves it or rejects it. The tool runs only on approval. This page explains how holding works and what it guarantees.

What waits

Section titled “What waits”
  • Tool calls you mark. On each agent, each tool it is granted either Runs without asking or is Held until a person approves. The choice belongs to the agent, so the same tool can run freely for one agent and wait for another.
  • Actions a Security investigation proposes. When an investigation reaches a verdict, the actions it suggests wait for a person in the same way. See Actions and approvals.

What happens to a held call

Section titled “What happens to a held call”
  1. The model asks for a held tool. Olympusx AI does not call it.
  2. The call is recorded with the tool, the agent, its arguments, who asked and when. The run stops with the outcome Waiting on approval.
  3. Every Admin and Reviewer in the tenant is notified, and the call appears in Operate › Approvals.
  4. A person reads the call and its arguments, and decides:
    • Approve and run runs the tool with exactly the arguments shown, and the agent carries on from where it stopped.
    • Reject needs a reason, runs nothing, and the reason goes back to the conversation.
  5. The person who asked sees the answer arrive: an assistant’s conversation waits and updates when someone decides.

A call nobody answers within 24 hours expires and never runs.

Who decides

Section titled “Who decides”
Role Sees the call Reads its arguments Decides
Admin Yes Yes Yes
Reviewer Yes Yes Yes
Auditor Yes No No
Builder, End user No No No

The person who builds an agent is not, by role, the person who approves its calls: a Builder cannot decide. In a small tenant an Admin can do both.

What it guarantees

Section titled “What it guarantees”
  • A held tool never runs unapproved. There is no timeout that lets it through: an unanswered call expires unrun.
  • What is approved is what runs. The arguments the approver reads are the arguments the tool receives.
  • The decision is on the record. Who decided, when, and the reason for a rejection are kept with the run and in the audit log.
Section titled “Related”