title | intro | redirect_from | versions | topics | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Renaming an organization |
If your project or company has changed names, you can update the name of your organization to match. |
|
|
|
Tip
Only organization owners can rename an organization. {% data reusables.organizations.new-org-permissions-more-info %}
After changing your organization's name, your previous organization name will be unavailable for anyone to claim for 90 days. When you change your organization's name, most references to your repositories under the previous organization name automatically change to the new name. However, some links to your profile won't automatically redirect.
- {% data variables.product.prodname_dotcom %} automatically redirects references to your repositories. Web links to your organization's existing repositories will continue to work. This can take a few minutes to complete after you initiate the change.
- You can continue pushing your local repositories to the old remote tracking URL without updating it. However, we recommend you update all existing remote repository URLs after changing your organization name. Because your old organization name is available for use by anyone else after you change it, the new organization owner can create repositories that override the redirect entries to your repository. For more information, see "AUTOTITLE."
- Previous Git commits will also be correctly attributed to users within your organization.{% ifversion fpt or ghec %}
- {% data reusables.accounts.rename-account-repo-namespace-retirement %}{% endif %}
- {% data reusables.package_registry.rename-account-namespace-retirement %}
After changing your organization's name:
- Links to your previous organization profile page, such as
https://{% data variables.product.product_url %}/previousorgname
, will return a 404 error. We recommend you update links to your organization from other sites{% ifversion fpt or ghec %}, such as your LinkedIn or Twitter profiles{% endif %}. - API requests that use the old organization's name will return a 404 error. We recommend you update the old organization name in your API requests.
- There are no automatic @mention redirects for teams that use the old organization's name.{% ifversion ghec %}
- If SAML single sign-on (SSO) and/or is enabled for the organization, you must update the organization name in the application for {% data variables.product.prodname_ghe_cloud %} on your identity provider (IdP). If you don't update the organization name on your IdP, members of the organization will no longer be able to authenticate with your IdP to access the organization's resources. For more information, see "AUTOTITLE."
- If SCIM is enabled for the organization, you must update the organization name in the application for {% data variables.product.prodname_ghe_cloud %} on your identity provider (IdP). If you don't update the organization name within the SCIM settings on your IdP, you will not be able to provision or deprovision users.{% endif %}
{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %}
- Near the bottom of the settings page, under "Danger zone", click Rename organization.
- Read the warning messages, then, if you want to go ahead, click I understand, let's rename my organization.
- Type a new name for your organization, then click Change organization's name.