Approvals
Approvals let people request changes they can't make themselves. A request goes to the people configured to decide it, and nothing changes until they approve. Requires the Pro plan or higher; see Billing.
The page has three tabs, each with a count badge: My requests, Needs my approval and Routing. The My queue panel counts your pending, approved and rejected requests.
What can be requested
| Request type | What it changes | Who can submit it |
|---|---|---|
api_key.budget_increase | Raises a daily and/or monthly cap on one of your own API keys, in USD or in tokens (a token cap takes whole tokens or shorthand like 250K or 1.5M). | Builder and above |
api_key.add_models | Adds models to a key's allowlist. | Builder and above |
api_key.rpm_increase | Raises a key's requests-per-minute limit. | Builder and above |
api_key.new_key | Creates a key with the requested name, caps, models and rate limit. On approval, the secret is shown once to the requester. | Builder and above |
member.role_upgrade | Raises your own role. | Anyone |
other | Anything else. Nothing is applied automatically; your reason is the whole request. | Anyone |
Viewers have no API key, so they see only other and member.role_upgrade. Budget pool requests are covered in Pool requests.
New request shows who the request routes to, by name, before you submit. It asks for the fields that type needs: new caps (USD and token) for a budget increase, or name, caps, models and rate limit for a new key. Use CC to notify other members without making them deciders.
Who decides
Each request type has a chain of one or two stages, set on the Routing tab (admin only):
- Every stage is a named person, not a role.
- Stage 2, if set, must be a different person from stage 1.
- A Default CC per request type is copied on every request but never approves.
- Changes on the Routing tab apply immediately.
- If the requester's team has a lead, that person is added to the chain. See Teams → Lead.
Decide a request
Needs my approval lists every request in the workspace, with the ones you can decide now first. Select a row to see who raised it, when, the reason, and the requested values.
Approve and Reject each open a confirmation with an optional comment, and say whether this is the final stage. Both are disabled on your own request, even if a stage routes to you.
How a request changes state
Submitted
The request starts as
pendingat stage 1.Decided per stage
An approver at the current stage approves or rejects, with an optional comment. Approving a non-final stage moves it to the next stage; it stays
pending.Applied on final approval
The change is applied only when the last stage approves. The status becomes
approved.Or cancelled
The requester can cancel their own request while it's
pending.
A rejection at any stage sets the status to rejected and applies nothing. Decisions are final; to try again, submit a new request.