Review approvals
Use Require approval when an action should leave the agent’s autonomous authority and wait for a human decision.
Set up an approval group
Section titled “Set up an approval group”A workspace owner or administrator opens Approval groups, creates an active group, and adds eligible workspace members. Select that group in the policy rule that requires approval, then test and publish the policy.
The group page shows membership and the policies that request it. Groups managed through your identity provider follow that provider’s membership controls. A group used by a published policy cannot simply be deactivated; update the policy’s approval requirement first.
Review eligibility is checked when the person responds. An administrative role or possession of an agent key is not a substitute for eligible group membership.
Review a request
Section titled “Review a request”Open Needs approval and inspect the agent, action, arguments, policy reason, and any expiry shown.
Approve only the operation captured in that request. Reject it with a reason when it should not proceed. If its authorization has expired, submit a new request so current authority and usage can be evaluated.
After approval, the integration must continue the action. Decision status and execution outcome remain separate: look for a completion report before treating the operation as finished.
Notify the right reviewers
Section titled “Notify the right reviewers”Open Notifications to see available channels and configure destinations for each active approval group.
- Slack: connect the workspace, invite Actera to the relevant channel, and send a test.
- Email: use the email destinations available for your workspace and send a test.
- Webhooks: configure HTTPS endpoints when included in your plan. Protect the signing secret and verify signatures in the receiving service.
Assign destinations to the group and save. Channel availability depends on your workspace configuration and plan. Requests still wait in Needs approval even if a notification is delayed or a destination is unavailable.
Receiving a message does not grant approval authority. Keep each group’s membership and notification destinations aligned, and verify the complete flow with a controlled request.