When you create an enterprise, you choose a "slug" for the enterprise, which is a string used in the URL for your enterprise. For example, if you chose
octo-enterprise as the slug, the URL for your enterprise would be
If your company pays for GitHub Enterprise Cloud by credit card or PayPal, you can change the slug in the settings for your enterprise. When you change the slug, GitHub does not set up any redirects from the old URL. Your old enterprise slug will immediately become available for another customer to use.
Note: If you pay for GitHub Enterprise Cloud via invoice, or if your enterprise uses Enterprise Managed Users, you must contact GitHub's Sales team to change your enterprise slug.
Before changing the slug for an enterprise, ensure you have considered any parts of your enterprise's configuration, automations, or processes that may depend on the old enterprise slug. To minimize disruption, you should address these points either immediately before or immediately after changing the slug.
Parts of your system that may be affected by changing the slug include, but are not limited to, the following points.
If you have enabled SAML single sign-on (SSO) at the enterprise level, you will need to reconfigure the settings in your identity provider (IdP) to use the new enterprise slug. When you change your slug, existing IdP sessions are not revoked, but your members won't be able to use SSO to access resources in your enterprise until you update the IdP settings. If you have enabled SAML or SCIM at the organization level, changing the slug will not affect SSO. For more information, see "Configuring SAML single sign-on for your enterprise."
Before changing the slug, to ensure you will have access to your enterprise even if SSO is not working, we recommend you download the recovery codes for your enterprise. For more information, see "Downloading your enterprise account's single sign-on recovery codes."
Many GitHub API endpoints for managing an enterprise take the enterprise slug as a parameter. If you use these endpoints in automations, you will need to update the API calls to use the new slug. API calls that use the old slug will stop working immediately. The enterprise ID, which can be used as an alternative to the slug in many cases, is not affected by a slug change.
If you use OpenID Connect (OIDC) in GitHub Actions workflows, and have configured your cloud provider to only accept tokens from a unique URL that includes your enterprise slug, you will need to update the settings in your cloud provider. To prevent workflows from failing, the most robust option is to configure your provider to accept tokens from both the old and new slug just before you change the slug. For more information, see "About security hardening with OpenID Connect."
Note: Before changing the slug for an enterprise, make sure you have understood the potential consequences. For more information, see "Prerequisites."
In the top-right corner of GitHub.com, click your profile photo, then click Your enterprises.
In the list of enterprises, click the enterprise you want to view.
In the enterprise account sidebar, click Settings.
At the bottom of the page, in the "Danger zone" section, click Change enterprise URL slug.
In the "Change enterprise URL slug" dialog, follow the instructions, then click Change enterprise slug URL.