# 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. For more information, see [Roles in an organization](/en/enterprise-server@3.21/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization).
## What happens when I change my organization's name?
After changing your organization's name, your old organization name becomes available for someone else to claim. When you change your organization's name, most references to your repositories under the old organization name automatically change to the new name. However, some links to your profile won't automatically redirect.
### Changes that occur automatically
* GitHub 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 [Managing remote repositories](/en/enterprise-server@3.21/get-started/git-basics/managing-remote-repositories).
* Previous Git commits will also be correctly attributed to users within your organization.
* If the account namespace includes any packages or container images stored in a GitHub Packages registry, GitHub transfers the packages and container images to the new namespace. By renaming your account, you may break projects that depend on these packages.
### Changes that aren't automatic
After changing your organization's name:
* Links to your previous organization profile page, such as `https://HOSTNAME/previousorgname`, will return a 404 error. We recommend you update links to your organization from other sites.
* 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](/en/enterprise-server@3.21/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#mentioning-people-and-teams) redirects for teams that use the old organization's name.
## Changing your organization's name
1. In the upper-right corner of GitHub, click your profile picture, then click ** Organizations**.
2. Select an organization by clicking on it.
3. Under your organization name, click ** Settings**. If you cannot see the "Settings" tab, select the **** dropdown menu, then click **Settings**.
4. Near the bottom of the settings page, under "Danger zone", click **Rename organization**.
5. Read the warning messages, then, if you want to go ahead, click **I understand, let's rename my organization**.
6. Type a new name for your organization, then click **Change organization's name**.
## Further reading
* [Troubleshooting commits](/en/enterprise-server@3.21/pull-requests/committing-changes-to-your-project/troubleshooting-commits#commits-are-linked-to-the-wrong-user)