diff --git a/assets/images/help/copilot/enterprise-premium-request-budget.png b/assets/images/help/copilot/enterprise-premium-request-budget.png new file mode 100644 index 000000000000..e29f60b6bca3 Binary files /dev/null and b/assets/images/help/copilot/enterprise-premium-request-budget.png differ diff --git a/content/billing/managing-your-billing/gathering-insights-on-your-spending.md b/content/billing/managing-your-billing/gathering-insights-on-your-spending.md index 4551cb3a180c..bb6f333b2d69 100644 --- a/content/billing/managing-your-billing/gathering-insights-on-your-spending.md +++ b/content/billing/managing-your-billing/gathering-insights-on-your-spending.md @@ -82,9 +82,9 @@ You can view the usage of your {% data variables.enterprise.enterprise_or_org %} 1. To request a CSV usage report, select **Get usage report** in the upper-right corner of the page. * For a breakdown of all metered usage, click **Metered billing usage report**. - * For a per user breakdown of additional premium requests, click **{% data variables.product.prodname_copilot_short %} premium requests usage report**. + * For a per user breakdown of premium requests for the last 45 days, click **{% data variables.product.prodname_copilot_short %} premium requests usage report**. - You can choose a pre-selected option or use the "Custom range" option to specify a date range of up to 31 days. + >[!TIP] The premium request usage report includes all premium requests, both within and beyond the allowance. By contrast, the metered billing usage report only reflects costs for requests beyond the allowance. ## Viewing license usage diff --git a/content/billing/managing-your-billing/using-budgets-control-spending.md b/content/billing/managing-your-billing/using-budgets-control-spending.md index aba3a9c7c49e..f919c2dfae44 100644 --- a/content/billing/managing-your-billing/using-budgets-control-spending.md +++ b/content/billing/managing-your-billing/using-budgets-control-spending.md @@ -132,7 +132,6 @@ As the owner of an enterprise or organization account, or as a billing manager, You can edit or delete a budget at any time, but you cannot change the scope of a budget after creating it. -1. In the "Budgets and alerts" view, click **New budget**. -1. Click **Budgets and alerts**. -1. To edit a budget, in the list of budgets, click {% octicon "kebab-horizontal" aria-label="View actions" %} next to the budget you want to edit, and click **{% octicon "pencil" aria-hidden="true" aria-label="pencil" %} Edit** or **{% octicon "trash" aria-hidden="true" aria-label="trash" %} Delete**. +1. Navigate to the "Budgets and alerts" view. See [Viewing budgets](#viewing-budgets). +1. In the list of budgets, click {% octicon "kebab-horizontal" aria-label="View actions" %} next to the budget you want to edit, and click **{% octicon "pencil" aria-hidden="true" aria-label="pencil" %} Edit** or **{% octicon "trash" aria-hidden="true" aria-label="trash" %} Delete**. 1. Follow the prompts. diff --git a/content/copilot/concepts/copilot-billing/understanding-and-managing-requests-in-copilot.md b/content/copilot/concepts/copilot-billing/understanding-and-managing-requests-in-copilot.md index c77817e1b329..08073d6e8e1f 100644 --- a/content/copilot/concepts/copilot-billing/understanding-and-managing-requests-in-copilot.md +++ b/content/copilot/concepts/copilot-billing/understanding-and-managing-requests-in-copilot.md @@ -67,9 +67,10 @@ If you're on a **paid plan** and use all of your premium requests, you can still If you need more premium requests beyond your monthly allowance, you can: * Set a spending limit for additional premium requests. See [AUTOTITLE](/billing/managing-your-billing/using-budgets-control-spending). -* Upgrade to a higher plan. +* Upgrade your individual subscription to a higher plan. +* If you're an enterprise owner, edit the default $0 budget or upgrade members to {% data variables.copilot.copilot_enterprise_short %}. See [AUTOTITLE](/copilot/how-tos/premium-requests/manage-for-enterprise). -These actions can be taken by organization owners, billing managers, and personal account users. +These actions can be taken by enterprise owners, organization owners, billing managers, and personal account users. > [!IMPORTANT] By default, all budgets are set to zero and premium requests over the allowance are rejected unless a budget has been created. Additional premium requests beyond your plan’s included amount are billed at {% data variables.copilot.additional_premium_requests %} per request. diff --git a/content/copilot/get-started/choosing-your-enterprises-plan-for-github-copilot.md b/content/copilot/get-started/choosing-your-enterprises-plan-for-github-copilot.md index 44accb3e3366..21cc6a35ba91 100644 --- a/content/copilot/get-started/choosing-your-enterprises-plan-for-github-copilot.md +++ b/content/copilot/get-started/choosing-your-enterprises-plan-for-github-copilot.md @@ -61,9 +61,12 @@ With {% data variables.copilot.copilot_code-review_short %}, {% data variables.p ## How much will we benefit from premium requests? -{% data reusables.copilot.premium-requests-for-enterprises %} +Each {% data variables.product.prodname_copilot_short %} plan includes a per-user allowance for premium requests: -To decide if you will benefit from a higher allowance for premium requests, compare the goals of your rollout to **development tasks** that each model is specialized in. For example, the {% data variables.copilot.copilot_claude_sonnet_40 %} is designed for advanced reasoning and coding tasks. Teams who work in specialized areas may require more requests to premium models. To learn about the benefits of different models, see [AUTOTITLE](/copilot/using-github-copilot/ai-models/choosing-the-right-ai-model-for-your-task). +* 300 requests per user per month for {% data variables.copilot.copilot_business_short %} +* 1000 requests per user per month for {% data variables.copilot.copilot_enterprise_short %} + +By ensuring members have access to enough premium requests, you can drive real business outcomes, such as reducing your backlog with {% data variables.copilot.copilot_coding_agent %}, accelerating pull requests with {% data variables.copilot.copilot_code-review_short %}, or increasing code quality with suggestions from more specialized models. Regardless of your plan, you can set a spending limit for premium requests over your plan's allowance. Premium requests over the allowance will be charged at a rate of {% data variables.copilot.additional_premium_requests %} per request, with an additional multiplier applied to certain models. diff --git a/content/copilot/how-tos/administer/organizations/reviewing-activity-related-to-github-copilot-in-your-organization/reviewing-user-activity-data-for-copilot-in-your-organization.md b/content/copilot/how-tos/administer/organizations/reviewing-activity-related-to-github-copilot-in-your-organization/reviewing-user-activity-data-for-copilot-in-your-organization.md index 9922d76347d6..96184a8e7707 100644 --- a/content/copilot/how-tos/administer/organizations/reviewing-activity-related-to-github-copilot-in-your-organization/reviewing-user-activity-data-for-copilot-in-your-organization.md +++ b/content/copilot/how-tos/administer/organizations/reviewing-activity-related-to-github-copilot-in-your-organization/reviewing-user-activity-data-for-copilot-in-your-organization.md @@ -41,31 +41,11 @@ redirect_from: You can use {% data variables.product.prodname_dotcom %}'s REST API to get details about the assignment of {% data variables.product.prodname_copilot %} seats in your organization. See [Get Copilot seat information and settings for an organization](/rest/copilot/copilot-user-management?apiVersion=2022-11-28#get-copilot-seat-information-and-settings-for-an-organization), [List all Copilot seat assignments for an organization](/rest/copilot/copilot-user-management?apiVersion=2022-11-28#list-all-copilot-seat-assignments-for-an-organization), and [Get Copilot seat assignment details for a user](/rest/copilot/copilot-user-management?apiVersion=2022-11-28#get-copilot-seat-assignment-details-for-a-user). -## Understanding the `last_activity_at` calculation +## Troubleshooting `last_activity_at` data -> [!NOTE] This data is in {% data variables.release-phases.public_preview %} and subject to change. +If you believe a user's `last_activity_at` date should be more recent than shown in the CSV or API report, wait 24 hours and check again. If their recent Copilot usage is still not reflected in their `last_activity_at` date, have the user check that telemetry is enabled in their IDE settings. -To align the `last_activity_at` data point with _actual usage_, the system returns the timestamp of a user's most recent interaction with Copilot functionality. These interactions are: - -* Receiving a code suggestion in an IDE -* Chatting with Copilot Chat in an IDE -{%- ifversion ghec %} -* Creating or updating a knowledge base -* Creating a pull request summary -* Interacting with Copilot Chat in GitHub -{%- endif %} -* Interacting with Copilot on a mobile device -* Interacting with Copilot Chat for CLI - -The `last_activity_at` date is consistent across the CSV generated via `Get Report` in Copilot Access settings as well as through {% data variables.product.prodname_dotcom %}'s REST API. The events which are tracked come from both client, and server-side telemetry. This allows the timestamp to be durable in the event that network conditions would impact client-telemetry. - -The retention period for `last_activity_at` data is 90 days. After 90 days of no new activity, a user's `last_activity_at` value is set to `nil`. The data retention period cannot be modified. For more information, see [Updating retention period for `last_activity_at` values on the Copilot user management API to 90 days](https://github.blog/changelog/2025-01-17-updating-retention-period-for-last_activity_at-values-on-the-user-management-api-public-preview-to-90-days/) on {% data variables.product.prodname_blog %}. - -### Troubleshooting `last_activity_at` data - -Processing new telemetry events and updating a user's `last_activity_at` date can take up to 24 hours. Users must have telemetry enabled in their IDE for their usage to be reflected in `last_activity_at`. - -If you believe a user's `last_activity_at` date should be more recent than shown in the CSV or API report, please wait 24 hours and check again. If their recent Copilot usage is still not reflected in their `last_activity_at` date, have the user check that telemetry is enabled in their IDE settings. +For more information about this property, see [AUTOTITLE](/copilot/reference/metrics-data#last_activity_at). ## Further reading diff --git a/content/copilot/how-tos/index.md b/content/copilot/how-tos/index.md index 3c26905db258..adb920bc5467 100644 --- a/content/copilot/how-tos/index.md +++ b/content/copilot/how-tos/index.md @@ -16,7 +16,7 @@ children: - /custom-instructions - /content-exclusion - /github-flow - - /monitoring-your-copilot-usage-and-entitlements + - /premium-requests - /personal-settings - /manage-your-account - /administer diff --git a/content/copilot/how-tos/premium-requests/index.md b/content/copilot/how-tos/premium-requests/index.md new file mode 100644 index 000000000000..2e75eded2f51 --- /dev/null +++ b/content/copilot/how-tos/premium-requests/index.md @@ -0,0 +1,13 @@ +--- +title: Premium requests for Copilot +shortTitle: Premium requests +intro: 'Manage and track premium requests for yourself or for your users.' +versions: + feature: copilot +topics: + - Copilot +children: + - /monitoring-your-copilot-usage-and-entitlements + - /manage-for-enterprise +--- + diff --git a/content/copilot/how-tos/premium-requests/manage-for-enterprise.md b/content/copilot/how-tos/premium-requests/manage-for-enterprise.md new file mode 100644 index 000000000000..65e937800622 --- /dev/null +++ b/content/copilot/how-tos/premium-requests/manage-for-enterprise.md @@ -0,0 +1,64 @@ +--- +title: Managing the premium request allowance for users in your enterprise +shortTitle: Manage allowance for members +intro: 'Change the default spending limit or upgrade users to {% data variables.copilot.copilot_enterprise_short %}.' +permissions: 'Enterprise owners' +versions: + feature: copilot +topics: + - Copilot +allowTitleToDifferFromFilename: true +product: '{% data variables.copilot.copilot_for_business %} or {% data variables.copilot.copilot_enterprise %}' +--- + +Each {% data variables.product.prodname_copilot_short %} plan includes a per-user allowance for premium requests. To learn more about premium requests, see [AUTOTITLE](/copilot/concepts/copilot-billing/understanding-and-managing-requests-in-copilot). For allowances per plan, see [AUTOTITLE](/copilot/get-started/plans-for-github-copilot#comparing-copilot-plans). + +By default, every enterprise has a $0 budget for the Premium Request SKU. Unless this budget is edited or deleted, your enterprise will have **no extra costs** for premium requests: when one of your licensed users exhausts the allowance in their plan, the user's premium requests will be rejected for the rest of the month. + +![Screenshot of the enterprise budgets page, with the default budget: a $0 budget for the Premium Request SKU.](/assets/images/help/copilot/enterprise-premium-request-budget.png) + +You can edit or delete this budget to grant extra requests to all your licensed members. If you want to grant extra requests to certain users only, you can upgrade those users to {% data variables.copilot.copilot_enterprise_short %}. + +## Prerequisites + +* Before making changes, download a usage report to see which developers are frequently hitting the limit or using a significant number of requests over the allowance. You may want to contact these users to understand their use cases and requirements. See [Downloading a monthly usage report](/copilot/how-tos/monitoring-your-copilot-usage-and-entitlements#downloading-a-monthly-usage-report). +* If a user receives licenses from multiple enterprises or standalone organizations, the user must select a billing entity to use premium requests. See [Managing premium request billing with multiple {% data variables.product.prodname_copilot_short %} licenses](/copilot/managing-copilot/monitoring-usage-and-entitlements/monitoring-your-copilot-usage-and-entitlements#managing-premium-request-billing-with-multiple-copilot-licenses). + +## Changing the budget for all members + +To enable premium requests over the allowance for everyone, you can: + +* Delete the default $0 budget to allow **unlimited spending on premium requests** for all users. +* Edit the "Budget amount" of the default $0 budget to set **a non-zero total spending limit** for premium requests in your enterprise. + +For instructions, see [AUTOTITLE](/billing/managing-your-billing/using-budgets-control-spending#editing-or-deleting-a-budget). + +>[!NOTE] Creating new budgets without deleting the $0 budget does not override the $0 budget. If **any** applicable budget with "Stop usage when budget limit is reached" enabled is exhausted, additional premium requests are blocked. + +## Upgrading users to {% data variables.copilot.copilot_enterprise_short %} + +You can upgrade certain users to increase their base allowance of premium requests. + +>[!TIP] {% data variables.copilot.copilot_business_short %} users who make make more than 800 premium requests per month would save money with a {% data variables.copilot.copilot_enterprise_short %} license. + +1. Create a new organization in your enterprise. See [AUTOTITLE](/enterprise-cloud@latest/admin/managing-accounts-and-repositories/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise#creating-a-new-organization). +1. Add the users who need more premium requests to the new organization. +1. Grant {% data variables.copilot.copilot_enterprise_short %} licenses to all users in the organization. + + 1. If needed, upgrade the enterprise to {% data variables.copilot.copilot_enterprise_short %}. See [AUTOTITLE](/enterprise-cloud@latest/copilot/how-tos/administer/enterprises/managing-the-copilot-plan-for-your-enterprise/upgrading-copilot-for-your-enterprise). + + 1. Enable {% data variables.copilot.copilot_enterprise_short %} for the new organization. See [AUTOTITLE](/enterprise-cloud@latest/copilot/how-tos/administer/enterprises/managing-access-to-copilot-in-your-enterprise/enabling-copilot-for-organizations-in-your-enterprise). + + 1. Grant licenses to all users in the organization. See [AUTOTITLE](/copilot/how-tos/administer/organizations/managing-access-to-github-copilot-in-your-organization/granting-access-to-copilot-for-members-of-your-organization#granting-access-to-github-copilot-for-all-current-and-future-users-in-your-organization). + +1. Check the usage report regularly to ensure that {% data variables.copilot.copilot_enterprise_short %} remains the most cost-effective option for these users. + +## Setting a budget for specific members + +You can set a higher budget for premium requests over the allowance for specific users in your enterprise. However, you must ensure that every user in your enterprise is covered by a budget. Users who are not covered by a budget will have access to unlimited spending on premium requests. + +At a high level, the required steps are: + +1. Delete the default $0 budget. +1. Create a new budget for the users who need a higher allowance. For example, create an organization or cost center containing just these users, then create a Premium Request SKU budget for the organization or cost center. +1. Create a separate, more restrictive budget that covers every other {% data variables.product.prodname_copilot_short %} user in your enterprise. You will likely need to integrate with the API to ensure that this budget covers new users as they are added to your enterprise. diff --git a/content/copilot/how-tos/monitoring-your-copilot-usage-and-entitlements.md b/content/copilot/how-tos/premium-requests/monitoring-your-copilot-usage-and-entitlements.md similarity index 97% rename from content/copilot/how-tos/monitoring-your-copilot-usage-and-entitlements.md rename to content/copilot/how-tos/premium-requests/monitoring-your-copilot-usage-and-entitlements.md index 6e5f2b1e52a6..1495c5bf2400 100644 --- a/content/copilot/how-tos/monitoring-your-copilot-usage-and-entitlements.md +++ b/content/copilot/how-tos/premium-requests/monitoring-your-copilot-usage-and-entitlements.md @@ -11,6 +11,7 @@ redirect_from: - /copilot/managing-copilot/managing-copilot-as-an-individual-subscriber/monitoring-usage-and-entitlements/monitoring-your-copilot-usage-and-entitlements - /copilot/managing-copilot/monitoring-usage-and-entitlements/monitoring-your-copilot-usage-and-entitlements - /copilot/managing-copilot/understanding-and-managing-copilot-usage/monitoring-your-copilot-usage-and-entitlements + - /copilot/how-tos/monitoring-your-copilot-usage-and-entitlements --- You can track your monthly usage of premium requests to help you get the most value from your {% data variables.product.prodname_copilot_short %} plan. @@ -52,6 +53,8 @@ You can view your premium request usage at any time from your {% data variables. ### Downloading a {% data variables.product.prodname_copilot_short %} premium request usage report +The premium request usage report includes all premium request usage, both within and beyond the allowance. By contrast, other metered billing reports only reflect costs for premium requests beyond the allowance. + >[!NOTE] > For organizations and enterprises, only admins can download a usage report to understand {% data variables.product.prodname_copilot_short %} usage across their business. Individual members of the organization or enterprise cannot download the report for themselves. diff --git a/content/copilot/reference/index.md b/content/copilot/reference/index.md index 70f1b9e19745..824f33f5d47d 100644 --- a/content/copilot/reference/index.md +++ b/content/copilot/reference/index.md @@ -11,5 +11,6 @@ children: - /ai-models - /proxy-server-and-firewall-settings-for-copilot - /copilot-extensions + - /metrics-data --- diff --git a/content/copilot/reference/metrics-data.md b/content/copilot/reference/metrics-data.md new file mode 100644 index 000000000000..55404af3cc47 --- /dev/null +++ b/content/copilot/reference/metrics-data.md @@ -0,0 +1,46 @@ +--- +title: Metrics data properties for GitHub Copilot +shortTitle: Metrics data +intro: 'See how GitHub calculates properties from APIs and reports.' +versions: + feature: copilot +topics: + - Copilot +allowTitleToDifferFromFilename: true +--- + +## `last_activity_at` + +> [!NOTE] This data is in {% data variables.release-phases.public_preview %} and subject to change. + +The timestamp of a user's most recent interaction with {% data variables.product.prodname_copilot_short %} functionality. + +### Surfaces + +This property is consistent across the following surfaces: + +* The CSV report downloaded from the "Access management" page (see [AUTOTITLE](/copilot/how-tos/administer/organizations/reviewing-activity-related-to-github-copilot-in-your-organization/reviewing-user-activity-data-for-copilot-in-your-organization)) +* The [AUTOTITLE](/rest/copilot/copilot-user-management) + +### Calculation + +The following interactions count as activity: + +* Receiving a code suggestion in an IDE +* Chatting with Copilot Chat in an IDE +* Creating or updating a knowledge base +* Creating a pull request summary +* Interacting with Copilot Chat in GitHub +* Interacting with Copilot on a mobile device +* Interacting with Copilot Chat for CLI + +The tracked events come from both client- and server-side telemetry, ensuring the timestamp is durable if network conditions affect client-side telemetry. + +Processing new telemetry events and updating a user's `last_activity_at` date can take up to 24 hours. Users must have telemetry enabled in their IDE for their usage to be reflected in `last_activity_at`. + +### Retention period + +* The retention period for `last_activity_at` data is 90 days. This cannot be modified. +* After 90 days of no new activity, a user's `last_activity_at` value is set to `nil`. + +For more information, see [Updating retention period for `last_activity_at` values on the Copilot user management API to 90 days](https://github.blog/changelog/2025-01-17-updating-retention-period-for-last_activity_at-values-on-the-user-management-api-public-preview-to-90-days/) on {% data variables.product.prodname_blog %}. diff --git a/content/copilot/tutorials/rolling-out-github-copilot-at-scale/assigning-licenses/managing-your-companys-spending-on-github-copilot.md b/content/copilot/tutorials/rolling-out-github-copilot-at-scale/assigning-licenses/managing-your-companys-spending-on-github-copilot.md index 71e079b2e243..eb9c03f2e951 100644 --- a/content/copilot/tutorials/rolling-out-github-copilot-at-scale/assigning-licenses/managing-your-companys-spending-on-github-copilot.md +++ b/content/copilot/tutorials/rolling-out-github-copilot-at-scale/assigning-licenses/managing-your-companys-spending-on-github-copilot.md @@ -15,73 +15,33 @@ redirect_from: When you're adopting {% data variables.product.prodname_copilot %} in an enterprise, you will want to set budgets and track spending to ensure your rollout is sustainable. {% data variables.product.github %} offers billing tools to help you visualize your spending patterns, receive alerts when you reach budget thresholds, and optimize your license usage. ->[!NOTE] Some of the tools recommended in this article are part of {% data variables.product.github %}'s new billing platform, which isn't available to all customers. If your enterprise has access, you will see a **{% octicon "credit-card" aria-hidden="true" aria-label="credit-card" %} Billing & Licensing** option in your enterprise account's settings. - -## Understand who can grant licenses +## Understanding who can grant licenses To control spending, it's important to understand who can affect your bill by granting licenses to users. These are people with the **organization owner** role in organizations where you enable {% data variables.product.prodname_copilot %}. Organization owners can receive requests for access from members through the {% data variables.product.github %} UI. We recommend that you identify the people with this role and communicate with them about your company's strategy for distributing licenses. For example, you may have a budget or limited pilot program, or you may distribute licenses through an internal website. -## Managing charges for premium requests - -{% data reusables.copilot.premium-requests-for-enterprises %} - -### Use of premium requests over the allowance - -Premium requests over the allowance are rejected unless you have set a budget. Depending on the type of development tasks your developers use {% data variables.product.prodname_copilot_short %} for, you may find developers need to make more premium requests than the allowance included in your plan. - -Premium requests over the allowance are charged at a rate of {% data variables.copilot.additional_premium_requests %} per request, with an additional multiplier applied to certain models. You can also increase your monthly allowance by upgrading to {% data variables.copilot.copilot_enterprise_short %}. - -For pricing details and a list of available models, see [AUTOTITLE](/copilot/about-github-copilot/subscription-plans-for-github-copilot#comparing-copilot-plans). - -{% data reusables.copilot.premium-request-entity-selection %} - -### Managing budgets - -By default, a $0 budget for the {% data variables.product.prodname_copilot %} Premium Request SKU is created for your enterprise. You can edit this budget from the "Budgets and alerts" page. See [AUTOTITLE](/billing/managing-your-billing/using-budgets-control-spending). +## Managing premium requests -> [!WARNING] Deleting this budget without setting a new one will enable **unlimited {% data variables.product.prodname_copilot %} usage**. +Each {% data variables.product.prodname_copilot_short %} plan includes a per-user allowance for premium requests. To learn more about premium requests, see [AUTOTITLE](/copilot/concepts/copilot-billing/understanding-and-managing-requests-in-copilot). For allowances per plan, see [AUTOTITLE](/copilot/get-started/plans-for-github-copilot#comparing-copilot-plans). -The default budget that is created applies to your whole enterprise. To set a new budget for a specific part of your enterprise, such as a cost center, you can create a new budget: +### Tracking premium request usage -{% ifversion fpt %} +To track premium request usage, download the premium request usage report for your organization or enterprise. See [AUTOTITLE](/copilot/how-tos/premium-requests/monitoring-your-copilot-usage-and-entitlements#downloading-a-monthly-usage-report). -{% data reusables.profile.access_org %} -{% data reusables.profile.org_settings %} -{% data reusables.billing.org-billing-menu %} +This report includes all premium request usage by user, both within and beyond the allowance, so you can use the report to understand general patterns and identify users who would benefit from more premium requests. -{% elsif ghec %} +By contrast, other metered billing usage reports only reflect costs for premium requests beyond the allowance. -1. Go to your enterprise or organization account settings and click **{% octicon "credit-card" aria-hidden="true" aria-label="credit-card" %} Billing & Licensing**. - -{% endif %} -1. Click **Budgets and alerts**. -1. Click **New budget**. -1. Under "Budget Type" select **SKU-level budget**. -1. Select the "Product" dropdown and click **Copilot**. -1. Select the "SKU" dropdown and click **Copilot Premium Request** -1. Under "Budget scope", set the scope of spending for this budget. -1. Under "Budget", set a budget amount. Optionally, choose to stop usage when the budget limit is reached. -1. Click **Create budget**. - -### Tracking premium requests +### Granting more premium requests to members -You can view a CSV report that shows the cumulative number of premium requests per user over a time period. You can use this report to: +By default, enterprises have a $0 budget for the Premium Request SKU. This means that when users exhaust their allowance, they cannot make any more premium requests for the rest of the month. Deleting this budget allows for **unlimited spending**. -* Understand if developers are frequently hitting the limit and would benefit from you enabling additional premium requests or upgrading your plan. -* Identify users who are making a large number of premium requests over the limit, and follow up to the users to understand their use cases and requirements. -* After enabling additional premium requests, track usage to determine if it would be more cost effective to upgrade to {% data variables.copilot.copilot_enterprise_short %}. +To change the default budget or increase members' base allowance, see [AUTOTITLE](/copilot/how-tos/premium-requests/manage-for-enterprise). -You can download the report for an enterprise account, or for an organization that is not part of an enterprise. +## Mapping spending to groups of users -1. Go to your enterprise or organization account settings and click **{% octicon "credit-card" aria-hidden="true" aria-label="credit-card" %} Billing & Licensing**. -1. In the left sidebar, click **Usage**. -1. To download the usage report, select **Get usage report** in the upper-right corner of the page, and click **{% data variables.product.prodname_copilot_short %} premium requests usage report**. - -## Map spending to groups of users - -With {% data variables.product.github %}'s new billing platform, you can create cost centers to map spending to individual business units or groups of users. Cost centers allow you to track costs tied to different initiatives and charge the costs to specific areas of your business. +You can create cost centers to map spending to individual business units or groups of users. Cost centers allow you to track costs tied to different initiatives and charge the costs to specific areas of your business. For example, if you were running a pilot program for {% data variables.copilot.copilot_enterprise %} for a group of employees, you might want to create a cost center to track their spending and set a budget independently of the rest of the company. @@ -95,21 +55,20 @@ For example, if you were running a pilot program for {% data variables.copilot.c 1. After creating the cost center, use the REST API to add the users whose usage you want to track. See [AUTOTITLE](/enterprise-cloud@latest/rest/enterprise-admin/billing#add-users-to-a-cost-center). -## Receive alerts for overspending +## Preventing overspending -With {% data variables.product.github %}'s new billing platform, you can set a monthly budget on {% data variables.product.prodname_copilot %} spending. Setting a budget for license-based products, such as {% data variables.product.prodname_copilot_short %}, is for monitoring purposes only and will not prevent usage beyond the budgeted amount. However, you will receive notifications by email when spending exceeds certain percentages of the budget you've set. To prevent usage over the limit for the Copilot Premium Request SKU, update the default $0 SKU-level budget and select "Stop usage when budget limit is reached". +You can set a monthly budget on {% data variables.product.prodname_copilot %} spending. -{% ifversion ghec %}You can create the budget for the whole enterprise or for a cost center.{% endif %} +* For {% data variables.product.prodname_copilot_short %} **licenses**, a budget is for monitoring purposes only and will not prevent usage beyond the budgeted amount. However, you will receive notifications by email when spending exceeds certain percentages of the budget you've set. +* For {% data variables.product.prodname_copilot_short %} **premium requests**, you can choose to stop usage once the budget amount is reached. The default $0 budget for enterprises already does this. -1. Go to your enterprise or organization account settings and click **{% octicon "credit-card" aria-hidden="true" aria-label="credit-card" %} Billing & Licensing**. -1. In the left sidebar, click **Budgets and alerts**. -1. Click **New budget**. -1. Select **{% data variables.product.prodname_copilot_short %}** for the product, or **{% data variables.product.prodname_copilot_short %} Premium Request** for the SKU, then configure the settings as required. You can choose who receives alerts when budget thresholds are reached. -1. Click **Create budget**. +To create a budget, see [AUTOTITLE](/billing/managing-your-billing/using-budgets-control-spending#editing-or-deleting-a-budget). + +## Visualizing spending trends -## Visualize spending trends +You can understand your spending trends by viewing a graph for {% data variables.product.prodname_copilot_short %} usage over a certain timeframe. Usage includes costs for {% data variables.product.prodname_copilot_short %} licenses and additional premium requests beyond the allowance. -With {% data variables.product.github %}'s new billing platform, you can understand your spending trends by viewing a graph for {% data variables.product.prodname_copilot_short %} usage over a certain timeframe. For more detailed insights, you can filter the results by cost center and group usage by the type of {% data variables.product.prodname_copilot_short %} plan. +For more detailed insights, you can filter the results by cost center and group usage by the type of {% data variables.product.prodname_copilot_short %} plan. 1. Go to your enterprise or organization account settings and click **{% octicon "credit-card" aria-hidden="true" aria-label="credit-card" %} Billing & Licensing**. 1. In the left sidebar, click **Usage**. diff --git a/content/copilot/tutorials/rolling-out-github-copilot-at-scale/assigning-licenses/reminding-inactive-users.md b/content/copilot/tutorials/rolling-out-github-copilot-at-scale/assigning-licenses/reminding-inactive-users.md index 6199dee5b060..ab9a6c24ed5f 100644 --- a/content/copilot/tutorials/rolling-out-github-copilot-at-scale/assigning-licenses/reminding-inactive-users.md +++ b/content/copilot/tutorials/rolling-out-github-copilot-at-scale/assigning-licenses/reminding-inactive-users.md @@ -159,5 +159,6 @@ jobs: ## Further reading +* [AUTOTITLE](/copilot/reference/metrics-data#last_activity_at) * [AUTOTITLE](/copilot/rolling-out-github-copilot-at-scale/driving-copilot-adoption-in-your-company) * [AUTOTITLE](/copilot/rolling-out-github-copilot-at-scale/analyzing-usage-over-time-with-the-copilot-metrics-api) diff --git a/content/packages/learn-github-packages/deleting-and-restoring-a-package.md b/content/packages/learn-github-packages/deleting-and-restoring-a-package.md index a50de3906d8f..1bf7bb37eeda 100644 --- a/content/packages/learn-github-packages/deleting-and-restoring-a-package.md +++ b/content/packages/learn-github-packages/deleting-and-restoring-a-package.md @@ -98,7 +98,7 @@ To delete a specific version of a user-scoped package on {% data variables.produ To review who can delete a package version, see [Required permissions](#required-permissions-to-delete-or-restore-a-package). {% data reusables.package_registry.package-settings-from-user-level %} -{% data reusables.package_registry.package-settings-option %} +1. Search for and then click the name of the package that you want to manage. {% data reusables.package_registry.package-settings-manage-versions-menu %} {% data reusables.package_registry.package-settings-delete-versions %} 1. In the confirmation box, type the name of the package to confirm you want to delete the chosen version of it. @@ -112,7 +112,7 @@ To delete an entire package, see [Deleting an entire organization-scoped package To review who can delete a package version, see [Required permissions to delete or restore a package](#required-permissions-to-delete-or-restore-a-package). {% data reusables.package_registry.package-settings-from-org-level %} -{% data reusables.package_registry.package-settings-option %} +1. Search for and then click the name of the package that you want to manage. {% data reusables.package_registry.package-settings-manage-versions-menu %} {% data reusables.package_registry.package-settings-delete-versions %} 1. In the confirmation box, type the name of the package to confirm you want to delete the chosen version of it.