Deciding on requests
The inbox, decision types, bulk approve, and cancellation.
The inbox
Everything waiting on you, live. New assignments appear the moment they are created, pushed over a realtime channel. Each row shows the request code, the stage you are deciding in, the requester, the age, and the SLA state.
Decision types
| Action | Effect |
|---|---|
| Approve | Satisfies your assignment; the stage evaluates its mode |
| Approve with conditions | Approves and attaches written conditions to the request |
| Reject | Finalizes the whole request as rejected, with an optional category (legal, commercial, counterparty) and reason |
Stage modes decide when a stage completes: any_of finishes on the first approval, all_of
waits for everyone, in_order activates approvers one after another.
Bulk approve
Select up to 25 inbox items and approve them together. Guardrails are deliberate: bulk is approve-only (rejections deserve individual attention), each item re-checks ownership, and you get a per-item result.
Cancelling a request
The requester (or an administrator) can pull back an in-flight request. Pending assignments are skipped, the request finalizes as cancelled, and the audit trail records who cancelled it. Terminal requests cannot be cancelled.