|
| 1 | +--- |
| 2 | +title: Managing your company's spending on GitHub Copilot |
| 3 | +shortTitle: Manage spending |
| 4 | +intro: 'Learn how to track spending, view usage, and optimize license distribution.' |
| 5 | +versions: |
| 6 | + feature: copilot |
| 7 | +topics: |
| 8 | + - Copilot |
| 9 | +permissions: 'Enterprise owners and billing managers' |
| 10 | +product: '{% data variables.product.prodname_copilot_for_business %} or {% data variables.product.prodname_copilot_enterprise %}' |
| 11 | +--- |
| 12 | + |
| 13 | +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. |
| 14 | + |
| 15 | +>[!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" %} Billing & Licensing** option in your enterprise account's settings. |
| 16 | +
|
| 17 | +## Understand who can grant licenses |
| 18 | + |
| 19 | +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. |
| 20 | + |
| 21 | +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. |
| 22 | + |
| 23 | +## Map spending to groups of users |
| 24 | + |
| 25 | +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. |
| 26 | + |
| 27 | +For example, if you were running a pilot program for {% data variables.product.prodname_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. |
| 28 | + |
| 29 | +### Create a cost center |
| 30 | + |
| 31 | +1. Go to your enterprise account settings and click **{% octicon "credit-card" aria-hidden="true" %} Billing & Licensing**. |
| 32 | +1. In the left sidebar, click **Cost centers**, then click **New cost center**. |
| 33 | +1. Create the cost center. You don't need to add any repositories or organizations, because you will add users to the cost center directly in the next step. |
| 34 | + |
| 35 | + >[!NOTE] As a priority, a cost center is charged for a {% data variables.product.prodname_copilot_short %} license if the assigned **user** has been added to the cost center directly. As a fallback, a cost center is charged for the license if the **organization where the user receives access** has been added to the cost center. |
| 36 | +
|
| 37 | +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). |
| 38 | + |
| 39 | +## Receive alerts for overspending |
| 40 | + |
| 41 | +With {% data variables.product.github %}'s new billing platform, you can ensure your spending on {% data variables.product.prodname_copilot %} is manageable by setting a monthly budget. A budget for {% data variables.product.prodname_copilot_short %} won't limit usage, but you will receive notifications by email when spending exceeds certain percentages of the budget you've set. |
| 42 | + |
| 43 | +You can create the budget for the whole enterprise or for a cost center. |
| 44 | + |
| 45 | +1. Go to your enterprise account settings and click **{% octicon "credit-card" aria-hidden="true" %} Billing & Licensing**. |
| 46 | +1. In the left sidebar, click **Budgets and alerts**. |
| 47 | +1. Click **New budget**. |
| 48 | +1. Select **{% data variables.product.prodname_copilot_short %}** as the product, then configure the settings as required. You can choose who receives alerts when budget thresholds are reached. |
| 49 | +1. Click **Create budget**. |
| 50 | + |
| 51 | +## Visualize spending trends |
| 52 | + |
| 53 | +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. |
| 54 | + |
| 55 | +1. Go to your enterprise account settings and click **{% octicon "credit-card" aria-hidden="true" %} Billing & Licensing**. |
| 56 | +1. In the left sidebar, click **Usage**. |
| 57 | +1. In the "Metered usage" section, in the search field, enter `product:copilot`. To filter by cost center, add a query like `cost_center:ce-pilot-group`. |
| 58 | +1. To understand spending differences between {% data variables.product.prodname_copilot_business_short %} and {% data variables.product.prodname_copilot_enterprise_short %} plans, select the **Group: None** dropdown menu and click **Group: SKU**. |
| 59 | + |
| 60 | + |
| 61 | + |
| 62 | +## Optimize license usage |
| 63 | + |
| 64 | +When you begin rolling out {% data variables.product.prodname_copilot_short %} in a company, you may see low rates of adoption at first. An effective enablement process is essential to drive adoption of {% data variables.product.prodname_copilot_short %} in your company. Tailor this process to your company's needs and goals, and design it to help your teams understand how to use {% data variables.product.prodname_copilot_short %} effectively. |
| 65 | + |
| 66 | +To ensure your licenses are being used effectively, you can use the API to identify inactive users. We recommend sending these users a message with advice and resources for getting started. If a user remains inactive, you can revoke their license and assign it to another user. |
| 67 | + |
| 68 | +If you're not sure how best to distribute licenses, {% data variables.product.company_short %} has found that many successful rollouts offer a fully self-service model where developers can claim a license without approval. This allows people to get started quickly and ensures you're giving licenses to people who plan to use them. |
| 69 | + |
| 70 | +For detailed guidance, see: |
| 71 | + |
| 72 | +* [AUTOTITLE](/copilot/rolling-out-github-copilot-at-scale/driving-copilot-adoption-in-your-company) |
| 73 | +* [AUTOTITLE](/copilot/rolling-out-github-copilot-at-scale/setting-up-a-self-serve-process-for-github-copilot-licenses) |
| 74 | +* [AUTOTITLE](/copilot/rolling-out-github-copilot-at-scale/reminding-inactive-users) |
0 commit comments