{"meta":{"title":"Buying Advanced Security for your organization or enterprise","intro":"How to buy licenses for GitHub Advanced Security whether you have usage-based or volume/subscription billing.","product":"Billing and payments","breadcrumbs":[{"href":"/en/billing","title":"Billing and payments"},{"href":"/en/billing/how-tos","title":"How-tos"},{"href":"/en/billing/how-tos/products","title":"Products"},{"href":"/en/billing/how-tos/products/buy-advanced-security","title":"Buy Advanced Security"}],"documentType":"article"},"body":"# Buying Advanced Security for your organization or enterprise\n\nHow to buy licenses for GitHub Advanced Security whether you have usage-based or volume/subscription billing.\n\n## Checking your current plan\n\nYou must use a GitHub Team or GitHub Enterprise plan before you can enable GitHub Secret Protection or GitHub Code Security on private repositories.\n\n1. Navigate to your organization or enterprise. For example, from the [Organizations](https://github.com/settings/organizations?ref_product=github\\&ref_type=engagement\\&ref_style=text) or [Enterprises](https://github.com/settings/enterprises?ref_product=ghec\\&ref_type=engagement\\&ref_style=text) pages on GitHub.com.\n2. From the list of \"Billing & licensing\" pages, click **Licensing**.\n\nYour current plan is shown with any options to upgrade to a different plan.\n\n## Metered billing users\n\nIf your organization or enterprise uses metered billing, then you are ready to start enabling GitHub Secret Protection and GitHub Code Security. Whenever you enable a feature or apply a configuration, a modal dialog shows detailed information with estimated billing changes. You can confirm your change or return to the page without making changes.\n\nThe most effective way to control and enable these features is using security configurations, see [Enabling security features at scale](/en/code-security/concepts/security-at-scale/organization-security).\n\n## Volume/subscription users\n\nIf you use volume/subscription billing, then you will need to purchase licenses before you can start using GitHub Secret Protection or GitHub Code Security on private or internal repositories.\n\n1. Navigate to your organization or enterprise. For example, from the [Organizations](https://github.com/settings/organizations?ref_product=github\\&ref_type=engagement\\&ref_style=text) or [Enterprises](https://github.com/settings/enterprises?ref_product=ghec\\&ref_type=engagement\\&ref_style=text) pages on GitHub.com.\n\n2. From the list of \"Billing & licensing\" pages, click **Licensing**.\n\n3. To the right of \"GitHub Advanced Security\", click **Buy Advanced Security**.\n\n   ![Screenshot of the Advanced Security section of the licensing screen. The \"Buy Advanced Security\" button is outlined in orange.](/assets/images/help/enterprises/ghas-buy-advanced-security-button.png)\n\n4. Confirm your billing information and payment method.\n\n5. Under \"How many committers do you want to include?\", enter the number of committers you want to purchase licenses for.\n\n6. Click **Purchase Advanced Security**.\n\n> \\[!TIP]\n> To see how license use by committers is measured, see [GitHub Advanced Security license billing](/en/billing/concepts/product-billing/github-advanced-security).\n\n## Further reading\n\n* [Planning a trial of GitHub Advanced Security](/en/code-security/tutorials/trialing-github-advanced-security/planning-a-trial-of-ghas)\n* [Enabling security features at scale](/en/code-security/concepts/security-at-scale/organization-security)"}