GitHub budgets are now searchable across scopes, products and users

GitHub's October 13 release puts personal, organization and enterprise budgets into one searchable list on the Budgets and alerts page. Operators can search or filter by scope, product or SKU; organization and enterprise views can also search by user.

The change targets discovery rather than enforcement. It makes a specific budget easier to locate and shows user‑level budgets alongside broader rules, but it does not change the amount, recipients or stop behavior of an existing budget.

That matters during cost incidents: finding the matching row faster can shorten diagnosis, yet the row still needs to be read in the context of its scope and budget type.

The new Scope menu can narrow the list to organizations, repositories, cost centers or other available account levels. GitHub's [budget setup documentation](https://docs.github.com/billing/how‑tos/set‑up‑budgets) explains that available scopes depend on the account and budget type: organization budgets can cover an organization or repository, while enterprise metered‑product budgets can extend to the enterprise, organization, repository or cost center. Search results should therefore be treated as candidates, not a single effective policy. Two rows with the same product can govern different populations. Export or record the scope, product or SKU, amount, status and owner before deciding which rule explains a charge. For shared reviews, use stable account and scope names rather than screenshots alone. A screenshot can hide a filter and make a partial list look complete.

GitHub says administrators can search the combined list by user. The docs describe universal, cost‑center and individual AI‑credit budgets, with a specific user's budget taking precedence over broader user‑level rules where configured. Individual budgets can also expire, after which the user falls back to the next applicable level. A user search can reveal the rows involved, but it should not be interpreted as a complete billing calculation without checking precedence and expiration. Record the current billing cycle, the relevant cost center and any dated individual override. This is especially useful when two developers with similar Copilot usage see different remaining allowances. The explanation may be a specific user rule or an expired override rather than inconsistent metering.

The [setup guide](https://docs.github.com/billing/how‑tos/set‑up‑budgets) states that budgets can send alerts at 75%, 90% and 100%. For supported metered products and Advanced Security SKU‑level budgets, an administrator may also choose an option that stops or limits further use at the threshold. Without that option, exceeding a budget sends notifications but does not stop usage. Include enforcement mode in every budget audit. Labels such as `100% reached` or `over budget` describe a threshold, not automatically a hard block. Confirm whether usage‑stop controls are available and enabled for that exact budget type. For Advanced Security, GitHub notes that a hard budget prevents new enablement on additional repositories; it does not disable the product where it is already active. That difference should be explicit in incident and forecast playbooks.

At the start of a billing cycle, filter by product and SKU, then review large scopes before user overrides. Check duplicate or stale rows, alert recipients, expiration and stop behavior. For AI credits, sample one universal user, one cost‑center member and one individual override to verify the intended precedence. Retain a dated export or review record and repeat after cost‑center, membership or product changes. Search reduces navigation cost; it does not prove that the intended budget governs every user or repository. The practical gain is faster reconciliation across a growing budget inventory. Follow [GitHub's OpenTools organization page](https://opentools.ai/organizations/github) for related billing and governance releases. *Figure: A budget audit path from search filters to scope, precedence and enforcement checks. Sources: [GitHub's announcement](https://github.blog/changelog/2026‑10‑13‑search‑and‑filter‑for‑budgets‑now‑available/) and the [budget setup guide](https://docs.github.com/billing/how‑tos/set‑up‑budgets). Figure by OpenTools Team; no third‑party expressive material used.*