Skip to content

Commit d79fd1f

Browse files
docs: refresh organization setup pages and clarify name versus namespace (#26239)
Deep validation, added important conceptual information, refresh tier 2 on setup docs for organizations --------- Co-authored-by: Cursor <cursoragent@cursor.com>
1 parent 5a23eba commit d79fd1f

6 files changed

Lines changed: 378 additions & 264 deletions

File tree

‎content/manuals/accounts/organization/_index.md‎

Lines changed: 5 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -35,26 +35,15 @@ aliases:
3535
- /accounts/organization/overview/
3636
---
3737

38-
Organization and company owners can manage members, control access, and enforce
39-
security across their Docker environments. You perform these tasks in Docker
40-
Home, which provides centralized observability, access management, and security
41-
controls.
42-
43-
A Docker organization is a collection of teams and repositories under
44-
centralized management. Organization administrators group members and
45-
assign repository access at scale.
46-
47-
As an organization or company owner, you can:
48-
49-
- Create and manage companies and organizations
50-
- Assign roles and permissions to members
51-
- Group members into teams to manage access by project or role
52-
- Set company-wide policies, including SCIM provisioning and security
53-
enforcement
38+
A Docker organization is a collection of teams and repositories that you
39+
manage in [Docker Home](https://app.docker.com/). Organization and company
40+
owners manage members, assign access, and enforce security.
5441

5542
For how individual, organization, and company accounts compare, see
5643
[Accounts](/manuals/accounts/_index.md). For individual accounts, see
5744
[Docker individual accounts](/manuals/accounts/individual/_index.md).
45+
To create, convert, or onboard an organization, see
46+
[Set up a Docker organization](/manuals/accounts/organization/setup/_index.md).
5847

5948
## Organization structure
6049

Lines changed: 46 additions & 25 deletions
Original file line numberDiff line numberDiff line change
@@ -1,22 +1,30 @@
11
---
2-
title: Set up your organization
2+
title: Set up a Docker organization
33
linkTitle: Setup
44
weight: 10
5-
description: Learn how to set up your Docker organization, including creating an organization, onboarding, and converting an account.
6-
keywords: set up organization, create organization, onboard, convert account, docker home
5+
description: >
6+
Create, convert, or onboard a Docker organization under one namespace and
7+
subscription.
8+
keywords:
9+
- Docker organization setup
10+
- create organization
11+
- onboard organization
12+
- convert Docker account
13+
- organization namespace
14+
- Docker Home
715
grid:
816
- title: Create your organization
9-
description: Create an organization to group teams and members and assign access.
17+
description: Choose a new namespace and subscription.
1018
icon: building-storefront
1119
link: /accounts/organization/setup/orgs/
20+
- title: Convert your account
21+
description: Keep an existing Docker ID as the organization namespace.
22+
icon: arrows-right-left
23+
link: /accounts/organization/setup/convert-account/
1224
- title: Onboard your organization
13-
description: Onboard and secure your Docker Team or Business organization.
25+
description: Invite members and configure sign-in.
1426
icon: magnifying-glass-plus
1527
link: /accounts/organization/setup/onboard/
16-
- title: Convert account
17-
description: Convert an existing Docker user account into an organization.
18-
icon: arrows-right-left
19-
link: /accounts/organization/setup/convert-account/
2028
- title: Manage your organization
2129
description: Add members, teams, licenses, and seats after setup.
2230
icon: user-group
@@ -29,26 +37,39 @@ aliases:
2937
- /admin/organization/setup/
3038
---
3139

32-
Before you manage members and access, set up your Docker organization. You can
33-
create an organization, onboard and secure it, or convert an existing user
34-
account into an organization.
40+
An organization groups members and teams under one namespace and one
41+
subscription. Anyone with a [Docker ID](/manuals/accounts/_index.md) can
42+
create an organization or convert an individual account into one.
3543

36-
## Setting up your organization
44+
You start by creating a new organization or converting an individual
45+
account. After creating or converting, you can onboard your organization.
3746

38-
You set up your organization from [Docker Home](https://app.docker.com) and
39-
must be assigned the
40-
[organization owner role](/manuals/security/roles-and-permissions/_index.md).
41-
Setting up an organization happens in broad phases:
47+
## Names versus namespaces
4248

43-
1. You can create a new organization, or convert an existing user account
44-
into one. Choose the option that fits how you already use Docker. You
45-
don't need both.
46-
1. After creating your organization, you must onboard it by inviting members,
47-
securing authentication, and enforcing sign-in. These steps build on each
48-
other, so follow them in order.
49+
When you create an organization, you set two values:
4950

50-
## Next steps
51+
- Organization namespace is the permanent, unique identifier for your
52+
organization. It becomes the first part of every image name you push, as
53+
in `namespace/image:tag`. You can't change it after you create the
54+
organization.
55+
- Docker IDs and organization namespaces must be unique.
56+
- If a Docker ID is `acme`, no organization can use `acme` as its
57+
namespace.
58+
- Organization name is the display name shown on your organization's
59+
Docker profile. You can change it at any time. See
60+
[Change organization information](/manuals/accounts/organization/manage/general-settings.md).
5161

52-
Explore the following sections to set up your organization.
62+
## Choose how to set up
63+
64+
The difference between creating and converting is what happens to your
65+
existing repositories.
66+
67+
- Create an organization: Choose a new namespace. Your existing
68+
repositories stay under your personal Docker ID.
69+
- Convert your account: Your Docker ID becomes the organization’s
70+
namespace. Your repositories and image names stay the same, so anyone
71+
pulling your images can keep using their existing image references.
72+
73+
## Next steps
5374

5475
{{< grid >}}
Lines changed: 107 additions & 60 deletions
Original file line numberDiff line numberDiff line change
@@ -1,85 +1,132 @@
11
---
2-
description: Convert your Docker Hub user account into an organization
2+
title: Convert a Docker account to an organization
33
linkTitle: Convert account
4-
title: Convert an account into an organization
5-
keywords: docker hub, hub, organization, convert account, migrate account
6-
weight: 40
4+
weight: 20
5+
description: >-
6+
Convert an individual Docker account into an organization. Keep the same
7+
Docker ID and repository namespace, then assign a new owner for shared
8+
access.
9+
keywords:
10+
- convert Docker account
11+
- convert account to organization
12+
- individual account to organization
13+
- organization owner
14+
- Docker organization
15+
- organization namespace
716
aliases:
817
- /admin/organization/setup/convert-account/
918
- /docker-hub/convert-account/
1019
- /admin/organization/convert-account/
20+
toc_max: 3
1121
---
1222

1323
{{< summary-bar feature_name="Admin orgs" >}}
1424

15-
Learn how to convert an existing user account into an organization. This is
16-
useful if you need multiple users to access your account and the repositories
17-
it’s connected to. Converting it to an organization gives you better control
18-
over permissions for these users through
19-
[teams](/manuals/accounts/organization/manage/manage-a-team.md) and
20-
[roles](/manuals/security/roles-and-permissions/_index.md).
21-
22-
When you convert a user account to an organization, the account is migrated to
23-
a Docker Team subscription by default.
25+
When you convert, your
26+
[Docker ID](/manuals/accounts/_index.md) becomes an organization instead of
27+
an individual account. The Docker ID stays the same, so repository
28+
namespaces and names stay the same. Convert an existing individual account
29+
into an organization when more than one person needs access to that
30+
account and its repositories. To choose a new namespace and keep your
31+
Docker ID as an individual account, see
32+
[Create a Docker organization](/manuals/accounts/organization/setup/orgs.md).
33+
34+
## Conversion
35+
36+
Converting an account into an organization does the following:
37+
38+
- The account gets a
39+
[Docker Team](/manuals/subscription-billing/plans/docker.md)
40+
subscription. If the individual account was on a paid plan, it keeps
41+
the same billing cycle.
42+
- Docker signs you out. Your email address is no longer on any Docker
43+
account. You can [sign up](https://hub.docker.com/signup) with it again
44+
or update an existing account to use it.
45+
- Repository collaborators are removed.
46+
[Invite them to your organization](/manuals/accounts/organization/manage/members.md),
47+
then add them to a
48+
[team](/manuals/accounts/organization/manage/manage-a-team.md)
49+
that has access to the repositories.
50+
- Existing automated builds appear as if the new owner set them up.
2451

2552
## Prerequisites
2653

27-
Before you convert a user account to an organization, ensure that you meet the following requirements:
54+
Before you convert an individual account to an organization:
2855

29-
- The user account that you want to convert must not be a member of a company or any teams or organizations. You must remove the account from all teams, organizations, or the company.
56+
- The individual account must have a verified email address.
57+
- You need a separate Docker ID to [assign as organization owner](#choose-an-organization-owner).
58+
- The individual account must not belong to an organization, a team, or a
59+
company. If it does, you must
60+
[leave the organization](#leave-an-existing-organization) before you convert.
3061

31-
To do this:
32-
1. Navigate to **My Hub** and then select the organization you need to leave.
33-
1. Find your username in the **Members** tab.
34-
1. Select the **More options** menu and then select **Leave organization**.
62+
> [!TIP]
63+
>
64+
> After you convert an account, personal access tokens from that account
65+
> stop working. Sign in as the new owner and create an
66+
> [organization access token (OAT)](/manuals/security/access-tokens/organization-access-tokens.md)
67+
> for the converted organization.
3568
36-
If the user account is the sole owner of any organization or company, assign another user the owner role and then remove yourself from the organization or company.
69+
### Choose an organization owner
3770

38-
- You must have a separate Docker ID ready to assign as the owner of the organization during conversion.
71+
To convert, you must name an owner. That owner has full administrative access
72+
to configure and manage the organization. You can add more owners after
73+
conversion. Each owner signs in to a separate individual account, then
74+
selects the organization in Docker Home.
3975

40-
If you want to convert your user account into an organization account and you don't have any other user accounts, you need to create a new user account to assign it as the owner of the new organization. With the owner role assigned, this user account has full administrative access to configure and manage the organization. You can assign more users the owner role after the conversion.
76+
To name someone else as the owner, enter that person's Docker ID during
77+
conversion. If you still need access after conversion, you must sign up
78+
again so the new owner can invite you to the organization.
4179

42-
## What happens when you convert your account
80+
If you want to remain the sole owner without assigning another owner, you
81+
must create a second individual account with a different email address.
82+
Use your new account's Docker ID.
4383

44-
The following happens when you convert your account into
45-
an organization:
84+
- For example, if the account you are converting uses `alex@example.com`,
85+
create the owner account with `alex.admin@example.com`.
86+
- After conversion, `alex@example.com` is no longer on any Docker account.
4687

47-
- This process removes the email address for the account. Notifications are
48-
instead sent to organization owners. You'll be able to reuse the
49-
removed email address for another account after converting.
50-
- The current subscription will automatically cancel and your new subscription
51-
will start.
52-
- Repository namespaces and names won't change, but converting your account
53-
removes any repository collaborators. Once you convert the account, you'll need
54-
to add repository collaborators as team members.
55-
- Existing automated builds appear as if they were set up by the first owner
56-
added to the organization.
57-
- The user account that you add as the first owner will have full
58-
administrative access to configure and manage the organization.
88+
You can update the `alex.admin@example.com` email back to
89+
`alex@example.com` after conversion. See
90+
[Update email address](/manuals/accounts/individual/manage-account.md#update-email-address).
5991

60-
## Convert an account into an organization
92+
### Leave an existing organization
6193

62-
> [!IMPORTANT]
63-
>
64-
> Converting an account into an organization is permanent. Back up any data
65-
> or settings you want to retain.
94+
Use this procedure when the individual account is already a member of an
95+
organization, a team, or a company. The account can be converted after it
96+
has left each of them. If it has no memberships, skip this section and
97+
[convert the account](#convert-to-an-organization).
6698

67-
1. Sign in to [Docker Home](https://app.docker.com/).
68-
1. Select your avatar in the top-right corner to open the drop-down.
69-
1. From **Account settings**, select **Convert**.
70-
1. Review the warning displayed about converting a user account. This action
71-
cannot be undone and has considerable implications for your assets and the
72-
account.
73-
1. Enter a **Username of new owner** to set an organization owner. The new
74-
Docker ID you specify becomes the organization’s owner. You cannot use the
75-
same Docker ID as the account you are trying to convert. The Docker ID is
76-
case-sensitive.
77-
1. Select **Confirm**. The new owner receives a notification email. Use that
78-
owner account to sign in and manage the new organization.
99+
If the account is the only owner of an organization or company, assign
100+
the owner role to another member first. Leave after that member can
101+
administer the organization or company.
79102

80-
> [!TIP]
81-
>
82-
> After you convert an account, existing personal access tokens from that
83-
> account no longer work. Sign in as the new owner and create an
84-
> [organization access token (OAT)](/manuals/security/access-tokens/organization-access-tokens.md)
85-
> for the converted organization.
103+
To leave an organization and its teams:
104+
105+
1. Sign in to [Docker Home](https://app.docker.com/) and select the
106+
organization.
107+
1. Select **Members** and find your username.
108+
1. Select the **Actions** menu, then **Leave organization**.
109+
110+
## Convert to an organization
111+
112+
Converting an account into an organization is permanent. Back up any data
113+
or settings you want to keep.
114+
115+
1. Sign in to [Docker Home](https://app.docker.com/).
116+
1. Select your avatar in the top-right corner.
117+
1. Select **Account settings**, then **Convert**.
118+
1. Review the warning. You can't undo this action.
119+
1. Enter the **Username of new owner**.
120+
Enter a Docker ID, not an email address. Use 4 to 30 letters and
121+
digits. The Docker ID must belong to a different account from the one
122+
you are converting. That account must be active and have a verified
123+
email address.
124+
1. Select **Confirm**. For an account on a Pro plan, the button is
125+
**Confirm and purchase**.
126+
The new owner receives a notification email. Sign in with that account
127+
to manage the organization.
128+
129+
## Next steps
130+
131+
- [Onboard your organization](/manuals/accounts/organization/setup/onboard.md)
132+
- [Create an organization access token](/manuals/security/access-tokens/organization-access-tokens.md)

0 commit comments

Comments
 (0)