Two-person approval for AI agent actions

Some agent actions are too big for one person's click. How two-person approval works for AI, when to require it, and how to set it up.

· 5 min read

Banks have long required two people to sign off a large transfer. The reason is not that one person is careless. It is that one person can be tired, rushed, mistaken or pressured, and two independent people are rarely all four at once. The same holds when the one asking is an AI agent.

When one click is not enough

Most agent actions need no person at all, and most of the rest need one. Two is for the short list where a single wrong yes is expensive and hard to undo:

  • Payments or refunds above a threshold you would notice.
  • Deleting production data, or anything without a backup.
  • Changing who has access: permissions, keys, admin roles.
  • Messages to everyone at once: all customers, a public post, a press contact.

Keep the list short. If two people are asked about everything, both stop reading, and the second signature means nothing.

How it works

Two-person approval is a property of an “always ask” rule: it can need two or three different people. The agent asks exactly as before; nothing in its code changes.

  • The request stays pending until enough different people have approved. Each person counts once, however often they click.
  • One denial from anyone stops it at once.
  • When several rules cover a request, it needs the most approvals any of them asks for.
  • The record lists everyone who approved, so “who allowed this?” has two names for an answer.

While it waits for the second person, the agent sees:

{
  "status": "pending",
  "allowed": false,
  "approvals_needed": 2,
  "approvals": [
    {
      "user_id": "8d0c…",
      "by": "ada@example.com",
      "at": "2026-11-13T09:14:02Z",
      "note": null
    }
  ]
}

allowed becomes true only with the last approval needed. An agent that acts on allowed, as it should, needs no change to support this.

Set it up

  1. Invite at least one colleague to the workspace under People; see Teams.
  2. Under Rules, write “always ask” for the action, such as payment.*, with a limit such as above €1,000, and choose two people.
  3. Turn on Slack notifications, so the second person hears about it without watching the inbox.
  4. Give those requests a time limit long enough for two people to see them, such as a few hours, with ttl_seconds.

Things it deliberately does not allow

  • An approval that needs more than one person cannot be remembered from the inbox. Remembering would turn a two-person rule into a one-person habit.
  • An agent cannot be one of the people. Its key can ask; it can never approve, its own request or anyone else’s.
  • Who approved comes from each person’s sign-in, never from the request, so nobody can approve in a colleague’s name.

Two-person approval works best as the top of a ladder: rules let small amounts through, one person decides the middle, and two decide the top. The spending limits article builds that ladder for payments.