Guides
How to approve AI actions safely (November 2026)
For anyone who wants an AI to do real work without giving up control. After reading, you can set approval rules, review requests quickly and keep a record of decisions.
In short
- Separate actions that only read from actions that change something outside your computer.
- Require approval for anything that sends, publishes, spends or deletes.
- Keep a record of every decision, including refusals, so you can review the rules later.
What it is
Approving an AI action means that a person sees exactly what an assistant wants to do and says yes, no or "change this" before it happens. Safe approval has three parts: a clear description of the action, a rule that decides which actions need a person, and a record afterwards.
How to do it
- List the actions the assistant could take. Group them as read, draft, send, publish, spend and delete. The first two are low risk; the last four affect other people or money.
- Decide the default. If no rule covers an action, refuse it. A default of "allow" turns every forgotten case into a risk.
- Make the request readable. The person must see the real content: the full text of the e-mail, the exact amount, the recipient. A summary that hides details is not an approval.
- Allow editing, not only yes or no. Most requests are nearly right. An edit option stops people from approving imperfect work just to move on.
- Plan for mistakes. Some actions can be undone in a short window; some, such as a sent e-mail, cannot. Treat irreversible actions with the strictest rule.
- Review the record monthly. Look for requests you always approve (candidates for a looser rule) and ones you always refuse (candidates for removal).
How Growth OX helps
In Growth OX, posts, replies, e-mails, publishing and spending wait for your approval; you can approve, edit or refuse. Rules decide which kinds of request reach you as an approval card, and with no rules the assistant's requests are refused. Each decision is recorded as allowed, refused, approved, denied or expired. Details are in the approvals documentation.
The Do it button shows what will be done, lets you edit or ask for a revision, and acts only after you approve. After a run you can undo for a short time on the card, and after that from History. A sent mail cannot be taken back. With phone approval, a paired phone allowed to approve can see approvals and confirm with fingerprint or screen lock.
Limits: the approval record shows decisions, it does not make a bad decision good. Rules are only as careful as the person who writes them.
Other ways to do it
| Option | Good for | Limit |
|---|---|---|
| Approve everything manually | Low volume | Fatigue sets in; people click through |
| Allow everything, review afterwards | Reversible, low-stake tasks | Harm happens before review |
| Rules per action type | Mixed workloads | Needs maintenance as work changes |
| Two-person approval | High-stake spending | Slow; requires a second person |
| Approval cards with rules (Growth OX) | One owner, many small decisions | Depends on rules you set; sent mail is final |
Where to go next
Write your list of actions today and mark each as read, draft, send, publish, spend or delete. Set the refuse-by-default rule first, then open actions one at a time. For the privacy side of the same decision, read how to keep business data on your computer.
FAQ
Does approval slow work down?
Slightly, but review takes seconds when the request shows the real content. Rules reduce how many requests reach you.
What happens if I ignore a request?
Expired requests are recorded as expired. Nothing runs without a decision.
Can I approve from a phone?
In Growth OX, a paired phone can be set to approve or view only, and you can remove it at any time.