Restricting deploy keys in your organization

To protect your organization's data, you can configure permissions for creating deploy keys in your organization.

누가 이 기능을 사용할 수 있나요?

Organization owners.

You can choose whether members can create deploy keys for repositories in your organization.

By default, new organizations are configured to disallow the creation of deploy keys in repositories.

Organization owners can restrict the creation of deploy keys to help prevent sensitive information from being exposed. For more information, see "조직에서 데이터 유출을 방지하기 위한 모범 사례" and "배포 키 관리." If you want more fine-grained control over permissions, consider using a GitHub App instead. See "GitHub 앱 개요."

If your organization is owned by an enterprise account, you may not be able to configure this setting for your organization, if an enterprise owner has set a policy at the enterprise level. For more information, see "엔터프라이즈에서 리포지토리 관리 정책 적용."

Warning

Changing this setting to disabled will result in existing deploy keys being disabled in all repositories in the organization. Scripts, apps, or workflows that create, use, or delete deploy keys will no longer work.

  1. GitHub의 오른쪽 위 모서리에서 프로필 사진을 선택하고 조직을 클릭합니다.
  2. 조직 옆에 있는 설정을 클릭합니다.
  3. 사이드바의 "액세스" 섹션에서 구성원 권한을 클릭합니다.
  4. Under "Deploy keys", review the information about changing the setting, click Enabled or Disabled.
  5. Click Save.