Skip to content

Latest commit

 

History

History
82 lines (69 loc) · 7.07 KB

converting-a-user-into-an-organization.md

File metadata and controls

82 lines (69 loc) · 7.07 KB
Raw
title redirect_from intro versions topics shortTitle
Converting a user into an organization
/articles/what-is-the-difference-between-create-new-organization-and-turn-account-into-an-organization
/articles/explaining-the-account-transformation-warning
/articles/converting-a-user-into-an-organization
/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization
/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization
/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization
/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/converting-a-user-into-an-organization
You can convert your personal account into an organization. This allows more granular permissions for repositories that belong to the organization.
fpt ghes ghec
*
*
*
Accounts
User into an organization

Warning

Before converting a user into an organization, keep these points in mind.

  • You will no longer be able to sign into the converted personal account.
  • You will no longer be able to create or modify gists owned by the converted personal account.
  • An organization cannot be converted back to a user.
  • The SSH keys, OAuth tokens, job profile, reactions, and associated user information, will not be transferred to the organization. This is only true for the personal account that's being converted, not any of the personal account's collaborators.
  • Any {% data variables.product.prodname_github_apps %} installed on the converted personal account will be uninstalled.
  • Any commits made with the converted personal account will no longer be linked to that account. The commits themselves will remain intact.
  • Any existing comments made by the converted personal account will no longer be linked to that account. The comments themselves will remain intact, but will be associated with the ghost user.
  • Any forks of private repositories made with the converted personal account will be deleted.
  • Since organizations cannot star repositories, you will no longer have access to your original list of starred repositories.
  • You will no longer have access to the list of users you were following from your user account.
  • Any followers of your user account will not automatically follow the new organization. {% ifversion projects-v2 %}> * Any existing collaborators on your projects will still have access to those projects in the new organization.{% endif %}
  • {% data variables.product.prodname_actions %} is not automatically enabled on the account after converting it to an organization, and will have to be re-enabled. To re-enable {% data variables.product.prodname_actions %}, create a new workflow file in the .github/workflows directory of your repository.

Prerequisites

The personal account you want to convert cannot be a member of any organizations. If the personal account you want to convert is a member of an organization, you must leave the organization before you can convert the account.

{% ifversion ghes %} You may not be able to convert a personal account into an organization, if an enterprise owner has set a policy at the enterprise level. See, "AUTOTITLE." {% endif %}

Keep your personal account and create a new organization manually

If you want your organization to have the same name that you are currently using for your personal account, or if you want to keep your personal account's information intact, then you must create a new organization and transfer your repositories to it instead of converting your personal account into an organization.

  1. To retain your current personal account name for your personal use, change the name of your personal account to something new and wonderful.
  2. Create a new organization with the original name of your personal account.
  3. Transfer your repositories to your new organization account.

Convert your personal account into an organization automatically

You can also convert your personal account directly into an organization. Converting your account:

  • Preserves the repositories as they are without the need to transfer them to another account manually
  • Automatically invites collaborators to teams with permissions equivalent to what they had before {%- ifversion fpt or ghec %}
  • For personal accounts on {% data variables.product.prodname_pro %}, automatically transitions billing to the paid {% data variables.product.prodname_team %} without the need to re-enter payment information, adjust your billing cycle, or double pay at any time {%- endif %}

When you convert a personal account into an organization, we'll add collaborators on repositories that belong to the account to the new organization as outside collaborators. You can then invite outside collaborators to become members of your new organization if you wish. For more information, see "AUTOTITLE."

  1. Create a new personal account, which you'll use to sign into GitHub and access the organization and your repositories after you convert.
  2. Leave any organizations the personal account you're converting has joined. {% data reusables.user-settings.access_settings %} {% data reusables.user-settings.organizations %}
  3. In the "Transform account" section, click Turn USERNAME into an organization.
  4. Review the warning, then click Turn USERNAME into an organization.
  5. Under "Choose an organization owner", type either the secondary personal account you created in the previous section, or another user you trust, to manage the organization.
  6. Choose your new organization's subscription and enter your billing information, if prompted.
  7. Click Create Organization.
  8. Sign in to the new personal account you created earlier, then use the context switcher to access your new organization.

Further reading