Start from observed traffic

Monitoring records the policy result while the integration continues with the call. Use it to understand the actions an agent requests and design authority boundaries from real inputs.

Build policies from requests

1. Connect the agent and select Monitoring in the plugin or application.
2. Open Decisions, filter to that agent, and inspect the action and context.
3. Create a policy from a relevant decision. Keep the fields needed to express the control.
4. Add tests for allowed, approval-required, blocked, and out-of-scope requests.
5. Publish the policy, assign it to the agent, and save.
6. Review new Monitoring decisions to see the effect of the assigned rules.

Monitoring still records decisions and can affect counters. If an action runs, report its outcome. A recorded Block in Monitoring means the policy would have stopped the action under enforcement; it does not mean the action was stopped.

Switch to enforcement

Review the agent’s When no policy matches setting. New agents default to Allow. If your rollout requires explicit permission for every operation, choose Block and check coverage before enabling enforcement.

Switch the plugin or application to Enforcing. Changing policies in Actera does not change the caller’s mode.

Verify all three effects through the actual integration. A blocked call must not reach the provider. An approval-required call must pause until an eligible reviewer responds. An allowed call should produce the expected outcome report.

Use Needs approval to review exceptions and Inspect a decision to compare authority with what actually ran.