# Where a human should approve

Guide, 8 Nov 2026, read 8 Nov 2026

**The short answer.** A human should approve at four points: before a record is written, before a message leaves the system, before money or access changes, and before a process starts for a group. Six platforms state an approval step for agent actions on 8 Nov 2026; the wording differs, and the difference is which of the four gates it covers.

## The four gates

- Before a record is written: a new hire's fields, a policy assignment, a manager change. Shapes's directory built with an agent writes nothing until Approve.
- Before a message leaves: an offer letter, a Slack nudge, an email to a leaver. BambooHR's agentic workflows 'still go through the appropriate person before they're applied or sent'.
- Before money or access changes: a salary line in a comp cycle, a device, an app. Gusto's MCP returns every write for confirmation before anything moves.
- Before a process starts for a group: a comp cycle for forty people, an onboarding wave. Shapes shows who is in a cycle before it launches, with the count of included and excluded people.

## What the vendor sentences cover

| Vendor sentence | Gate it names |
| --- | --- |
| Shapes: 'Nothing goes live until you say so.' | All four, as a blanket rule; the pre-launch count covers the group gate. |
| Rippling: 'Before it takes action, it gets your approval.' | Record and action gates; the group gate is not named. |
| Factorial: 'It asks before it acts.' | Action gate, under each person's permissions. |
| Workday: review or approve sensitive actions before anything changes; sandboxed what-ifs. | Money, access and group gates; the record gate is a permission matter. |
| Gusto: 'Every write comes back to you for confirmation before anything moves.' | Record and money gates, through the MCP connector. |
| HiBob, Humaans, Personio, Deel: partial. | A confirmation in some tools, letters 'ready for approval', a named owner, a human in the loop in the terms. |

## Where approval is too much

An agent that asks before every policy answer is an assistant with a delay. The answers column needs the sensitive-field rule, not an approval; the approval belongs to writes, sends, money, access and groups. A vendor whose approval step is a confirmation dialog on every read has built friction, not control.

## Sources

- Shapes agents: https://shapes.co/agents (read 8 Nov 2026)
- Shapes: who is in a cycle before launch: https://shapes.co/releases/see-who-s-in-a-cycle-before-you-launch (read 8 Nov 2026)
- Rippling AI: https://www.rippling.com/platform/ai (read 8 Nov 2026)
- Workday Sana: https://www.workday.com/en-us/artificial-intelligence/workday-sana.html (read 8 Nov 2026)

Last reviewed 8 Nov 2026. Canonical: https://bestaiagentsforhr.com/guides/where-a-human-should-approve/
