From 732a6b78b7dc3e08f771f077dcdaf593da6526be Mon Sep 17 00:00:00 2001
From: Greg Mondello <72952982+gmondello@users.noreply.github.com>
Date: Thu, 23 Oct 2025 08:35:36 -0500
Subject: [PATCH] Add budget alerts section to documentation (#58114)

---
 content/billing/concepts/budgets-and-alerts.md | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/content/billing/concepts/budgets-and-alerts.md b/content/billing/concepts/budgets-and-alerts.md
index b17cce7520..5664eae946 100644
--- a/content/billing/concepts/budgets-and-alerts.md
+++ b/content/billing/concepts/budgets-and-alerts.md
@@ -30,6 +30,10 @@ Each budget has a type and a scope that define which paid use contributes to spe
 * **Type**: Defines which metered product or SKU is measured.
 * **Scope**: Defines whether the budget applies to the whole account, or to a subset of repositories, organizations, or cost centers (enterprise only).
 
+## Budget alerts
+
+You can enable alerts for budgets to receive emails when usage reaches 75%, 90%, and 100% of the budget amount. Emails are sent to account owners and billing managers by default. Additional recipients can be added as needed.
+
 ## Your first billing cycle after creating a budget
 
 When you first create a budget, be aware that the budget applies only to metered usage from the date of its creation onwards. Any use made before you created the budget is not included in the calculations. This means that you may exceed your budget in the first billing cycle after you create your budget, even if you select the option stop usage when the limit is reached.