Approvals
The Approvals page lists requests that are currently held by the gateway waiting for a human decision. A request is held when it matches a require_approval rule in your policy.
How requests get held
When the gateway evaluates a request and matches a require_approval rule, it parks the request in a queue instead of forwarding it to the provider. The client's connection stays open and waits for the decision. Once approved, the gateway forwards the request immediately and the client receives a normal response. If denied, the gateway returns a denial response to the client.
A policy rule that holds requests matching a specific model:
rules: - action: require_approval match: model: gpt-4o reason: "GPT-4o requires operator approval"
Table columns
| Column | Description |
|---|---|
| Created | When the request arrived at the gateway |
| Workload | The workload that sent the request |
| Caller | The caller ID associated with the request |
| Target | The provider host and API path the request was headed to |
| Model | The model requested |
| Status | pending, approved, or denied |
| Decided By | Who approved or denied the request |
| Reason | The decision reason (or the policy rule reason if not yet decided) |
| Actions | Approve / Deny buttons (pending rows only) |
Approving or denying
Click the green check to approve or the red X to deny a pending request. A modal opens where you can optionally provide:
- Your name or ID: recorded with the decision
- Reason: a short explanation
Both fields are optional. Confirm with Approve or Deny to apply the decision immediately.
Pagination
Rows per page: 10, 25, or 50. Pagination uses Previous / Next token-based navigation.