Pool requests

Leads and members cannot change a pool's limit or membership themselves. They file a request, and an approver decides it on the Approvals page. When it is approved, the change is applied.

Request	Filed by	Decided by	Effect
Request a higher limit `budget_pool.limit_increase`	The pool's lead, or an admin	The admin named on Routing	Raises the pool's monthly limit. The new limit must be higher than the current one and not above the workspace budget.
Request a member or key `budget_pool.member_move`	The pool's lead, or an admin	The admin named on Routing	Adds a person or a key to the pool. A person brings their one free key, or is issued one when the request is approved (never when it is filed). A key already in another pool is moved out of it. It arrives with no share until the lead gives it one.
Ask for a bigger share `budget_pool.share_increase`	The owner of a key in a pool with manual shares	The pool's lead (an admin if the pool has no lead)	Raises that key's share, inside the pool's limit. The request names the key, and it must be one the requester owns.

A lead cannot approve more money for their own pool. That is why a limit increase goes to an admin. A share increase only moves budget inside the pool, so the lead can approve it.

File a request from the pool

A lead's view of their pool, with the request buttons in the footer and the Request a higher limit form open

Open your pool
On Budgets, click the pool you lead or own a key in.
Click the request button
Leads see Request a member and Request a higher limit. Owners of a key in a pool with manual shares see Ask for a bigger share, and pick which of their keys needs more if they have several.
Fill in the form
The form shows the current value. Add a reason if the approver needs context. The form says who will decide it.
Click Send request
The approver is emailed. You are emailed when it is decided.

You can also file the same three requests from Approvals → New request. Pick the request type, then the pool.

Rules the request is checked against

Higher limit. Refused with not_an_increase if the number is not above the current limit, and with pool_limit_exceeds_workspace_budget if it is above the workspace budget. The workspace budget is checked again when the request is approved.
Bigger share. The pool needs room. If the guaranteed part of the pool has no undivided budget left, it is refused with insufficient_unallocated_headroom. Free some room first, or turn on burst.
Any request. If the pool changed between filing and approval so that the request no longer makes sense (for example the limit was already raised past it), approving it fails with request_is_stale and nothing changes. File it again.

Who can approve

Each request type has an approver chain set on the Approvals Routing tab (admin only), like any other request type. Limit increases and member requests go to the person named there, who must be an admin. Share increases use a stage called The pool's lead, which resolves to the lead when the request is filed, or to an admin if the pool has no lead.

A lead cannot approve a limit increase for their own pool.

Every filed, approved or rejected request is written to the audit log. An approved one records the pool's name, the key and its owner, whether a key was issued, and the before and after values.