# Managing requests to bypass push protection
As a member of the bypass list for an organization or repository, you can review bypass requests from other members of the organization or repository.
When delegated bypass for push protection is enabled, designated reviewers can approve or deny requests from contributors who want to push commits containing secrets.
This article explains how to review and manage bypass requests for repositories and organizations.
For more information about how bypass requests work, see [プッシュ保護の要求をバイパスする](/ja/code-security/concepts/secret-security/about-bypass-requests-for-push-protection).
## Managing requests for a repository
1. GitHub で、リポジトリのメイン ページに移動します。
2. リポジトリ名の下にある \[ ** Security and quality** ] タブをクリックします。\[ Security and quality] タブが表示されない場合は、 **** ドロップダウン メニューを選択し、\[ ** Security and quality**] をクリックします。
3. 左側のサイドバーの \[要求] で、\[**プッシュ保護バイパス**] をクリックします。
4. Select the **All statuses** dropdown menu, then click **Open** to view requests that are awaiting review, and those that have been approved but for which the commits haven't been pushed to the repository yet.
5. Click the request that you want to review.
6. Review the details of the request.
7. 必要に応じて、レビュー コメントを追加します。 コメントは、要求の確認タイムラインと secret scanning アラート タイムラインに追加されます。 たとえば、監査や報告の目的で要求が承認または拒否された理由を説明し、共同作成者が実行すべき次の手順を提案したい場合があります。
8. To allow the contributor to push the commit containing the secret, click **Approve bypass request**. Or, to require the contributor to remove the secret from the commit, click **Deny bypass request**.
## Managing requests for an organization
Organization owners, security managers and organization members with the relevant fine-grained permission (via a custom role) can review and manage bypass requests for all repositories in the organization using security overview. See [プッシュ保護をバイパスする要求の確認](/ja/code-security/security-overview/reviewing-requests-to-bypass-push-protection).
## Filtering requests
You can filter requests by:
* Approver (member of the bypass list)
* Requester (contributor making the request)
* Timeframe
* Status
### Filtering by status
The following statuses are assigned to a request:
| Status | Description |
| ----------- | ---------------------------------------------------------------------------------------------------------------------------- |
| `Cancelled` | The request has been canceled by the contributor. |
| `Completed` | The request has been approved and the commit(s) have been pushed to the repository. |
| `Denied` | The request has been reviewed and denied. |
| `Expired` | The request has expired. Requests are valid for 7 days. |
| `Open` | The request has either not yet been reviewed, or has been approved but the commit(s) have not been pushed to the repository. |
## Further reading
* [プッシュ保護用の委任バイパス](/ja/code-security/secret-scanning/using-advanced-secret-scanning-and-push-protection-features/delegated-bypass-for-push-protection/about-delegated-bypass-for-push-protection)
* [Enabling delegated bypass for push protection](/ja/code-security/secret-scanning/using-advanced-secret-scanning-and-push-protection-features/delegated-bypass-for-push-protection/enabling-delegated-bypass-for-push-protection)
* [プッシュ保護をバイパスする要求の確認](/ja/code-security/security-overview/reviewing-requests-to-bypass-push-protection)