From 4e682c21a2b9c41cafa92529d0c4dee4d7338fc3 Mon Sep 17 00:00:00 2001 From: Alexa Date: Wed, 30 Sep 2026 14:14:31 -0500 Subject: [PATCH] docs: correct access token guidance for account conversion Remove the inaccurate PAT transfer note and tip owners to create an OAT after converting an account. Co-authored-by: Cursor --- .../accounts/organization/setup/convert-account.md | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/content/manuals/accounts/organization/setup/convert-account.md b/content/manuals/accounts/organization/setup/convert-account.md index a17ba032cdcd..a580449f1c18 100644 --- a/content/manuals/accounts/organization/setup/convert-account.md +++ b/content/manuals/accounts/organization/setup/convert-account.md @@ -56,10 +56,6 @@ an organization: added to the organization. - The user account that you add as the first owner will have full administrative access to configure and manage the organization. -- To transfer a user's personal access tokens (PATs) to your converted - organization, 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. ## Convert an account into an organization @@ -80,3 +76,10 @@ an organization: case-sensitive. 1. Select **Confirm**. The new owner receives a notification email. Use that owner account to sign in and manage the new organization. + +> [!TIP] +> +> After you convert an account, existing personal access tokens from that +> account no longer work. Sign in as the new owner and create an +> [organization access token (OAT)](/manuals/security/access-tokens/organization-access-tokens.md) +> for the converted organization.