Scope
This guide covers setup & configuration for Agent Approvals. Availability depends on your tenant package, role and configured providers.
Purpose
Keep proposed AI work behind explicit human decisions.
Define which agent outputs require which reviewer.
Before you start
Correct tenant and project selected
Required source or provider is available
An accountable owner is identified
Test data can be separated from live activity
Procedure
- Open the correct tenant and confirm the project or workspace that owns this capability.
- Define which agent outputs require which reviewer.
- Connect or select the required source records and owners.
- Create a safe test configuration before using live customer or campaign data.
- Measure acceptance, revisions, rejections and follow-through.
- Preserve reviewer, decision, evidence and timestamps.
Verify the result
Measure acceptance, revisions, rejections and follow-through. Confirm that the intended record, state, run or report is visible to another authorised operator and that its next owner is clear.
Completion checkpoint
The capability is in the intended state, evidence is current, exceptions are owned and the next action can be understood without a separate status message.
Controls and limitations
Preserve reviewer, decision, evidence and timestamps. Predictive, attribution and recommendation outputs support operator judgement; provider and data limitations remain relevant.