title | intro | permissions | allowTitleToDifferFromFilename | versions | type | topics | shortTitle | redirect_from | ||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Managing {% data variables.product.prodname_GHAS %} features for your enterprise |
You can control {% data variables.product.prodname_GHAS %} features that secure and analyze code across all organizations owned by your enterprise. |
Enterprise owners can manage {% data variables.product.prodname_AS %} features for organizations in an enterprise. |
true |
|
how_to |
|
Manage {% data variables.product.prodname_GHAS %} |
|
You can use {% data variables.product.prodname_AS %} features to harden security for the organizations in your enterprise.
{% ifversion security-configurations %}{% data reusables.security-configurations.enable-security-features-with-gh-config %}
To manage individual {% data variables.product.prodname_GHAS %} features, {% else %}To streamline management of {% data variables.product.prodname_AS %}, {% endif %}you can enable or disable each feature for all existing and/or new repositories within the organizations owned by your enterprise.
{% ifversion security-configurations-ghes-only %}
Warning
You should communicate any changes you plan to make to existing feature enablement settings to organization owners before making them, so as not to impact existing security configurations that have been rolled out by organizations in your enterprise.
{% endif %}
{% data reusables.secret-scanning.secret-scanning-enterprise-level-api %}
For information about buying a license for {% data variables.product.prodname_GHAS %}, see AUTOTITLE.
If you have disallowed {% data variables.product.prodname_GHAS %} for an organization, that organization will not be affected by enabling a feature for all existing repositories or for all new repositories. For more information about disallowing {% data variables.product.prodname_GHAS %} for an organization, see AUTOTITLE.
When you enable one or more security and analysis features for existing repositories, you will see any results displayed on {% data variables.product.prodname_dotcom %} within minutes.
{% data reusables.security.security-and-analysis-features-enable-read-only %}
{% data reusables.advanced-security.note-org-enable-uses-seats %}
{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.advanced-security-tab %}
-
Optionally, enable or disable a feature for all existing repositories.
- To the right of the feature, click Disable all or Enable all. If the control for "{% data variables.product.prodname_GHAS %}" is disabled, you have no available licenses for {% data variables.product.prodname_GHAS %}.
- To confirm the change, click the Enable/Disable all or Enable/Disable for eligible repositories button in the dialog that is displayed.
-
Optionally, to enable or disable a feature automatically when new private and internal repositories{% ifversion secret-scanning-user-owned-repos %}, user namespace repositories{% endif %}, or public repositories and repositories with {% data variables.product.prodname_GHAS %} enabled are created, select the checkbox below the feature.{% ifversion org-npp-enablement-security-configurations %}
-
Optionally, to enable the scanning of non-provider patterns, to the right of "Scan for non-provider patterns", click Enable all. To learn more about scanning for non-provider patterns, see AUTOTITLE and AUTOTITLE.{% endif %}
-
Optionally, to include a resource link in the message that members will see when they attempt to push a secret, select Add a resource link in the CLI and web UI when a commit is blocked, then type a URL, and click Save link.
[!NOTE] When a custom link is configured for an organization, the organization-level value overrides the custom link set for the enterprise. See AUTOTITLE.