{"meta":{"title":"Exempting trusted actors from push protection","intro":"Reduce friction for trusted automation by granting exemptions from push protection.","product":"Security and code quality","breadcrumbs":[{"href":"/en/code-security","title":"Security and code quality"},{"href":"/en/code-security/how-tos","title":"How-tos"},{"href":"/en/code-security/how-tos/secure-your-secrets","title":"Secure your secrets"},{"href":"/en/code-security/how-tos/secure-your-secrets/manage-bypass-requests","title":"Manage bypass requests"},{"href":"/en/code-security/how-tos/secure-your-secrets/manage-bypass-requests/grant-exemptions","title":"Grant exemptions"}],"documentType":"article"},"body":"# Exempting trusted actors from push protection\n\nReduce friction for trusted automation by granting exemptions from push protection.\n\n> \\[!WARNING]\n> Push protection exemptions are designed for trusted automation that needs to push many commits with minimal friction. Exemptions may lead to leaked secrets, and should be granted with caution.\n\n## Granting exemptions for your repository\n\n> \\[!NOTE]\n> If an organization or enterprise owner configures delegated bypass at the organization or enterprise level, the repository-level settings are disabled.\n\n1. On GitHub, navigate to the main page of the repository.\n\n2. Under your repository name, click ** Settings**. If you cannot see the \"Settings\" tab, select the **** dropdown menu, then click **Settings**.\n\n \n\n3. In the \"Security and quality\" section of the sidebar, click ** Advanced Security**.\n\n4. Under \"Secret Protection,\" ensure that push protection is enabled for the repository.\n\n5. Under \"Push protection,\" to the right of \"Who can bypass push protection for secret scanning,\" select the dropdown menu, then click **Specific roles or teams**.\n\n6. Under \"Bypass list,\" click **Add role or team**.\n\n7. In the dialog box, select the roles and teams that you want to add to the bypass list, then click **Add selected**.\n\n > \\[!NOTE]\n > You can't add secret teams to the bypass list.\n\n8. To fully exempt the actors from push protection, to the right of the actors' details, select , then click **Exempt**.\n\n## Granting exemptions for your organization\n\n1. On GitHub, navigate to the main page of the organization.\n\n2. Under your organization name, click ** Settings**. If you cannot see the \"Settings\" tab, select the **** dropdown menu, then click **Settings**.\n\n \n\n3. In the \"Security\" section of the sidebar, select the ** Advanced Security** dropdown menu, then click **Configurations**.\n\n4. Create a new custom security configuration, or edit an existing one. See [Creating a custom security configuration](/en/code-security/how-tos/secure-at-scale/configure-organization-security/establish-complete-coverage/create-custom-configuration).\n\n5. When defining the custom security configuration, under \"Secret scanning,\" ensure that \"Push protection\" is set to **Enabled**.\n\n6. Under \"Push protection,\" to the right of \"Bypass privileges,\" select the dropdown menu, then click **Specific actors**.\n\n7. Select the **Select actors** dropdown menu, then choose the actors you want to add to the bypass list.\n\n > \\[!NOTE]\n >\n > * You can't add secret teams to the bypass list.\n\n8. To fully exempt the actors from push protection, to the right of the actors' details, select , then click **Exempt**.\n\n9. Click **Save configuration**.\n\n10. Apply the security configuration to repositories in your organization. See [Applying a custom security configuration](/en/code-security/how-tos/secure-at-scale/configure-organization-security/establish-complete-coverage/apply-custom-configuration).\n\n## Granting exemptions for your enterprise\n\n1. Navigate to your enterprise. For example, from the [Enterprises](https://github.com/settings/enterprises?ref_product=ghec\\&ref_type=engagement\\&ref_style=text) page on GitHub.com.\n\n2. At the top of the page, click **Settings**.\n\n3. In the left sidebar, click ** Advanced Security Code security**.\n\n4. In the \"Security\" section of the sidebar, select the ** Advanced Security** dropdown menu, then click **Configurations**.\n\n5. Create a new custom security configuration, or edit an existing one. See [Creating a custom security configuration for your enterprise](/en/code-security/how-tos/secure-at-scale/configure-enterprise-security/establish-complete-coverage/create-custom-configuration).\n\n6. Under **Secret scanning**, ensure **Push protection** is enabled.\n\n7. Under \"Push protection,\" to the right of \"Bypass privileges,\" select the dropdown menu, then click **Specific actors**.\n\n > \\[!NOTE]\n > You can't add secret teams to the bypass list.\n\n8. Select the **Select actors** dropdown menu, then choose the actors you want to add to the bypass list.\n\n9. To fully exempt the actors from push protection, to the right of the actors' details, select , then click **Exempt**.\n\n10. Click **Save configuration**.\n\n11. Apply the security configuration to organizations and repositories in your enterprise. See [Applying a custom security configuration to your enterprise](/en/code-security/how-tos/secure-at-scale/configure-enterprise-security/establish-complete-coverage/apply-custom-configuration)."}