From d79fd1f436e9bb8542fedf004f93f8e4893366cd Mon Sep 17 00:00:00 2001 From: Alexa Kristensen <81787716+akristen@users.noreply.github.com> Date: Fri, 2 Oct 2026 07:43:38 -0500 Subject: [PATCH] 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 --- .../manuals/accounts/organization/_index.md | 21 +- .../accounts/organization/setup/_index.md | 73 +++--- .../organization/setup/convert-account.md | 177 +++++++++------ .../accounts/organization/setup/onboard.md | 212 +++++++++--------- .../accounts/organization/setup/orgs.md | 107 +++++---- content/manuals/faqs/accounts.md | 60 ++++- 6 files changed, 382 insertions(+), 268 deletions(-) diff --git a/content/manuals/accounts/organization/_index.md b/content/manuals/accounts/organization/_index.md index f270382e28..2924a9f615 100644 --- a/content/manuals/accounts/organization/_index.md +++ b/content/manuals/accounts/organization/_index.md @@ -35,26 +35,15 @@ aliases: - /accounts/organization/overview/ --- -Organization and company owners can manage members, control access, and enforce -security across their Docker environments. You perform these tasks in Docker -Home, which provides centralized observability, access management, and security -controls. - -A Docker organization is a collection of teams and repositories under -centralized management. Organization administrators group members and -assign repository access at scale. - -As an organization or company owner, you can: - -- Create and manage companies and organizations -- Assign roles and permissions to members -- Group members into teams to manage access by project or role -- Set company-wide policies, including SCIM provisioning and security - enforcement +A Docker organization is a collection of teams and repositories that you +manage in [Docker Home](https://app.docker.com/). Organization and company +owners manage members, assign access, and enforce security. For how individual, organization, and company accounts compare, see [Accounts](/manuals/accounts/_index.md). For individual accounts, see [Docker individual accounts](/manuals/accounts/individual/_index.md). +To create, convert, or onboard an organization, see +[Set up a Docker organization](/manuals/accounts/organization/setup/_index.md). ## Organization structure diff --git a/content/manuals/accounts/organization/setup/_index.md b/content/manuals/accounts/organization/setup/_index.md index 87c233886d..4d94e13294 100644 --- a/content/manuals/accounts/organization/setup/_index.md +++ b/content/manuals/accounts/organization/setup/_index.md @@ -1,22 +1,30 @@ --- -title: Set up your organization +title: Set up a Docker organization linkTitle: Setup weight: 10 -description: Learn how to set up your Docker organization, including creating an organization, onboarding, and converting an account. -keywords: set up organization, create organization, onboard, convert account, docker home +description: > + Create, convert, or onboard a Docker organization under one namespace and + subscription. +keywords: + - Docker organization setup + - create organization + - onboard organization + - convert Docker account + - organization namespace + - Docker Home grid: - title: Create your organization - description: Create an organization to group teams and members and assign access. + description: Choose a new namespace and subscription. icon: building-storefront link: /accounts/organization/setup/orgs/ - - title: Onboard your organization - description: Onboard and secure your Docker Team or Business organization. - icon: magnifying-glass-plus - link: /accounts/organization/setup/onboard/ - - title: Convert account - description: Convert an existing Docker user account into an organization. + - title: Convert your account + description: Keep an existing Docker ID as the organization namespace. icon: arrows-right-left link: /accounts/organization/setup/convert-account/ + - title: Onboard your organization + description: Invite members and configure sign-in. + icon: magnifying-glass-plus + link: /accounts/organization/setup/onboard/ - title: Manage your organization description: Add members, teams, licenses, and seats after setup. icon: user-group @@ -29,26 +37,39 @@ aliases: - /admin/organization/setup/ --- -Before you manage members and access, set up your Docker organization. You can -create an organization, onboard and secure it, or convert an existing user -account into an organization. +An organization groups members and teams under one namespace and one +subscription. Anyone with a [Docker ID](/manuals/accounts/_index.md) can +create an organization or convert an individual account into one. -## Setting up your organization +You start by creating a new organization or converting an individual +account. After creating or converting, you can onboard your organization. -You set up your organization from [Docker Home](https://app.docker.com) and -must be assigned the -[organization owner role](/manuals/security/roles-and-permissions/_index.md). -Setting up an organization happens in broad phases: +## Names versus namespaces -1. You can create a new organization, or convert an existing user account - into one. Choose the option that fits how you already use Docker. You - don't need both. -1. After creating your organization, you must onboard it by inviting members, - securing authentication, and enforcing sign-in. These steps build on each - other, so follow them in order. +When you create an organization, you set two values: + +- Organization namespace is the permanent, unique identifier for your + organization. It becomes the first part of every image name you push, as + in `namespace/image:tag`. You can't change it after you create the + organization. + - Docker IDs and organization namespaces must be unique. + - If a Docker ID is `acme`, no organization can use `acme` as its + namespace. +- Organization name is the display name shown on your organization's + Docker profile. You can change it at any time. See + [Change organization information](/manuals/accounts/organization/manage/general-settings.md). + +## Choose how to set up + +The difference between creating and converting is what happens to your +existing repositories. + +- Create an organization: Choose a new namespace. Your existing + repositories stay under your personal Docker ID. +- Convert your account: Your Docker ID becomes the organization’s + namespace. Your repositories and image names stay the same, so anyone + pulling your images can keep using their existing image references. ## Next steps -Explore the following sections to set up your organization. - {{< grid >}} diff --git a/content/manuals/accounts/organization/setup/convert-account.md b/content/manuals/accounts/organization/setup/convert-account.md index a580449f1c..f067f80362 100644 --- a/content/manuals/accounts/organization/setup/convert-account.md +++ b/content/manuals/accounts/organization/setup/convert-account.md @@ -1,85 +1,132 @@ --- -description: Convert your Docker Hub user account into an organization +title: Convert a Docker account to an organization linkTitle: Convert account -title: Convert an account into an organization -keywords: docker hub, hub, organization, convert account, migrate account -weight: 40 +weight: 20 +description: >- + Convert an individual Docker account into an organization. Keep the same + Docker ID and repository namespace, then assign a new owner for shared + access. +keywords: + - convert Docker account + - convert account to organization + - individual account to organization + - organization owner + - Docker organization + - organization namespace aliases: - /admin/organization/setup/convert-account/ - /docker-hub/convert-account/ - /admin/organization/convert-account/ +toc_max: 3 --- {{< summary-bar feature_name="Admin orgs" >}} -Learn how to convert an existing user account into an organization. This is -useful if you need multiple users to access your account and the repositories -it’s connected to. Converting it to an organization gives you better control -over permissions for these users through -[teams](/manuals/accounts/organization/manage/manage-a-team.md) and -[roles](/manuals/security/roles-and-permissions/_index.md). +When you convert, your +[Docker ID](/manuals/accounts/_index.md) becomes an organization instead of +an individual account. The Docker ID stays the same, so repository +namespaces and names stay the same. Convert an existing individual account +into an organization when more than one person needs access to that +account and its repositories. To choose a new namespace and keep your +Docker ID as an individual account, see +[Create a Docker organization](/manuals/accounts/organization/setup/orgs.md). -When you convert a user account to an organization, the account is migrated to -a Docker Team subscription by default. +## Conversion + +Converting an account into an organization does the following: + +- The account gets a + [Docker Team](/manuals/subscription-billing/plans/docker.md) + subscription. If the individual account was on a paid plan, it keeps + the same billing cycle. +- Docker signs you out. Your email address is no longer on any Docker + account. You can [sign up](https://hub.docker.com/signup) with it again + or update an existing account to use it. +- Repository collaborators are removed. + [Invite them to your organization](/manuals/accounts/organization/manage/members.md), + then add them to a + [team](/manuals/accounts/organization/manage/manage-a-team.md) + that has access to the repositories. +- Existing automated builds appear as if the new owner set them up. ## Prerequisites -Before you convert a user account to an organization, ensure that you meet the following requirements: +Before you convert an individual account to an organization: -- 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. - - To do this: - 1. Navigate to **My Hub** and then select the organization you need to leave. - 1. Find your username in the **Members** tab. - 1. Select the **More options** menu and then select **Leave organization**. - - 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. - -- You must have a separate Docker ID ready to assign as the owner of the organization during conversion. - - 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. - -## What happens when you convert your account - -The following happens when you convert your account into -an organization: - -- This process removes the email address for the account. Notifications are - instead sent to organization owners. You'll be able to reuse the - removed email address for another account after converting. -- The current subscription will automatically cancel and your new subscription - will start. -- Repository namespaces and names won't change, but converting your account - removes any repository collaborators. Once you convert the account, you'll need - to add repository collaborators as team members. -- Existing automated builds appear as if they were set up by the first owner - 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. - -## Convert an account into an organization - -> [!IMPORTANT] -> -> Converting an account into an organization is permanent. Back up any data -> or settings you want to retain. - -1. Sign in to [Docker Home](https://app.docker.com/). -1. Select your avatar in the top-right corner to open the drop-down. -1. From **Account settings**, select **Convert**. -1. Review the warning displayed about converting a user account. This action - cannot be undone and has considerable implications for your assets and the - account. -1. Enter a **Username of new owner** to set an organization owner. The new - Docker ID you specify becomes the organization’s owner. You cannot use the - same Docker ID as the account you are trying to convert. The Docker ID is - case-sensitive. -1. Select **Confirm**. The new owner receives a notification email. Use that - owner account to sign in and manage the new organization. +- The individual account must have a verified email address. +- You need a separate Docker ID to [assign as organization owner](#choose-an-organization-owner). +- The individual account must not belong to an organization, a team, or a + company. If it does, you must + [leave the organization](#leave-an-existing-organization) before you convert. > [!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 +> After you convert an account, personal access tokens from that account +> stop working. 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. + +### Choose an organization owner + +To convert, you must name an owner. That owner has full administrative access +to configure and manage the organization. You can add more owners after +conversion. Each owner signs in to a separate individual account, then +selects the organization in Docker Home. + +To name someone else as the owner, enter that person's Docker ID during +conversion. If you still need access after conversion, you must sign up +again so the new owner can invite you to the organization. + +If you want to remain the sole owner without assigning another owner, you +must create a second individual account with a different email address. +Use your new account's Docker ID. + +- For example, if the account you are converting uses `alex@example.com`, + create the owner account with `alex.admin@example.com`. +- After conversion, `alex@example.com` is no longer on any Docker account. + +You can update the `alex.admin@example.com` email back to +`alex@example.com` after conversion. See +[Update email address](/manuals/accounts/individual/manage-account.md#update-email-address). + +### Leave an existing organization + +Use this procedure when the individual account is already a member of an +organization, a team, or a company. The account can be converted after it +has left each of them. If it has no memberships, skip this section and +[convert the account](#convert-to-an-organization). + +If the account is the only owner of an organization or company, assign +the owner role to another member first. Leave after that member can +administer the organization or company. + +To leave an organization and its teams: + +1. Sign in to [Docker Home](https://app.docker.com/) and select the + organization. +1. Select **Members** and find your username. +1. Select the **Actions** menu, then **Leave organization**. + +## Convert to an organization + +Converting an account into an organization is permanent. Back up any data +or settings you want to keep. + +1. Sign in to [Docker Home](https://app.docker.com/). +1. Select your avatar in the top-right corner. +1. Select **Account settings**, then **Convert**. +1. Review the warning. You can't undo this action. +1. Enter the **Username of new owner**. + Enter a Docker ID, not an email address. Use 4 to 30 letters and + digits. The Docker ID must belong to a different account from the one + you are converting. That account must be active and have a verified + email address. +1. Select **Confirm**. For an account on a Pro plan, the button is + **Confirm and purchase**. + The new owner receives a notification email. Sign in with that account + to manage the organization. + +## Next steps + +- [Onboard your organization](/manuals/accounts/organization/setup/onboard.md) +- [Create an organization access token](/manuals/security/access-tokens/organization-access-tokens.md) diff --git a/content/manuals/accounts/organization/setup/onboard.md b/content/manuals/accounts/organization/setup/onboard.md index cfaea1fb24..950c246a72 100644 --- a/content/manuals/accounts/organization/setup/onboard.md +++ b/content/manuals/accounts/organization/setup/onboard.md @@ -1,11 +1,20 @@ --- -title: Onboard your organization +title: Onboard a Docker organization linkTitle: Onboard -weight: 20 -description: Get started onboarding your Docker Team or Business organization. -keywords: business, team, organizations, get started, onboarding, Docker Home, organization management, -toc_min: 1 -toc_max: 3 +weight: 30 +description: > + Invite members, configure SSO and SCIM, and enforce Docker Desktop + sign-in for a Team or Business organization. +keywords: + - onboard Docker organization + - guided setup + - Docker Team + - Docker Business + - enforce sign-in + - SSO + - SCIM + - Docker Desktop +toc_max: 2 aliases: - /admin/organization/setup/onboard/ - /docker-hub/onboard/ @@ -16,145 +25,133 @@ aliases: {{< summary-bar feature_name="Admin orgs" >}} -Learn how to onboard your organization. - Onboarding your organization includes: -- Identifying users to help you allocate your subscription seats -- Invite members and owners to your organization -- Secure authentication and authorization for your organization -- Enforce sign-in for Docker Desktop to ensure security best practices +- Identifying users so you can allocate subscription seats +- Inviting members and owners +- Securing authentication and authorization +- Enforcing sign-in for Docker Desktop -These actions help administrators gain visibility into user activity and -enforce security settings. Organization members also receive increased pull -limits and other benefits when they are signed in. +These actions give administrators visibility into user activity and a way +to enforce security settings. Organization members also receive higher +pull limits and other benefits when they are signed in. ## Prerequisites -Before you start onboarding your organization, ensure you: +Before you onboard your organization, you need a Docker Team or Business +subscription. For details, see +[Docker subscriptions and features](https://www.docker.com/pricing?ref=Docs&refAction=DocsAdminOnboard). +When you buy a self-serve subscription, the on-screen instructions guide +you through creating an organization. -- Have a Docker Team or Business subscription. For more details, see - [Docker subscriptions and features](https://www.docker.com/pricing?ref=Docs&refAction=DocsAdminOnboard). +If you bought a subscription through Docker Sales and you haven't created +an organization yet, see +[Create an organization](/manuals/accounts/organization/setup/orgs.md). - > [!NOTE] - > - > When purchasing a self-serve subscription, the on-screen instructions - > guide you through creating an organization. If you have purchased a - > subscription through Docker Sales and you have not yet created an - > organization, see [Create an organization](/manuals/accounts/organization/setup/orgs.md). +## Guided onboarding -- Familiarize yourself with Docker concepts and terminology in - the [administration overview](../../_index.md). +You can use a guided setup for the first onboarding tasks: -## Onboard with guided setup +1. Sign in to [Docker Home](https://app.docker.com). +1. Select **Guided setup** at the bottom of the left sidebar. -Docker Home has a guided setup to help you -onboard your organization. The guided setup's steps consist of basic onboarding -tasks. If you want to onboard outside of the guided setup, -see [Recommended onboarding steps](/manuals/accounts/organization/setup/onboard.md#recommended-onboarding-steps). - -To onboard using the guided setup, -navigate to [Docker Home](https://app.docker.com) and -select **Guided setup** in the left-hand navigation. - -The guided setup walks you through the following onboarding steps: +Guided setup walks through these steps: - **Invite your team**: Invite owners and members. -- **Manage user access**: Add and verify a domain, manage users with SSO, and - enforce Docker Desktop sign-in. -- **Docker Desktop security**: Configure image access management, registry - access management, and settings management. +- **Manage user access**: Claim your company's domain, manage members + with SSO, and enforce Docker Desktop sign-in. +- **Docker Desktop security**: Configure Image Access Management, + Registry Access Management, and Settings Management. -## Recommended onboarding steps +## Manual onboarding ### Step one: Identify your Docker users -Identifying your users helps you allocate seats efficiently and ensures they +Identifying your users helps you allocate seats and makes sure they receive your Docker subscription benefits. 1. Identify the Docker users in your organization. - - If your organization uses device management software, like MDM or Jamf, - you can use the device management software to help identify Docker users. - See your device management software's documentation for details. You can - identify Docker users by checking if Docker Desktop is installed at the - following location on each user's machine: + - If your organization uses device management software, such as MDM + or Jamf, use it to find machines with Docker Desktop installed: - Mac: `/Applications/Docker.app` - - Windows: `C:\Program Files\Docker\Docker`(all-user installation) or `%LOCALAPPDATA%\Programs\DockerDesktop` (per-user installation (Beta)) + - Windows: `C:\Program Files\Docker\Docker` (all-users + installation) or `%LOCALAPPDATA%\Programs\DockerDesktop` + (per-user installation) - Linux: `/opt/docker-desktop` - - If your organization doesn't use device management software or your - users haven't installed Docker Desktop yet, you can survey your users to - identify who is using Docker Desktop. -1. Ask users to update their Docker account's email address to one associated - with your organization's domain, or create a new account with that email. - - To update an account's email address, instruct your users to sign in - to [Docker Hub](https://hub.docker.com), and update the email address to - their email address in your organization's domain. - - To create a new account, instruct your users to - [sign up](https://hub.docker.com/signup) using their email address associated - with your organization's domain. Ensure your users verify their email address. -1. Identify Docker accounts associated with your organization's domain: - - Ask your Docker sales representative or - contact sales to get a list - of Docker accounts that use an email address in your organization's domain. + - If your organization doesn't use device management software, or + users haven't installed Docker Desktop yet, ask them who uses + Docker Desktop. +1. Ask users to update their Docker account email address to one in your + organization's domain, or to create an account with that email. + - To update an email address, see + [Update email address](/manuals/accounts/individual/manage-account.md#update-email-address). + - To create an account, users + [sign up](https://hub.docker.com/signup) with an email address in + your organization's domain and verify that address. +1. Identify Docker accounts that already use your organization's domain: + - Ask your Docker sales representative, or + contact sales, + for a list of Docker accounts that use an email address in your + domain. ### Step two: Invite owners -Owners can help you onboard and manage your organization. +When you create an organization, you are the only owner. Adding more +owners is optional, but additional owners can help you onboard and manage +your organization. -When you create an organization, you are the only owner. It is optional to -add additional owners. - -To add an owner, invite a user and assign them the owner role. For more -details, see [Invite members](/manuals/accounts/organization/manage/members.md) and +To add an owner, invite a user and assign the owner role. For details, +see [Invite members](/manuals/accounts/organization/manage/members.md) +and [Roles and permissions](/manuals/security/roles-and-permissions/_index.md). ### Step three: Invite members -When you add users to your organization, you gain visibility into their -activity and you can enforce security settings. Your members also -receive increased pull limits and other organization wide benefits when -they are signed in. +When you add users to your organization, you can see their activity and +enforce security settings. Members also receive higher pull limits and +other organization-wide benefits when they are signed in. -To add a member, invite a user and assign them the member role. -For more details, see [Invite members](/manuals/accounts/organization/manage/members.md) and +To add a member, invite a user and assign the member role. For details, +see [Invite members](/manuals/accounts/organization/manage/members.md) +and [Roles and permissions](/manuals/security/roles-and-permissions/_index.md). ### Step four: Manage user access with SSO and SCIM -Configuring SSO and SCIM is optional and only available to Docker Business -subscribers. To upgrade a Docker Team subscription to a Docker Business -subscription, see [Upgrade a plan](/manuals/subscription-billing/manage/plans.md#upgrade-plans). +SSO and SCIM are optional and available to Docker Business subscribers. +To upgrade a Docker Team subscription to Docker Business, see +[Upgrade a plan](/manuals/subscription-billing/manage/plans.md#upgrade-plans). -Use your identity provider (IdP) to manage members and provision them to Docker -automatically via SSO and SCIM. See the following for more details: +Use your identity provider (IdP) to manage members and provision them to +Docker through SSO and SCIM: - [Configure SSO](/manuals/security/authentication/single-sign-on/connect.md) - to authenticate and add members when they sign in to Docker through your + to authenticate members and add them when they sign in through your identity provider. - Optional. - [Enforce SSO](/manuals/security/authentication/single-sign-on/connect.md) to - ensure that when users sign in to Docker, they must use SSO. + [Enforce SSO](/manuals/security/authentication/single-sign-on/connect.md) + so users must use SSO when they sign in to Docker. > [!NOTE] > - > Enforcing single sign-on (SSO) and enforcing Docker Desktop sign in - > are different features. For more details, see + > Enforcing single sign-on (SSO) and enforcing Docker Desktop sign-in + > are different features. For details, see > [Enforcing sign-in versus enforcing single sign-on (SSO)](/manuals/desktop/enterprise/enforce-sign-in/_index.md#enforcing-sign-in-versus-enforcing-single-sign-on-sso). - [Configure SCIM](/manuals/security/provisioning/scim/_index.md) to - automatically provision, add, and de-provision members to Docker through - your identity provider. + provision, add, and deprovision members through your identity + provider. ### Step five: Enforce sign-in for Docker Desktop -By default, members of your organization can use Docker Desktop without signing -in. When users don’t sign in as a member of your organization, they don’t -receive the -[benefits of your organization’s subscription](https://www.docker.com/pricing?ref=Docs&refAction=DocsAdminOnboard) -and they can circumvent [Docker’s security features](/manuals/desktop/enterprise/hardened-desktop/_index.md). +By default, members of your organization can use Docker Desktop without +signing in. When users don't sign in as a member of your organization, +they don't receive the +[benefits of your organization's subscription](https://www.docker.com/pricing?ref=Docs&refAction=DocsAdminOnboard) +and they can bypass +[Docker's security features](/manuals/desktop/enterprise/hardened-desktop/_index.md). -There are multiple ways you can enforce sign-in, depending on your organization's -Docker configuration: +You can enforce sign-in in more than one way: - [Registry key method (Windows only)](/manuals/desktop/enterprise/enforce-sign-in/methods.md#registry-key-method-windows-only) - [`.plist` method (Mac only)](/manuals/desktop/enterprise/enforce-sign-in/methods.md#plist-method-mac-only) @@ -162,18 +159,21 @@ Docker configuration: ### Step six: Manage Docker Desktop security -Docker offers the following security features to manage your organization's -security posture: +Use these features to manage your organization's security posture: -- [Image Access Management](/manuals/desktop/enterprise/hardened-desktop/image-access-management.md): Control which types of images your developers can pull from Docker Hub. -- [Registry Access Management](/manuals/desktop/enterprise/hardened-desktop/registry-access-management.md): Define which registries your developers can access. -- [Settings management](/manuals/desktop/enterprise/hardened-desktop/settings-management.md): Set and control Docker Desktop settings for your users. +- [Image Access Management](/manuals/desktop/enterprise/hardened-desktop/image-access-management.md): + Control which types of images developers can pull from Docker Hub. +- [Registry Access Management](/manuals/desktop/enterprise/hardened-desktop/registry-access-management.md): + Define which registries developers can access. +- [Settings Management](/manuals/desktop/enterprise/hardened-desktop/settings-management.md): + Set and control Docker Desktop settings for your users. ## Next steps -- [Manage Docker products](../manage/manage-products.md) to configure access and view usage. -- Configure [Hardened Docker Desktop](/manuals/desktop/enterprise/hardened-desktop/_index.md) to improve your organization’s security posture for containerized development. -- [Manage your domains](/manuals/security/provisioning/domain-management.md) to ensure that all Docker users in your domain are part of your organization. - -Your Docker subscription provides many more additional features. To learn more, -see [Docker subscriptions and features](https://www.docker.com/pricing?ref=Docs&refAction=DocsAdminOnboard). +- [Manage Docker products](../manage/manage-products.md) to configure + access and view usage. +- Configure + [Hardened Docker Desktop](/manuals/desktop/enterprise/hardened-desktop/_index.md) + to tighten security for containerized development. +- [Manage your domains](/manuals/security/provisioning/domain-management.md) + so Docker users in your domain are part of your organization. diff --git a/content/manuals/accounts/organization/setup/orgs.md b/content/manuals/accounts/organization/setup/orgs.md index 425aa81aff..6efa3c2bd3 100644 --- a/content/manuals/accounts/organization/setup/orgs.md +++ b/content/manuals/accounts/organization/setup/orgs.md @@ -1,9 +1,15 @@ --- -title: Create your organization +title: Create a Docker organization linkTitle: Create weight: 10 -description: Learn how to create an organization. -keywords: docker organizations, organization, create organization, docker teams, organization management +description: Create a Docker organization and choose its namespace and plan. +keywords: + - create Docker organization + - organization namespace + - organization name + - Docker Team + - Docker Business + - Docker Home aliases: - /admin/organization/setup/orgs/ - /docker-hub/orgs/ @@ -12,67 +18,78 @@ aliases: {{< summary-bar feature_name="Admin orgs" >}} -There are multiple ways to create an organization. You can either: - -- Create a new organization using the **Create Organization** option in the - Docker Home -- Convert an existing user account to an organization +Create an organization to group members and teams under one namespace and +one subscription. Your Docker ID stays an individual account. To use an +existing Docker ID as the namespace, see +[Convert a Docker account to an organization](/manuals/accounts/organization/setup/convert-account.md). ## Prerequisites -- Before you create an organization, you need a [Docker ID](/manuals/accounts/individual/create-account.md). -- For prerequisites and detailed instructions on converting an existing user account to an organization, see - [Convert an account into an organization](/manuals/accounts/organization/setup/convert-account.md). +You need a [Docker ID](/manuals/accounts/_index.md) before you create an +organization. > [!TIP] -> Need a different plan for your team's needs? Review different [Docker subscriptions and features](https://www.docker.com/pricing?ref=Docs&refAction=DocsAdminOrgs) to choose a subscription for your organization. +> +> Review [Docker subscriptions and features](https://www.docker.com/pricing?ref=Docs&refAction=DocsAdminOrgs) +> before you choose a plan. ## Create an organization -1. Sign in to [Docker Home](https://app.docker.com/) and navigate to the bottom - of the organization list. Select **Create new organization**. -1. Choose a subscription for your organization, a billing cycle, and specify how many seats you need. See [Docker Pricing](https://www.docker.com/pricing?ref=Docs&refAction=DocsAdminOrgs) for details on the features offered in the Team and Business subscription. -1. Select **Continue to profile**, then **Create an organization** to create a new organization. -1. Enter an **Organization namespace**. This is the official, unique name for - your organization in Docker Hub. - - It's not possible to change the name of the organization after you've created it. - - Your Docker ID and organization can't share the same name. - - If you want to use your Docker ID as the organization name, then you must first [convert your account into an organization](/manuals/accounts/organization/setup/convert-account.md). -1. Enter your **Company name**. This is the full name of your company. - - Docker displays the company name on your organization page and in the details of any - public images you publish. - - You can update the company name anytime by navigating to your organization's **Settings** page. -1. Select **Continue to billing** to continue, then enter your organization's billing information. Select **Continue to payment** to continue to the billing portal. -1. Provide your payment details and select **Purchase**. +When you create a new organization, you must select a Docker plan, +enter organization details, and verify billing details. -You've now created an organization. +1. Sign in to [Docker Home](https://app.docker.com/) and select + **Create new organization** at the bottom of the organization list. +1. On **Plan**, choose a subscription, a billing cycle, and the number of + seats. Select **Continue to profile**. +1. On **Organization**, enter the details for the new organization. + - If you already belong to one or more organizations, this step opens + as **Choose an organization**, which applies the subscription to an + existing organization. + - Select **Create an organization** to make a new one instead. The + picker is replaced by the **Organization namespace** and + **Organization name** fields. + - For what each field means, see + [Names versus namespaces](/manuals/accounts/organization/setup/_index.md#names-versus-namespaces). +1. Select **Continue to billing**. +1. On **Billing**, enter billing information and select + **Continue to payment**. +1. On **Payment**, enter payment details and select **Purchase**. + +You can now view your new organization. ## View an organization -To view an organization: +1. Sign in to [Docker Home](https://app.docker.com). +1. Select your organization. -1. Sign in to [Docker Home](https://app.docker.com) and select your - organization. - -Docker Home contains many options that let you to -configure your organization. +Docker Home lists the options you use to configure the organization. ## Merge organizations > [!WARNING] > -> If you are merging organizations, it is recommended to do so at the _end_ of -> your billing cycle. When you merge an organization and downgrade another, you -> will lose seats on your downgraded organization. Docker does not offer -> refunds for downgrades. +> Merge organizations at the end of your billing cycle. When you merge an +> organization and downgrade another, you lose seats on the downgraded +> organization. Docker doesn't offer refunds for downgrades. -If you have multiple organizations that you want to merge into one, complete -the following steps: +If you have multiple organizations that you want to merge into one: -1. Based on the number of seats from the secondary organization, [purchase additional seats](../manage/manage-seats.md) for the primary organization account that you want to keep. -1. Manually add users to the primary organization and remove existing users from the secondary organization. -1. Manually move over your data, including all repositories. -1. Once you're done moving all of your users and data, [downgrade](../../../subscription-billing/plans/docker.md#cancel-a-docker-plan) the secondary account to a free subscription. Note that Docker does not offer refunds for downgrading organizations mid-billing cycle. +1. Based on the number of seats from the secondary organization, + [purchase additional seats](../manage/manage-seats.md) for the primary + organization you want to keep. +1. Add users to the primary organization and remove them from the + secondary organization. +1. Move your data, including repositories. +1. After the users and data are on the primary organization, + [downgrade](../../../subscription-billing/plans/docker.md#cancel-a-docker-plan) + the secondary account to a free subscription. Docker doesn't offer + refunds for a downgrade in the middle of a billing cycle. If your organization has a Docker Business subscription with a purchase -order, contact Support or your Account Manager at Docker. +order, contact Support or your account manager at Docker. + +## Next steps + +- [Onboard your organization](/manuals/accounts/organization/setup/onboard.md) +- [Manage organization members](/manuals/accounts/organization/manage/members.md) diff --git a/content/manuals/faqs/accounts.md b/content/manuals/faqs/accounts.md index b6b8c333c2..731a50a157 100644 --- a/content/manuals/faqs/accounts.md +++ b/content/manuals/faqs/accounts.md @@ -4,9 +4,25 @@ linkTitle: Accounts weight: 10 description: FAQs about Docker IDs, account creation, organizations, companies, seats, and members keywords: - docker ID, docker account FAQ, change docker ID, username taken, trademark, - organization name, organization namespace, create account, Google, GitHub, - deactivate docker ID, organizations, members, seats, company, company owners + - docker ID + - docker account FAQ + - change docker ID + - username taken + - trademark + - organization name + - organization namespace + - create account + - Google + - GitHub + - deactivate docker ID + - organizations + - members + - seats + - company + - company owners + - convert Docker account + - sign in after convert + - organization owner tags: [FAQ] toc_max: 2 aliases: @@ -68,12 +84,17 @@ Docker ID for you. ### What's an organization name or namespace? -The organization name, sometimes referred to as the organization namespace or -the organization ID, is the unique identifier of a Docker organization. The -organization name can't be the same as an existing Docker ID. +The organization namespace and the organization name are different. -For more information, see -[Organization accounts](/manuals/accounts/organization/_index.md). +The namespace is the permanent identifier for the organization. Image names +use it as the first part, as in `namespace/image:tag`. You can't change it, +and it can't match an existing Docker ID. + +The organization name is the public name of the organization. You can change +it. + +For the fields you set when you create an organization, see +[Create a Docker organization](/manuals/accounts/organization/setup/orgs.md). ### How can I see how many active users are in my organization? @@ -82,7 +103,8 @@ find out how many users have Docker Desktop installed. If your organization doesn't use this software, you can run an internal survey to find out who is using Docker Desktop. -For more information, see [Identify your Docker users and their Docker accounts](/manuals/accounts/organization/setup/onboard.md#step-one-identify-your-docker-users). +For more information, see +[Identify your Docker users and their Docker accounts](/manuals/accounts/organization/setup/onboard.md#step-one-identify-your-docker-users). ### Do users need to authenticate with Docker before an owner can add them to an organization? @@ -97,7 +119,11 @@ Yes. You can Some benefits of enforcing sign-in are: - Ensures users receive the benefits of your subscription. -- Ensures security features like [Image Access Management](/manuals/desktop/enterprise/hardened-desktop/image-access-management.md) and [Registry Access Management](/manuals/desktop/enterprise/hardened-desktop/registry-access-management.md) are applied. +- Ensures security features like + [Image Access Management](/manuals/desktop/enterprise/hardened-desktop/image-access-management.md) + and + [Registry Access Management](/manuals/desktop/enterprise/hardened-desktop/registry-access-management.md) + are applied. - Ensures you gain insights into users' activity. ### Can I convert my personal Docker ID to an organization account? @@ -109,6 +135,20 @@ revert it to a personal user account. For prerequisites and instructions, see [Convert an account into an organization](/manuals/accounts/organization/setup/convert-account.md). +### Can I convert an individual account that uses single sign-on? + +No. **Convert** shows "Your account uses single sign-on. Contact your +administrator to manage these settings." + +### Why can't I sign in after converting my account to an organization? + +Converting signs you out and removes your email address from every Docker +account, so you can no longer sign in with it. Sign in with the Docker ID you +named as the owner and select the organization in Docker Home. If you named +someone else as the owner, sign up again and ask that owner to invite you. See +[Convert a Docker account to an organization](/manuals/accounts/organization/setup/convert-account.md#conversion) +for the full explanation. + ### Do organization invitees take up seats? Yes. A user invited to an organization will take up one of the provisioned