Approval queue
Decide a change another operator requested. An approval binds the exact action, target and parameters that were previewed — and you can never decide your own.
Note: What this screen still does not show
Opening a change shows what the preview bound: its kind, the records and revisions it names, the impacts recorded against it, whether it widens privilege and which staff identities it affects. Two things ADM-F02 lists are not stored on a preview and so are not here — who requested it and any cost estimate. If either matters to your decision, get it from the requester before you record one.
Note: What an approval still enforces
You cannot approve a change you requested, and you cannot approve one that would affect your own access. Your authority for this exact kind of change is re-checked against current policy at the moment you decide — an approval given under an older policy does not carry forward. The digest binds your decision to the exact bytes that were previewed; that is a guarantee about which change you decided, not about what it does.
Queue
Updating…
| Change | Affects | Widens | Expires | Decision |
|---|---|---|---|---|
| Reading… | ||||
Decide a specific change
Note: The digest is checked when you open, not when you decide
Opening a change needs the preview id and its digest, and the server refuses a pair that does not match a preview it holds. So a stale digest fails here, while you are reading — not at the moment you record a decision. What is then shown, and what your decision binds, is the server’s own copy.
From the requester's preview panel, or from a validation on the permission group editor.
Binds your decision to the exact change that was previewed. A different digest is a different change.