title | shortTitle | intro | permissions | versions | topics | |||||
---|---|---|---|---|---|---|---|---|---|---|
Not enough GitHub Advanced Security licenses |
Not enough GHAS licenses |
You need available GHAS licenses to enable GHAS features on a private{% ifversion ghec or ghes %} or internal{% endif %} repository. |
{% data reusables.security-configurations.security-configurations-permissions %} |
|
|
{% note %}
Note: {% data reusables.security-configurations.security-configurations-beta-note-short %}
{% endnote %}
You must have an available {% data variables.product.prodname_GH_advanced_security %} (GHAS) license for each unique active committer 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."