Managing organization settings

If your project or company has changed names, you can update the name of your organization to match.

To make someone else the owner of an organization account, you must add a new owner and then remove yourself from the account.

To protect your organization's data, you can configure permissions for creating repositories in your organization.

You can allow organization members with admin permissions to a repository to delete or transfer the repository, or limit the ability to delete or transfer repositories to organization owners only.

To protect your organization's data, you can configure permissions for changing repository visibility in your organization.

You can can allow or prevent the forking of any private and internal repositories owned by your organization.

To protect your organization's data and the number of paid licenses used in your organization, you can allow only owners to invite outside collaborators to organization repositories.

Organization owners can allow certain people to delete issues in repositories owned by your organization.

You can allow all organization members to create teams or limit team creation to organization owners.

You can customize the labels that are included in every new repository in your organization.

You can allow members of your organization to see a comment author's profile name in private repositories in the organization.

When you delete an organization, all repositories, forks of private repositories, wikis, issues, pull requests, and Project or Organization Pages are deleted as well.

It's not possible to convert an organization into a personal user account, but you can create a new user account and transfer the organization's repositories to it.

You can integrate Jira Cloud with your organization account to scan commits and pull requests, creating relevant metadata and hyperlinks in any mentioned Jira issues.