# Setting up GitHub Copilot for your organization

Enable GitHub Copilot for your organization so members can write code faster.

## Enable GitHub Copilot

Owners of **organizations on GitHub Free or GitHub Team** can purchase Copilot Business for their organization. [Subscribe to Copilot Business](https://github.com/github-copilot/purchase?ref_product=copilot\&ref_type=purchase\&ref_style=button\&ref_plan=business).

If your organization is owned by an enterprise that has a Copilot subscription, you can ask your enterprise owner to enable Copilot for your organization. Go to <https://github.com/settings/copilot> and request access under "Get Copilot from an organization."

## Set policies

Control which Copilot features are available in your organization. See [Managing policies and features for GitHub Copilot in your organization](/en/copilot/how-tos/administer-copilot/manage-for-organization/manage-policies).

## Configure networking

If your organization members connect through an HTTP proxy server or firewall, add the required URLs to the allowlist. See [Copilot allowlist reference](/en/copilot/reference/copilot-allowlist-reference).

If your environment uses custom SSL certificates, install them on your members' machines. See [Configuring network settings for GitHub Copilot](/en/copilot/how-tos/configure-personal-settings/configure-network-settings#installing-custom-certificates).

## Grant access to members

Enable Copilot for some or all members of your organization. Consider starting with teams most likely to benefit, to discover potential blockers and demonstrate early success. See [Granting access to GitHub Copilot for members of your organization](/en/copilot/how-tos/administer-copilot/manage-for-organization/manage-access/grant-access).

> \[!TIP] If your organization belongs to an enterprise on GHE.com, users need additional setup to authenticate from their development environment. See [Using GitHub Copilot with an account on GHE.com](/en/copilot/how-tos/configure-personal-settings/authenticate-to-ghecom).

## Next steps

* **Set a governance posture that supports adoption**. Avoid over-restricting Copilot by delegating administration, enabling vetted features promptly, and aligning spend controls with your goals. See [Governing Copilot to support developer productivity](/en/copilot/tutorials/roll-out-at-scale/govern-at-scale/govern-for-adoption).
* **Explore self-service license management options**. Many successful rollouts use a self-service model where developers can claim a license without approval. See [Setting up a self-serve process for GitHub Copilot licenses](/en/copilot/tutorials/roll-out-at-scale/assign-licenses/set-up-self-serve-licenses).
* **Learn how to plan and implement an effective enablement process to drive Copilot adoption**. See [Driving GitHub Copilot adoption in your company](/en/copilot/tutorials/roll-out-at-scale/enable-developers/drive-adoption).
* **Enhance the development experience by enabling and training developers on the latest features**. For example, share context with Copilot Spaces and enable Copilot code review on pull requests. For an example showing how these features fit together, see [Integrating agentic AI into your enterprise's software development lifecycle](/en/copilot/tutorials/roll-out-at-scale/enable-developers/integrate-ai-agents).
* **Add Copilot cloud agent as a team member for asynchronous issue work**. See [Piloting GitHub Copilot cloud agent in your organization](/en/copilot/tutorials/cloud-agent/pilot-cloud-agent).