Approve Agent Actions
Review generated UI actions, approval prompts, and tool activity before allowing an agent to make changes.
Some agent responses can include generated UI blocks or approval prompts for actions. Review these carefully before allowing the agent to change records, send messages, create work, or use connected tools.
Review Before Approval
Before approving an action, confirm:
- the target record is correct;
- the action matches your intent;
- the proposed data is complete;
- customer-facing copy is safe;
- finance, HRM, files, or integration changes have the right owner;
- the action will not duplicate existing work.
If anything is unclear, reject the action and ask the agent to explain or revise the proposal.
Generated UI Blocks
Agent replies may render structured UI such as buttons, tables, or summaries. Use them as review tools. Do not assume a generated table or button has the same authority as the source record.
Open the source record when the action affects status, owner, amount, due date, recipient, access, or customer communication.
Approve Or Reject
Approve only when the action is correct and you are responsible for the result. Reject when the action targets the wrong record, lacks context, duplicates work, uses unsafe wording, or should be handled manually.
After approval, review the result in the destination record or connected app. If the action failed, inspect the thread status and related tool activity before trying again.
Escalate Repeated Actions
If the same approved action becomes routine, consider whether it should become an AI worker or workflow with explicit review steps. Repeated manual approvals are useful evidence for designing a safer repeatable process.