docker
/
docs
mirror of https://github.com/docker/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

docs freshness: updates for organization section (#21630) 

## Description
- Docs freshness updates:
    - Style guide updates/consistency
- Improved UI flow steps, some did not link to DH or Admin Console, and
were vague
    - Added Admin Console steps where missing
    - Fixed a few incorrect UI flows
- ENGDOCS-2357 updates: Updated Insights DD table for new fields

## Related issues or tickets
- [ENGDOCS-2348](https://docker.atlassian.net/browse/ENGDOCS-2348)
- [ENGDOCS-2357](https://docker.atlassian.net/browse/ENGDOCS-2357)

## Reviews
- [ ] Editorial review

[ENGDOCS-2348]:
https://docker.atlassian.net/browse/ENGDOCS-2348?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ
[ENGDOCS-2357]:
https://docker.atlassian.net/browse/ENGDOCS-2357?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ

---------

Co-authored-by: David Karlsson <35727626+dvdksn@users.noreply.github.com>
This commit is contained in:
Sarah Sanders 2024-12-16 08:42:08 -08:00 committed by GitHub
parent bd7617d955
commit de764a8138
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
7 changed files with 178 additions and 97 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

BIN
content/manuals/admin/images/team-repo-permission.png
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 20 KiB

2
content/manuals/admin/organization/general-settings.md
View File

@ -11,7 +11,7 @@ This section describes how to manage organization settings in the Docker Admin C
## Configure general information
General organization information appears on your organization landing page in Docker Hub.
General organization information appears on your organization landing page in the Admin Console.
This information includes:
- Organization Name

34
content/manuals/admin/organization/insights.md
View File

@ -15,17 +15,19 @@ productivity and efficiency across the organization.
Key benefits include:
* Uniform working environment. Establish and maintain standardized
- Uniform working environment. Establish and maintain standardized
configurations across teams.
* Best practices. Promote and enforce usage guidelines to ensure optimal
- Best practices. Promote and enforce usage guidelines to ensure optimal
performance.
* Increased visibility. Monitor and drive adoption of organizational
- Increased visibility. Monitor and drive adoption of organizational
configurations and policies.
* Optimized license use. Ensure that developers have access to advanced
- Optimized license use. Ensure that developers have access to advanced
features provided by a Docker subscription.
## View Insights for organization users
{{< include "admin-early-access.md" >}}
1. Go to the [Admin Console](https://app.docker.com/admin/) and sign in to an
account that is an organization owner.
2. Select your company on the **Choose profile** page.
@ -33,18 +35,19 @@ Key benefits include:
4. On the **Insights** page, select the period of time for the data.
> [!NOTE]
>
> Insights data is not real-time and is updated daily. At the top-right of the
> Insights page, view the **Last updated** date to understand when the data was
> last updated.
You can view data in the following charts:
* [Docker Desktop users](#docker-desktop-users)
* [Builds](#builds)
* [Containers](#containers)
* [Docker Desktop usage](#docker-desktop-usage)
* [Docker Hub images](#docker-hub-images)
* [Extensions](#extensions)
- [Docker Desktop users](#docker-desktop-users)
- [Builds](#builds)
- [Containers](#containers)
- [Docker Desktop usage](#docker-desktop-usage)
- [Docker Hub images](#docker-hub-images)
- [Extensions](#extensions)
### Docker Desktop users
@ -56,13 +59,12 @@ counts.
The chart contains the following data.
| Data | Description |
| Data | Description |
|:-----------------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Total active users | The number of users that have actively used Docker Desktop and either signed in with a Docker account that has a license in your organization or signed in to a Docker account with an email address from a domain associated with your organization. <br><br>Users who don’t sign in to an account associated with your organization are not represented in the data. To ensure users sign in with an account associated with your organization, you can [enforce sign-in](/security/for-admins/enforce-sign-in/). |
| Active with license | The number of users that have actively used Docker Desktop and have signed in to a Docker account with a license in your organization. |
| Active without license | The number of users that have actively used Docker Desktop, are linked to a Docker account with an email address from a domain associated with your organization, and don’t have a license assigned to their account. <br><br>Users without a license don’t receive the benefits of your subscription. You can use [domain audit](/security/for-admins/domain-audit/) to identify users without a license. You can also use [Just-in-Time provisioning](/security/for-admins/provisioning/just-in-time/) or [SCIM](/security/for-admins/provisioning/scim/) to help automatically provision users with a license. Note that when SSO is configured and enforced, active without license will be 0. |
| Users opted out of analytics | The number of users that are a member of your organization that have opted out of sending analytics. <br><br>When users opt out of sending analytics, you won't see any of their data in Insights. To ensure that the data includes all users, you can use [Settings Management](/desktop/hardened-desktop/settings-management/) to set `analyticsEnabled` for all your users. |
| Active users (graph) | The view over time for total active users. |
| Active user | The number of users that have actively used Docker Desktop and either signed in with a Docker account that has a license in your organization or signed in to a Docker account with an email address from a domain associated with your organization. <br><br>Users who don’t sign in to an account associated with your organization are not represented in the data. To ensure users sign in with an account associated with your organization, you can [enforce sign-in](/security/for-admins/enforce-sign-in/). |
| Total organization members | The number of users that have used Docker Desktop, regardless of their Insights activity. |
| Users opted out of analytics | The number of users that are a member of your organization that have opted out of sending analytics. <br><br>When users opt out of sending analytics, you won't see any of their data in Insights. To ensure that the data includes all users, you can use [Settings Management](/desktop/hardened-desktop/settings-management/) to set `analyticsEnabled` for all your users. |
| Active users (graph) | The view over time for total active users. |
### Builds

67
content/manuals/admin/organization/manage-a-team.md
View File

@ -10,37 +10,36 @@ aliases:
You can create teams for your organization in Docker Hub and the Docker Admin Console. You can [configure repository access for a team](#configure-repository-permissions-for-a-team) in Docker Hub.
A team is a group of Docker users that belong to an organization. An
organization can have multiple teams. An
organization owner can then create new teams and add members to an existing team
using their Docker ID or email address and by selecting a team the user should be part of. Members aren't required to be part of a team to be associated with an organization.
A team is a group of Docker users that belong to an organization. An organization can have multiple teams. An organization owner can then create new teams and add members to an existing team using their Docker ID or email address and by selecting a team the user should be part of. Members aren't required to be part of a team to be associated with an organization.
The organization owner can add additional organization owners to help them manage users, teams, and repositories in the organization by assigning them the owner role.
## Organization owner
An organization owner is an administrator who is responsible to manage
repositories and add team members to the organization. They have full access to
private repositories, all teams, billing information, and org settings. An org
owner can also specify [permissions](#permissions-reference) for each team in
the organization. Only an org owner can enable [SSO](../../security/for-admins/single-sign-on/_index.md)
for
the organization. When SSO is enabled for your organization, the org owner can
An organization owner is an administrator who has the following permissions:
- Manage repositories and add team members to the organization.
- Access private repositories, all teams, billing information, and organization settings.
- Specify [permissions](#permissions-reference) for each team in the organization.
- Enable [SSO](../../security/for-admins/single-sign-on/_index.md) for the organization.
When SSO is enabled for your organization, the organization owner can
also manage users. Docker can auto-provision Docker IDs for new end-users or
users who'd like to have a separate Docker ID for company use through SSO
enforcement.
The org owner can also add additional org owners to help them manage users, teams, and repositories in the organization.
The organization owner can also add additional organization owners to help them manage users, teams, and repositories in the organization.
## Create a team
{{< tabs >}}
{{< tab name="Docker Hub" >}}
1. Go to **Organizations** in Docker Hub, and select your organization.
2. Select the **Teams** tab and then select **Create Team**.
3. Fill out your team's information and select **Create**.
4. [Add members to your team](members.md#add-a-member-to-a-team).
1. Sign in to [Docker Hub](https://hub.docker.com).
2. Select **Organizations** and choose your organization.
3. Select the **Teams** tab and then select **Create Team**.
4. Fill out your team's information and select **Create**.
5. [Add members to your team](members.md#add-a-member-to-a-team).
{{< /tab >}}
{{< tab name="Admin Console" >}}
@ -61,19 +60,18 @@ The org owner can also add additional org owners to help them manage users, team
Organization owners can configure repository permissions on a per-team basis.
For example, you can specify that all teams within an organization have "Read and
Write" access to repositories A and B, whereas only specific teams have "Admin"
access. Note that org owners have full administrative access to all repositories within the organization.
access. Note that organization owners have full administrative access to all repositories within the organization.
To give a team access to a repository
To give a team access to a repository:
1. Navigate to **Organizations** in Docker Hub, and select your organization.
2. Select the **Teams** tab and select the team that you'd like to configure repository access to.
3. Select the **Permissions** tab and select a repository from the
1. Sign in to [Docker Hub](https://hub.docker.com).
2. Select **Organizations** and choose your organization.
3. Select the **Teams** tab and select the team that you'd like to configure repository access to.
4. Select the **Permissions** tab and select a repository from the
**Repository** drop-down.
4. Choose a permission from the **Permissions** drop-down list and select
5. Choose a permission from the **Permissions** drop-down list and select
**Add**.
![Team Repo Permissions](../images/team-repo-permission.png)
Organization owners can also assign members the editor role to grant partial administrative access. See [Roles and permissions](../../security/for-admins/roles-and-permissions.md) for more about the editor role.
### Permissions reference
@ -110,8 +108,10 @@ you automatically have "Read-only" permissions:
To view a team's permissions across all repositories:
1. Open **Organizations** > **_Your Organization_** > **Teams** > **_Team Name_**.
2. Select the **Permissions** tab, where you can view the repositories this team can access.
1. Sign in to [Docker Hub](https://hub.docker.com).
2. Select **Organizations** and choose your organization.
3. Select **Teams** and choose your team name.
4. Select the **Permissions** tab, where you can view the repositories this team can access.
## Delete a team
@ -120,19 +120,20 @@ Organization owners can delete a team in Docker Hub or Admin Console. When you r
{{< tabs >}}
{{< tab name="Docker Hub" >}}
1. Go to **Organizations** in Docker Hub, and select your organization.
2. Select the **Teams** tab.
3. Select the name of the team that you want to delete.
4. Select **Settings**.
5. Select **Delete Team**.
6. Review the confirmation message, then select **Delete**.
1. Sign in to [Docker Hub](https://hub.docker.com).
2. Select **Organizations** and choose your organization.
3. Select the **Teams** tab.
4. Select the name of the team that you want to delete.
5. Select **Settings**.
6. Select **Delete Team**.
7. Review the confirmation message, then select **Delete**.
{{< /tab >}}
{{< tab name="Admin Console" >}}
{{< include "admin-early-access.md" >}}
1. In Admin Console, select your organization.
1. In the [Admin Console](https://app.docker.com/admin), select your organization.
2. In the **User management** section, select **Teams**.
3. Select the **Actions** icon next to the name of the team you want to delete.
4. Select **Delete team**.

22
content/manuals/admin/organization/members.md
View File

@ -205,7 +205,25 @@ Owners can export a CSV file containing all members. The CSV file for a company
- Invited to Organizations: All organizations the user is an invitee of within a company
- Account Created: The time and date when the user account was created
To export a CSV file of the members:
{{< tabs >}}
{{< tab name="Docker Hub" >}}
To export a CSV file of your members:
1. Sign in to [Docker Hub](https://hub.docker.com).
2. Select **Organizations**, your organization, and then **Members**.
3. Select the **Action** icon and then select **Export users as CSV**.
3. Select the **Action** icon and then select **Export users as CSV**.
{{< /tab >}}
{{< tab name="Admin Console" >}}
{{< include "admin-early-access.md" >}}
To export a CSV file of your members:
1. In the [Admin Console](https://app.docker.com/admin), select your organization.
2. Select **Members**.
3. Select the **download** icon to export a CSV file of all members.
{{< /tab >}}
{{< /tabs >}}

23
content/manuals/admin/organization/onboard.md
View File

@ -15,9 +15,9 @@ aliases:
Learn how to onboard your organization using Docker Hub or the Docker Admin Console.
Onboarding your organization lets administrators gain visibility into the activity of your users and enforce security settings. In addition, members of your organization receive increased pull limits and other organization wide benefits. For more details, see [Docker subscriptions and features](../../subscription/details.md).
Onboarding your organization lets administrators gain visibility into user activity and enforce security settings. In addition, members of your organization receive increased pull limits and other organization wide benefits. For more details, see [Docker subscriptions and features](../../subscription/details.md).
In this guide, you'll learn how to get started with the following:
In this guide, you'll learn how to do the following:
- Identify your users to help you efficiently allocate your subscription seats
- Invite members and owners to your organization
@ -27,7 +27,8 @@ In this guide, you'll learn how to get started with the following:
## Prerequisites
Before you start to onboard your organization, ensure that you:
- Have a Docker Team or Business subscription. See [Pricing & Subscriptions](https://www.docker.com/pricing/) for details.
- Have a Docker Team or Business subscription. See [Docker Pricing](https://www.docker.com/pricing/) for details.
> [!NOTE]
>
@ -35,24 +36,24 @@ Before you start to onboard your organization, ensure that you:
- Familiarize yourself with Docker concepts and terminology in the [glossary](/glossary/) and [FAQs](/faq/admin/general-faqs/).
## Step 1: Identify your Docker users and their Docker accounts
## Step 1: Identify your Docker users
Identifying your users will ensure that you allocate your subscription seats efficiently and that all your Docker users receive the benefits of your subscription.
1. Identify the Docker users in your organization.
- If your organization uses device management software, like MDM or JAMF, you may 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, like MDM or Jamf, you may 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:
- Mac: `/Applications/Docker.app`
- Windows: `C:\Program Files\Docker\Docker`
- Linux: `/opt/docker-desktop`
- If your organization doesn't use device management software or your users haven't installed Docker Desktop yet, you may survey your users.
2. Instruct all your Docker users in your organization to update their existing Docker account's email address to an address that's in your organization's domain, or to create a new account using an email address in your organization's domain.
2. Instruct all your organization's Docker users to update their existing Docker account's email address to an address that's in your organization's domain, or to create a new account using an email address in your organization's domain.
- 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 go [sign up](https://hub.docker.com/signup) using their email address in your organization's domain.
3. Ask your Docker sales representative or [contact sales](https://www.docker.com/pricing/contact-sales/) to get a list of Docker accounts that use an email address in your organization's domain.
## Step 2: Invite owners
When you create an organization, you are the only owner. You may optionally add additional owners. 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. Owners can help you onboard and manage your organization.
To add an owner, invite a user and assign them the owner role. For more details, see [Invite members](/admin/organization/members/).
@ -68,22 +69,22 @@ Configuring SSO and SCIM is optional and only available to Docker Business subsc
You can manage your members in your identity provider and automatically provision them to your Docker organization with SSO and SCIM. See the following for more details.
- [Configure SSO](/manuals/security/for-admins/single-sign-on/configure.md) to authenticate and add members when they sign in to Docker through your identity provider.
- Optional: [Enforce SSO](/manuals/security/for-admins/single-sign-on/connect.md) to ensure that when users sign in to Docker, they must use SSO.
- Optional. [Enforce SSO](/manuals/security/for-admins/single-sign-on/connect.md) to ensure that when users sign in to Docker, they must use SSO.
> [!NOTE]
>
> Enforcing single sign-on (SSO) and [Step 5: Enforce sign-in for Docker
> Desktop](#step-5-enforce-sign-in-for-docker-desktop) are different
> features. For more details, see
> [Enforcing sign-in versus enforcing single sign-on (SSO)](/security/for-admins/enforce-sign-in/#enforcing-sign-in-versus-enforcing-single-sign-on-sso).
- [Configure SCIM](/security/for-admins/provisioning/scim/) to automatically provision, add, and de-provision members to Docker through your identity provider.
## Step 5: 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](../../subscription/details.md) and they can circumvent
[Docker’s security features](/security/for-admins/hardened-desktop/) for your
organization.
receive the [benefits of your organization’s subscription](../../subscription/details.md) and they can circumvent [Docker’s security features](/security/for-admins/hardened-desktop/).
There are multiple ways you can enforce sign-in, depending on your company's
set up and preferences:

127
content/manuals/admin/organization/orgs.md
View File

@ -10,33 +10,27 @@ aliases:
This section describes how to create an organization. Before you begin:
- You need a [Docker ID](/accounts/create-account/).
- Review the [Docker subscriptions and features](../../subscription/details.md) to determine what plan to choose for your organization.
- You need a [Docker ID](/accounts/create-account/)
- Review the [Docker subscriptions and features](../../subscription/details.md) to determine what plan to choose for your organization
## Create an organization
There are multiple ways to create an organization. You can create a brand new
organization using the **Create Organization** option in Docker Hub, or you can
convert an existing user account to an organization. The following section
contains instructions on how to create a new organization. For prerequisites and
There are multiple ways to create an organization. You can either:
- Create a new organization using the **Create Organization** option in Docker Hub
- Convert an existing user account to an organization
The following section contains instructions on how to create a new organization. For prerequisites and
detailed instructions on converting an existing user account to an organization, see
[Convert an account into an organization](../convert-account.md).
To create an organization:
{{< tabs >}}
{{< tab name="Docker Hub" >}}
1. Sign in to [Docker Hub](https://hub.docker.com/) using your Docker ID, your email address, or your social provider.
2. Select **Organizations** and then **Create Organization** to create a new
organization.
3. Choose a plan for your organization and select **Buy Now**. See
[Docker Pricing](https://www.docker.com/pricing/)
for details on the features offered in the Team and Business plan.
> [!NOTE]
>
> Selecting **Buy Now** isn't an obligation to pay. You can complete
> this step without incurring a payment.
4. Enter a name for your organization. This is the official, unique name for
2. Select **Organizations** and then **Create Organization** to create a new organization.
3. Choose a plan for your organization, a billing cycle, and specify how many seats you need. See [Docker Pricing](https://www.docker.com/pricing/) for details on the features offered in the Team and Business plan.
4. Select **Continue to profile**.
5. 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.
@ -44,34 +38,67 @@ organization after you've created it.
>
> You can't use the same name for the organization and your Docker ID. If you want to use your Docker ID as the organization name, then you must first [convert your account into an organization](../convert-account.md).
5. Enter the name of your company. This is the full name of your company. Docker
6. 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.
6. Select **Purchase** to continue.
7. Enter the billing information for your organization.
8. Select **Submit** to continue to the billing portal.
9. In the billing portal, select **Qty** to update the number of seats you require, then select **Update**.
10. (Optional) Select annual or monthly billing cycle.
11. Follow the on-screen instructions to pay for your subscription.
7. Select **Continue to billing** to continue.
8. Enter your organization's billing information and select **Continue to payment** to continue to the billing portal.
9. Provide your card details and select **Purchase**.
You've now created an organization.
{{< /tab >}}
{{< tab name="Admin Console" >}}
{{< include "admin-early-access.md" >}}
To create an organization:
1. Sign in to [Docker Home](https://app.docker.com/).
2. Under Settings and administration, select **Go to Admin Console**.
3. Select the **Organization** drop-down in the left-hand navigation and then **Create Organization**.
4. Choose a plan for your organization, a billing cycle, and specify how many seats you need. See [Docker Pricing](https://www.docker.com/pricing/) for details on the features offered in the Team and Business plan.
5. Select **Continue to profile**.
6. 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.
> [!NOTE]
>
> You can't use the same name for the organization and your Docker ID. If you want to use your Docker ID as the organization name, then you must first [convert your account into an organization](../convert-account.md).
7. 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.
8. Select **Continue to billing** to continue.
9. Enter your organization's billing information and select **Continue to payment** to continue to the billing portal.
10. Provide your card details and select **Purchase**.
You've now created an organization.
{{< /tab >}}
{{< /tabs >}}
## View an organization
{{< tabs >}}
{{< tab name="Docker Hub" >}}
To view an organization:
1. Sign in to Docker Hub with a user account that is a member of any team in the
organization.
1. Sign in to [Docker Hub](https://hub.docker.com) with a user account that is a member of any team in the
organization.
> [!NOTE]
>
> You can't _directly_ log in to an organization. This is especially
> You can't *directly* sign in to an organization. This is especially
> important to note if you create an organization by
[converting a user account](../convert-account.md), as conversion means you lose the ability to log into that
> "account", since it no longer exists. To view the organization you
> need to log in with the new owner account assigned during the
> conversion or another account that was added as a member. If you
> "account", since it no longer exists. To view the organization you
> need to sign in with the new owner account assigned during the
> conversion or another account that was added as a member. If you
> don't see the organization after logging in,
> then you are neither a member or an owner of it. An organization
> administrator needs to add you as a member of the organization.
@ -79,7 +106,7 @@ To view an organization:
2. Select **Organizations** in the top navigation bar, then choose your
organization from the list.
The organization landing page displays various options that allow you to
The organization landing page displays various options that let you to
configure your organization.
- **Members**: Displays a list of team members. You
@ -98,7 +125,7 @@ configure your organization.
details.
- **Settings**: Displays information about your
organization, and allows you to view and change your repository privacy
organization, and you to view and change your repository privacy
settings, configure org permissions such as
[Image Access Management](/manuals/security/for-admins/hardened-desktop/image-access-management.md), configure notification settings, and [deactivate](../deactivate-account.md#deactivate-an-organization) You can also update your organization name and company name that appear on your organization landing page. You must be an owner to access the
organization's **Settings** page.
@ -106,6 +133,38 @@ configure your organization.
- **Billing**: Displays information about your existing
[Docker subscription (plan)](../../subscription/_index.md), including the number of seats and next payment due date. For how to access the billing history and payment methods for your organization, see [View billing history](../../billing/history.md).
{{< /tab >}}
{{< tab name="Admin Console" >}}
{{< include "admin-early-access.md" >}}
To view an organization in the Admin Console:
1. Sign in to [Docker Home](https://app.docker.com).
2. Under Settings and administration, select **Go to Admin Console**.
3. Select your organization from the **Organization** drop-down in the left-hand navigation.
The Admin Console displays various options that let you to
configure your organization.
- **Members**: Displays a list of team members. You
can invite new members using the **Invite members** button. See [Manage members](./members.md) for details.
- **Teams**: Displays a list of existing teams and the number of
members in each team. See [Create a team](./manage-a-team.md) for details.
- **Activity** Displays the audit logs, a chronological list of activities that
occur at organization and repository levels. It provides the org owners a
report of all their team member activities. See [Audit logs](./activity-logs.md) for
details.
- **Security and access**: Manage security settings. For more information, see [Security](/manuals/security/_index.md).
- **Organization settings**: Update general settings, manage your company settings, or [deactivate your organization](/manuals/admin/deactivate-account.md).
{{< /tab >}}
{{< /tabs >}}
## Merge organizations
> [!WARNING]