Set approval rules

Use this to make some calls wait for a person with authority before they run, such as payments, deletes or anything sent to customers. Approval rules come with the Team plan. Owners and team leads set them on the Guardrails page.

Approvals sit on top of confirm before changes, which is on in every workspace: confirm asks the person who asked, approval asks someone else.

#Add a rule

1. Open Team, then Guardrails in your workspace.
2. Add a rule for the app or action you want to control.
3. Choose its mode:
   • Enforced (refused by ahel): ahel refuses the call.
   • Advisory (told to the AI): the AI is told the rule, and the call is not blocked.
4. To make a call wait for a yes, use the rule type that needs approval by an owner or team lead.

The same page holds the workspace's Confirm before changes switch, which only the owner can change.

#What happens when a call needs approval

1. Nothing runs. The person's AI is told the call is "Held for approval" and who has to say yes.
2. On the team page, owners and team leads see the calls waiting for a yes, with what was asked.
3. They press Approve or Send decline.
4. After an approval, the AI makes the same call with the same values again, and it runs once.

Time limits: a held call waits up to a day, and an approval is good for one run within an hour.

#Who approves

Owners and team leads. Members can ask but not approve. Give the team lead role to the people who should approve: see Set up a team.

#Find the record

• Activity lists every call and every key use, with whether it completed.
• Team audit on the team page keeps the workspace's log of who did what. By default it keeps 30 days and does not store call contents.