{"meta":{"title":"Adding GitHub Copilot cloud agent to your organization","intro":"Enable Copilot cloud agent for your members and control the repositories where it is available.","product":"GitHub Copilot","breadcrumbs":[{"href":"/en/copilot","title":"GitHub Copilot"},{"href":"/en/copilot/how-tos","title":"How-tos"},{"href":"/en/copilot/how-tos/administer-copilot","title":"Administer Copilot"},{"href":"/en/copilot/how-tos/administer-copilot/manage-for-organization","title":"Manage for organization"},{"href":"/en/copilot/how-tos/administer-copilot/manage-for-organization/add-copilot-cloud-agent","title":"Add Copilot cloud agent"}],"documentType":"article"},"body":"# Adding GitHub Copilot cloud agent to your organization\n\nEnable Copilot cloud agent for your members and control the repositories where it is available.\n\n> \\[!NOTE]\n> For an introduction to Copilot cloud agent, see [About GitHub Copilot cloud agent](/en/copilot/concepts/agents/cloud-agent/about-cloud-agent).\n\n## Enabling Copilot cloud agent for your members\n\n> \\[!NOTE]\n> 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](/en/copilot/concepts/policies).\n\nCopilot cloud agent and use of third-party MCP servers are disabled by default for organization members assigned a GitHub Copilot Enterprise or Copilot Business license by your organization.\n\nOrganizations with Copilot Enterprise or Copilot Business can enable these features for members on the Copilot policies page for their organization. See [Enabling Copilot features in your organization](/en/copilot/how-tos/administer-copilot/manage-for-organization/manage-policies#enabling-copilot-features-and-models-in-your-organization).\n\n* For the \"Copilot cloud agent\" policy, select \"Enabled\".\n* For the \"MCP servers on GitHub.com\" policy, select \"Enabled\".\n\n## Disabling or enabling Copilot cloud agent in your repositories\n\nBy default, Copilot cloud agent is available in all repositories for users who have access to the agent, but you can block it from being used in some or all repositories owned by your organization. You can manage repository availability using the following instructions, or programmatically using the [REST API](/en/rest/copilot/copilot-cloud-agent-management).\n\n1. In the upper-right corner of GitHub, click your profile picture, then click ** Organizations**.\n2. Select an organization by clicking on it.\n3. Under your organization name, click ** Settings**. If you cannot see the \"Settings\" tab, select the **** dropdown menu, then click **Settings**.\n\n \n4. In the sidebar, under \"Code, planning, and automation\", click ** Copilot**, and then click **Cloud agent**.\n5. Use the \"Repository access\" control to define which repositories allow Copilot cloud agent.\n6. If you choose \"Selected repositories\", in the \"Select repositories\" dialog, select the repositories that allow Copilot cloud agent, then click **Select**.\n\nOnce Copilot cloud agent is enabled for a repository, any user with access to Copilot cloud agent and write permission for the repository can delegate work to Copilot.\n\n## Controlling automations in your repositories\n\nAutomations let users run Copilot cloud agent automatically, on a schedule or in response to events. See [About Copilot automations](/en/copilot/concepts/agents/cloud-agent/about-automations).\n\nAutomations are allowed by default in repositories where Copilot cloud agent is available. You can control whether automations are allowed in repositories owned by your organization, separately from the Copilot cloud agent policy.\n\n1. In the upper-right corner of GitHub, click your profile picture, then click ** Organizations**.\n2. Select an organization by clicking on it.\n3. Under your organization name, click ** Settings**. If you cannot see the \"Settings\" tab, select the **** dropdown menu, then click **Settings**.\n\n \n4. In the sidebar, under \"Code, planning, and automation\", click ** Copilot**, and then click **Cloud agent**.\n5. To allow or block automations, toggle the **Allow automations** setting.\n\n## Managing the agent firewall for your organization\n\nOrganization owners can configure the Copilot cloud agent firewall for their organization, including whether it is enabled for the organization and which external hosts and URLs the agent can access. For more information, see [Customizing or disabling the firewall for GitHub Copilot](/en/copilot/how-tos/copilot-on-github/customize-copilot/customize-the-firewall).\n\n## Next steps\n\n* Tell the members of repositories where Copilot cloud agent is available that they can delegate work to the cloud agent.\n* Configure the default runner type for Copilot cloud agent in your organization. For more information, see [Configuring runners for GitHub Copilot cloud agent in your organization](/en/copilot/how-tos/administer-copilot/manage-for-organization/configure-runner-for-coding-agent).\n* Encourage members to educate themselves about setting up their repository to get the most from Copilot cloud agent. Useful resources:\n\n * [Best practices for using GitHub Copilot to work on tasks](/en/copilot/tutorials/cloud-agent/get-the-best-results)\n * [Configure the development environment](/en/copilot/how-tos/copilot-on-github/customize-copilot/customize-cloud-agent/customize-the-agent-environment)\n * [Risks and mitigations for GitHub Copilot cloud agent](/en/copilot/concepts/agents/cloud-agent/risks-and-mitigations)"}