title: Not enough GitHub Advanced Security licenses
shortTitle: Not enough GHAS licenses
intro: >-
If you are on a subscription-based billing model for GHAS, you need available
GHAS licenses to enable GHAS features on a private{% ifversion ghec or ghes %}
or internal{% endif %} repository.
permissions: '{% data reusables.permissions.security-org-enable %}'
versions:
feature: security-configurations
topics:
- Code Security
- Secret Protection
- Organizations
- Security
If you are on a volume / subscription-based billing model for {% data variables.product.prodname_GHAS %} (GHAS), you must have an available GHAS license for any additional unique active committers to enable GHAS features on a private{% ifversion ghec or ghes %} or internal{% endif %} repository. To learn about GHAS licensing, as well as unique and active committers, see AUTOTITLE.
If you try to apply a {% data variables.product.prodname_security_configuration %} with GHAS features to your repositories and don't have enough GHAS licenses, the configuration will only be successfully applied to public repositories. For private {% ifversion ghec or ghes %}and internal {% endif %}repositories, only free security features will be enabled due to the license limitation, resulting in the following outcomes:
- Free security features enabled in the configuration will be enabled for all private {% ifversion ghec or ghes %}and internal {% endif %}repositories.
- GHAS features will not be enabled for any private {% ifversion ghec or ghes %}or internal {% endif %}repositories.
- The {% data variables.product.prodname_security_configuration %} will not be applied to any private {% ifversion ghec or ghes %}or internal {% endif %}repositories, since only some features from the configuration are enabled.
For more information on managing GHAS licenses for your organization, see AUTOTITLE.