Approvals and human-in-the-loop
What you control
Customer-facing controls include:
- Tickets and approvals for actions that need a human decision
- Policies such as message filters that constrain what agents may do
- Automation settings in the portal that decide when approval is required vs when work may proceed
Keep automation settings conservative until you trust the agent’s scope.
Agent acted without asking
If an agent continued when you expected a pause:
1. Open the session and find the last approval or policy decision in the UI.
2. Check workspace policies and approval / automation settings for that agent or client.
3. Tighten settings so sensitive actions require approval again.
4. Review who has permission to change those settings.
Do not rely on undocumented engineering environment variables. Use only the controls visible in the portal and
documented for operators.
Tips
- Treat broad auto-approve style options as high risk for production clients.
- Record which policy applied when filing a Support request.
