Skip to main content
Skip to content

Managing GitHub Copilot in the cloud for your organization

Enable Copilot in the cloud for your members and control the repositories where it is available.

Who can use this feature?

Organization owners

Copilot in the cloud is a connected experience that lets users start and resume cloud sessions across the GitHub website, GitHub Mobile, Copilot CLI, and the Copilot app. See GitHub Copilot on GitHub.com and GitHub Mobile.

The Copilot in the cloud policy determines:

  • Whether users can access the chat interface or assign work to Copilot on the GitHub website and GitHub Mobile
  • Whether users can start sessions in cloud sandboxes from local clients (Copilot CLI and the Copilot app)

This feature is enabled by default. To ensure data security, chat sessions are scoped by default to either a single organization or the user's personal repositories. If you have enabled single sign-on (SSO), users will need to authenticate with SSO to access session data from a repository associated with that organization.

Enabling Copilot in the cloud for your members

Note

Copilot policies are also managed at the enterprise level. If your enterprise owner has selected a specific policy, such as enabling a feature everywhere, disabling it everywhere, or enabling it for selected organizations only, you cannot override that setting at the organization level. For information on how policies combine, see GitHub Copilot policies for enterprises and organizations.

Copilot in the cloud is enabled by default for organization members assigned a GitHub Copilot Enterprise or Copilot Business license by your organization.

Organizations with Copilot Enterprise or Copilot Business can enable or disable these features for members on the Copilot policies page for their organization. See Enabling Copilot features in your organization.

  • For the "Copilot in the cloud" policy, select "Enabled".
  • Optionally, for the "MCP servers on GitHub.com" policy, select "Enabled".

Disabling the cloud agent in your repositories

By default, GitHub's cloud agent is available in all repositories in an organization where Copilot in the cloud is enabled. However, you can block the agent from being used in some or all repositories owned by your organization.

  1. In the upper-right corner of GitHub, click your profile picture, then click Organizations.

  2. Select an organization by clicking it.

  3. Under your organization name, click Settings. If you cannot see the "Settings" tab, select the dropdown menu, then click Settings.

    Screenshot of the tabs in an organization's profile. The "Settings" tab is outlined in dark orange.

  4. In the sidebar, under "Code, planning, and automation", click Copilot, and then click Cloud.

  5. Use the "Repository access" control to define which repositories allow the agent.

  6. If you choose "Selected repositories", in the "Select repositories" dialog, select the repositories that allow Copilot cloud agent, then click Select.

Once the agent is enabled for a repository, any user with access to Copilot and write permission for the repository can delegate work to Copilot.

Controlling automations in your repositories

Automations let users run Copilot sessions automatically, on a schedule or in response to events. See Copilot automations.

Automations are allowed by default in repositories where Copilot in the cloud is available. You can control whether automations are allowed in repositories owned by your organization, separately from the Copilot in the cloud policy.

  1. In the upper-right corner of GitHub, click your profile picture, then click Organizations.

  2. Select an organization by clicking it.

  3. Under your organization name, click Settings. If you cannot see the "Settings" tab, select the dropdown menu, then click Settings.

    Screenshot of the tabs in an organization's profile. The "Settings" tab is outlined in dark orange.

  4. In the sidebar, under "Code, planning, and automation", click Copilot, and then click Cloud.

  5. To allow or block automations, update the Allow automations setting.

Managing the agent firewall for your organization

Organization owners can configure the firewall for their organization to determine which external hosts and URLs the cloud agent can access. For more information, see Customizing or disabling the firewall for GitHub Copilot.

Next steps