title | intro | permissions | versions | type | topics | shortTitle | ||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
Enabling delegated alert dismissal for secret scanning |
You can use delegated alert dismissal to control who can dismiss an alert found by {% data variables.product.prodname_secret_scanning %}. |
{% data reusables.permissions.delegated-alert-dismissal %} |
|
how_to |
|
Delegated alert dismissal |
{% data reusables.advanced-security.delegated-alert-dismissal-beta %}
{% data reusables.security.delegated-alert-dismissal-intro %}
[!NOTE] If an organization owner configures delegated alert dismissal via an enforced security configuration, the settings can't be changed at the repository level.
{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.navigate-to-code-security-and-analysis %}
- Under "{% data variables.product.prodname_secret_protection %}", to the right of "Prevent direct alert dismissals", click Enable.
You must configure delegated dismissal for your organization using a custom security configuration. You can then apply the security configuration to all (or selected) repositories in your organization.
- Create a new custom security configuration, or edit an existing one. See AUTOTITLE.
- When defining the custom security configuration, under "{% data variables.product.prodname_secret_scanning_caps %}", ensure that the dropdown menu for "Prevent direct alert dismissals" is set to Enabled.
- Click Save configuration.
- Apply the security configuration to all (or selected) repositories in your organization. See AUTOTITLE.
To learn more about security configurations, see AUTOTITLE.