Restricting deploy keys in your organization

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

Quem pode usar esse recurso?

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 "Melhores práticas para evitar vazamentos de dados na sua organização" and "Gerenciar chaves de implantação." If you want more fine-grained control over permissions, consider using a GitHub App instead. See "Visão geral de aplicativos 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 "Aplicar as políticas de gerenciamento do repositório na sua empresa."

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. No canto superior direito de GitHub, selecione sua foto de perfil e selecione Suas organizações.
  2. Ao lado da organização, clique em Configurações.
  3. Na seção "Acesso" na barra lateral, clique em Privilégios de membros.
  4. Under "Deploy keys", review the information about changing the setting, click Enabled or Disabled.
  5. Click Save.