update unassociated machines for clarification (#23505)

## Description
- Added some clarifying language for Kapa/Gordon for unassociated
machines to make it clear it can be enabled for the entire org (all
machines) or individual machines

## Related issues or tickets

https://docker.atlassian.net/browse/ENGDOCS-3027?atlOrigin=eyJpIjoiYTAxOTY4NmViZDY5NDk5ZGIxOTg2NWJmYTgyZWU5YzMiLCJwIjoiaiJ9
This commit is contained in:
Sarah Sanders
2025-10-07 10:42:51 -04:00
committed by GitHub
parent 9181177b0e
commit e534111744

View File

@@ -86,6 +86,11 @@ be required to sign in to Docker Desktop. Once they sign in, their email
addresses will appear in the Unassociated list, allowing you to then add them
to your organization.
You can enable sign-in enforcement using two methods:
- For all unassociated machines in your organization
- For individual unassociated machines
> [!IMPORTANT]
>
> Sign-in enforcement only takes effect after Docker Desktop is restarted.
@@ -93,6 +98,8 @@ Users can continue using Docker Desktop until their next restart.
### Enable sign-in enforcement for all unassociated machines
To enable sign-in enforcement for all unassociated machines:
1. Sign in to the [Admin Console](https://app.docker.com/admin) and select
your organization.
1. In **User management**, select **Unassociated**.
@@ -113,6 +120,8 @@ as **Pending** until they update to version 4.41 or later.
### Enable sign-in enforcement for individual unassociated machines
To enable sign-in enforcement for individual unassociated machines:
1. Sign in to the [Admin Console](https://app.docker.com/admin) and select
your organization.
1. In **User management**, select **Unassociated**.