Pending Actions

When an action policy is in place for an operation, performing that operation doesn't happen immediately — it creates a pending action instead, which sits waiting for review until enough of the policy's authorized reviewers approve it.

How review works

Every authorized reviewer for the policy can approve or decline a pending action. A reviewer's vote can be changed — approving removes you from the decliners, declining removes you from the approvers.
The pending action is carried out automatically as soon as it has at least as many approvals as the policy's minimum required reviewers, and nobody has declined it. If someone declines it after it already has enough approvals, it stays blocked until the decline is withdrawn (or the pending action is deleted).
Only the admins named as authorized reviewers on the governing policy can approve or decline. Approving or declining requires the Admin role in your organization.
Non-admin users only ever see the pending actions relevant to them (the ones they triggered), and can't see who else has approved or declined — a decline just shows as "Declined by Reviewer" rather than a username. Admins see every pending action, including who approved and declined it.
The user who triggered the governed operation can cancel it at any point by deleting their own pending action, without needing reviewer approval.

Listing pending actions

Using the web interface

Open Administration > Action Policies > Pending Actions. Admins see every pending action in the system; other users see only the ones they triggered.

Using the CLI

action_policies pending_actions list [<id>] [--onlyMyPendingActions] [--waitingForMyReview]

Option	Description
`<id>`	Filter pending actions by ID.
`--onlyMyPendingActions`	Show only pending actions relevant to you (always applied for non-admin users, regardless of this flag).
`--waitingForMyReview`	Show only pending actions that are still awaiting your review as an authorized reviewer.

Examples

List everything waiting on your review as an admin:

action_policies pending_actions list --waitingForMyReview

List only the pending actions you personally triggered:

action_policies pending_actions list --onlyMyPendingActions

Approving a pending action

Using the web interface

Open Administration > Action Policies > Pending Actions.
Select the pending action (or select multiple at once) and click Approve.

Using the CLI

action_policies pending_actions approve <id>

Option	Description
`<id>`	The ID of the pending action to approve.

Example

action_policies pending_actions approve 142

Declining a pending action

Declining blocks the pending action from completing, even if it already has enough approvals — it stays blocked until the decline is withdrawn or the pending action is deleted.

Using the web interface

Open Administration > Action Policies > Pending Actions.
Select the pending action (or select multiple at once) and click Decline.

Using the CLI

action_policies pending_actions decline <id>

Option	Description
`<id>`	The ID of the pending action to decline.

Example

action_policies pending_actions decline 142

Deleting a pending action

Deleting a pending action cancels the underlying request — it does not perform it, no matter how many approvals it had collected. Non-admin users may only delete pending actions they personally triggered; admins may delete any.

Using the web interface

Open Administration > Action Policies > Pending Actions.
Select the pending action and click Delete.

Using the CLI

action_policies pending_actions delete <id>

Option	Description
`<id>`	The ID of the pending action to delete.

Example

action_policies pending_actions delete 142

See also: Action Policies · Recycle Bin (where an approved volume deletion ends up, if a recycle bin is configured)