Skip to content

Commit fbdf549

Browse files
Remove outdated limitation and add suggestion for OATs
1 parent 23589f1 commit fbdf549

File tree

1 file changed

+7
-1
lines changed

1 file changed

+7
-1
lines changed

content/manuals/admin/organization/convert-account.md

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -48,7 +48,13 @@ Consider the following effects of converting your account:
4848

4949
- The user account that you add as the first owner will have full administrative access to configure and manage the organization.
5050

51-
- Converting a user account to an organization will delete all of the user's personal access tokens. See [Create an access token](/manuals/security/for-developers/access-tokens.md#create-an-access-token) for steps on creating personal access tokens after converting the user account.
51+
- To transfer a user's personal access tokens (PATs) to your converted organization,
52+
you must designate the user as an organization owner. This will ensure any PATs associated with the user's account are transferred to the organization owner.
53+
54+
> [!TIP]
55+
>
56+
> To avoid potentially disrupting service of personal access tokens when converting an account or changing ownership, it is recommended to use [Organization access tokens](/manuals/security/for-admins/access-tokens.md). Organization access tokens are
57+
associated with an organization, not a single user account.
5258

5359
## Convert an account into an organization
5460

0 commit comments

Comments
 (0)