Note
Starting September 3, 2024, GitHub Enterprise Cloud customers who use a single organization will be automatically upgraded to an enterprise account at no additional cost.
When should I create an enterprise account?
GitHub Enterprise Cloud allows you to create an enterprise account, which enables collaboration between multiple organizations and gives administrators a single point of visibility and management. See "About enterprise accounts."
In most cases, you can create an enterprise account yourself.
- When you start a free trial of GitHub Enterprise Cloud, you'll create an enterprise account as part of the process. See "Setting up a trial of GitHub Enterprise Cloud."
- If you currently use GitHub Enterprise Cloud with a single organization, you can upgrade to an enterprise account by following the steps later in this article.
You'll need help creating an enterprise account for:
- GitHub Enterprise Server
- Invoicing
- Managing GitHub Copilot Business licenses without adopting GitHub Enterprise
In these cases, contact GitHub's Sales team.
What will happen after I upgrade my organization?
The following changes also apply to single organizations that are automatically upgraded to an enterprise account. For details, see the the GitHub Blog.
- Ownership transfer: Your organization will automatically be owned by the enterprise account. For details, see "Adding organizations to your enterprise."
- Ownership roles: All organization owners will become enterprise owners.
- Billing details: The organization’s billing details will now apply to the enterprise account.
- Billing managers: All organization billing managers will become enterprise billing managers.
- Billing process: GitHub will bill the enterprise account for usage within all organizations owned by the enterprise.
- Enterprise account name: During the upgrade, the new enterprise account name will match your organization name or be as close as possible if taken. You can rename it after the upgrade.
- SAML SSO: Existing SAML SSO will stay at the organization level after being added to the new enterprise account. You can configure SSO at the enterprise level post-upgrade, which will override the organization level. Existing PATs and SAML-authorized tokens will remain unchanged.
- Policies: The new enterprise account starts with no policies, so existing organization policies won't be overridden.
- Spending limits: Existing organization spending limits transfer to the new enterprise account. Post-upgrade, billing is handled at the enterprise level. To adjust spending limits, under "Settings" in the enterprise account sidebar, select Billing.
- Coupons: Existing coupons will carry over to the new enterprise account with no interruptions.
- Workflow permissions: The new enterprise account will inherit your organization's workflow permissions. If the organization has a permissive setting ("Read and write"), the enterprise account will also default to permissive. Otherwise, it defaults to restrictive ("Read repository contents and packages"). For workflows with the id-token permission, the default changes to read-only due to a February 2023 update. Add an explicit permissions block in these workflows to grant the required permissions.
Upgrading an organization to an enterprise account
-
In the upper-right corner of any page on GitHub, click your profile photo, then click Settings.
-
In the "Access" section of the sidebar, click Organizations.
-
Next to the organization, click Settings.
-
If you are an organization owner, in the "Access" section of the sidebar, click Billing and plans.
-
Click Upgrade to enterprise account.
-
Under "Enterprise name", type a name for your enterprise account.
-
Under "Enterprise URL slug", type a slug to be used in the URL for your enterprise.
For example, if you choose
octo-enterprise
, the URL will behttps://github.com/enterprises/octo-enterprise
. -
Click Confirm and upgrade.
-
Read the warnings, then click Create enterprise account.
Next steps
Follow the "Get started with your enterprise account" learning path.