Skip to content

Commit 07ca373

Browse files
sarahsanders-dockerduffuniversecrazy-maxaevesdocker
authored
publish updates from main (#22470)
Automated pull request for publishing docs updates. --------- Co-authored-by: Andrey Sobolev <[email protected]> Co-authored-by: CrazyMax <[email protected]> Co-authored-by: Sarah Sanders <[email protected]> Co-authored-by: Allie Sadler <[email protected]>
2 parents 030bb34 + 0c89cc7 commit 07ca373

File tree

2 files changed

+8
-2
lines changed

2 files changed

+8
-2
lines changed

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

+7-1
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

content/manuals/build/building/best-practices.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -147,7 +147,7 @@ Limiting each container to one process is a good rule of thumb, but it's not a
147147
hard and fast rule. For example, not only can containers be
148148
[spawned with an init process](/manuals/engine/containers/multi-service_container.md),
149149
some programs might spawn additional processes of their own accord. For
150-
instance, [Celery](https://docs.celeryproject.org/) can spawn multiple worker
150+
instance, [Celery](https://docs.celeryq.dev/) can spawn multiple worker
151151
processes, and [Apache](https://httpd.apache.org/) can create one process per
152152
request.
153153

0 commit comments

Comments
 (0)