# 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 [푸시 보호 요청 무시](/ko/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 [푸시 보호 바이패스 요청 검토](/ko/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
* [푸시 보호를 위해 위임된 바이패스 사용](/ko/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](/ko/code-security/secret-scanning/using-advanced-secret-scanning-and-push-protection-features/delegated-bypass-for-push-protection/enabling-delegated-bypass-for-push-protection)
* [푸시 보호 바이패스 요청 검토](/ko/code-security/security-overview/reviewing-requests-to-bypass-push-protection)