Skip to content

docs: correct access token guidance for account conversion #26233

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
akristen merged 1 commit into from
Sep 30, 2026
Merged

docs: correct access token guidance for account conversion #26233

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 7 additions & 4 deletions content/manuals/accounts/organization/setup/convert-account.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand All @@ -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.
Loading