BlackOakAdmin
← Sitemap guide

Dual-approval queue

Planned — placeholder
Core portal · /dual-approval

High-risk actions pending a second distinct approver.

Open the placeholder →

How this step works

SIPOC
Who supplies this step, what it needs, what it does, what it produces, and who uses the result. Suppliers and customers are links — follow them to walk the workflow, including into the consumer and merchant apps.
SuppliersWhere the work comes from
InputsWhat this step needs to do its job
  • Actions the policy says one person may not do alone
  • The first approver
  • What is being changed
ProcessWhat happens here, in order
  1. Hold a high-risk change until a second authorised person approves it
  2. Show the reviewer exactly what will change
  3. Release or reject it, recording both decisions
OutputsWhat this step produces
  • An approved (or rejected) high-risk change
  • A two-person audit record
CustomersWho uses that output next

Where this fits

The workflows this step belongs to. The current step is highlighted.
Govern who can do whatControl administrative access and keep privileged actions accountable.