Approve or Reject Pending Actions
Review and action AI- or automation-requested operations that are queued for human sign-off before they run.
Overview
Whenever an autonomous action's policy mode is set to Suggest or Approve (rather than Auto), Plenix doesn't run it — it queues an Action Run and waits for a human to approve or reject it. The Autonomy Approvals page is where that review happens.
Accessing the page
Go to Autonomy → Approvals in the sidebar (only visible on Enterprise plans). Admins are also notified in-app whenever a new action is queued.
Reviewing a queued action
Each row in the table shows:
- Action — the action key, e.g.
diag.network-connectivityorai.triage - Risk — colour-coded badge: green (read), blue (low), yellow (medium), red (high)
- Requested By —
ai,rule, oruser - Queued — when the request came in
Click View intended action to expand the row and see the full transcript — exactly what the action intends to do and any input parameters — before deciding.
Approving or rejecting
- Click Approve on a row to let it run immediately. The action executes, and the result becomes visible in the run's transcript.
- Click Reject to discard it. Rejected runs are kept for audit purposes but never execute.
Bulk actions
Select multiple rows with the checkboxes on the left — an Approve N / Reject N action bar appears above the table so you can clear a backlog in one click.
If the queue is always empty
That's expected if every action key you use is configured for Auto mode (the default for all read-only diagnostics) — Approvals only fills up when a policy is explicitly set to Suggest/Approve, or when a higher-risk action requests something that always needs sign-off. See Configure Autonomy Policies to change a policy's mode.
Where to go next
Was this article helpful?