nano SIEM
SOAR

Approvals

Supported in:Self-hosted

Make a person sign off before SOAR changes something: when a step waits for approval, who can decide, how long it waits, and what happens after.

Use approvals to keep a person in charge of disruptive changes. When a step needs approval, the run pauses and the step appears on Automation → Approvals until someone with soar:approve approves or rejects it, or it expires.

When a step needs approval

A run waits for a person at:

  • every Approval gate step;
  • every destructive action;
  • every write action, unless the step allows automatic approval;
  • any action the pack marks as always needing approval;
  • any step whose approval policy is set to always require approval (approval: required);
  • every action and notification that comes after a Judge step anywhere earlier in the flow;
  • every action and notification in a run that an API key started;
  • from v2.0.34, every action, notification, Set hunt finding disposition and case step in a run triggered by an AI event: a hunt-finding alert, the AI triage verdict, a case the AI opened (or one seeded from a hunt finding), or a case status change the AI made, or a hunt escalation;
  • every case step after a Judge step, in a run an API key started, or with approval: required;
  • a resend of an action that isn't safe to retry, after an earlier attempt had an unclear (ambiguous) outcome.

A read action and a search step don't need approval unless one of these rules applies.

Approval policy on a step

Policyapproval valueWhat it does
Require approval (default)defaultFollows the rules above: write and destructive actions wait.
Allow automatic approvalautoA write action runs without waiting when a person or a trigger started the run. Refused on destructive actions. Ignored after a Judge step, in API-key runs and in runs triggered by AI events.
Always require approvalrequiredThe step always waits, whatever its effect.

Why a step after a Judge step always waits: a Judge verdict is model output over evidence an attacker can influence, such as alert fields and search rows. A branch on that verdict could pick a disruptive action, so nano treats every later action as AI-requested.

Who can approve

To approve or reject, you need all of these:

  • soar:approve;
  • an interactive sign-in. API keys can't decide approvals;
  • access to the run and its data. If any of the step's details are hidden from you by source visibility, you can reject it but not approve it;
  • not being the requester. You can't decide an approval for a run you started. For a run a trigger started, the requester is the person who last saved the flow.

nano checks the approver's authority twice: when they decide, and again just before the step runs. If the approver loses soar:approve, or loses access to the run's data in between, the run ends as canceled (approval_authority_revoked).

Decide an approval

Open Approvals

Go to Automation → Approvals, or click the approvals indicator in the top bar. Each card shows who or what requested the step, the action and its inputs, and a countdown to when it expires.

Review the request

Check the action, the target, and the connection. For a notification, the card shows the exact subject and body.

Approve or reject

If the gate offers choices, pick one. Enter a reason, then click Approve or Reject. A reason is required to reject, and an approval gate can require a note for specific choices. Reasons can be up to 2,048 characters.

After you decide:

DecisionResult
ApproveThe run continues from that step. For a notification, the approval covers exactly that content and destination; if either changed, the step fails with notification_changed.
RejectThe run ends as canceled with approval_rejected.
Nobody decides in timeThe approval expires and the run ends as failed with approval_expired.

One approval decides each step. Approvals and rejections are audited with the decider and the reason.

How long an approval waits

StepWaits up to
Approval gateIts Expires after (min) setting, from 1 minute to 1,440 minutes (24 hours). The default is 24 hours.
Action or notification that needs approval24 hours

An approval always waits at least 1 minute. When SOAR is turned off, every pending approval expires. When a run is canceled, its pending approvals are canceled.

Build approval gates

Add an Approval gate from the palette and set it in the inspector:

  • Message to approver: what the approver should check, up to 2,048 characters.
  • Choices: up to 32 options, separated by commas. The chosen option is available to later steps as results.<step id>.choice, so a condition can branch on it. A condition on an approval must read .choice or .approved; validation refuses one that compares the whole approval result.
  • Note required on: a choice that requires the approver to enter a note.
  • Expires after (min): how long the gate waits.

Approvals in tests

A test with a real alert never pauses. A step that would need approval is recorded as would_wait, with a preview of what the approver would see. A condition that reads that approval takes its default branch and is shown as not evaluated, so an approval followed by a condition tests cleanly. A dry run started with sample values or a recent case does wait for approvals. See Test a flow.

What's next

On this page