Skip to content

Commit 7e5cb8c

Browse files
sarahsanders-dockersarahsanders-docker
authored
security: add unassociated machines docs (#23103)
## Description - Adds unassociated machines (AA) docs - Docs are unlisted ## Related issues or tickets https://docker.atlassian.net/browse/ENGDOCS-2855 ## Reviews - [ ] Editorial review - [ ] Product review @smnovick ## Preview link https://deploy-preview-23103--docsdocker.netlify.app/unassociated-machines/
1 parent 66d5e5a commit 7e5cb8c

File tree

2 files changed

+214
-0
lines changed

2 files changed

+214
-0
lines changed

‎content/manuals/unassociated-machines/_index.md

Lines changed: 213 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,213 @@
1+
---
2+
title: Manage unassociated machines
3+
description: Learn how to manage unassociated machines using the Docker Admin Console
4+
keywords: unassociated machines, insights, manage users, enforce sign-in
5+
sitemap: false
6+
pagefind_exclude: true
7+
noindex: true
8+
params:
9+
sidebar:
10+
group: Enterprise
11+
---
12+
13+
{{% restricted title="About unassociated machines" %}}
14+
Unassociated machines is a private feature. Your Docker
15+
Account Executive must enable the feature for you.
16+
{{% /restricted %}}
17+
18+
Docker administrators can identify, view, and manage Docker Desktop machines
19+
that are likely associated with their organization but aren't currently linked
20+
to user accounts. This self-service capability helps you understand Docker
21+
Desktop usage across your organization and streamline user onboarding without
22+
IT involvement.
23+
24+
## Prerequisites
25+
26+
- Docker Business subscription
27+
- Organization owner access to your Docker organization
28+
29+
## About unassociated machines
30+
31+
Unassociated machines are Docker Desktop instances that Docker has identified
32+
as likely belonging to your organization based on usage patterns, but the users
33+
are not signed in to Docker Desktop with an account that is part of your
34+
organization.
35+
36+
## How Docker identifies unassociated machines
37+
38+
Docker uses telemetry data to identify which machines likely belong to your
39+
organization:
40+
41+
- Domain matching: Users signed in with email domains associated with your
42+
organization
43+
- Registry patterns: Analysis of container registry access patterns that
44+
indicate organizational usage
45+
46+
## View unassociated machines
47+
48+
To see detailed information about unassociated machines:
49+
50+
1. Sign in to the [Admin Console](https://app.docker.com/admin) and select
51+
your organization.
52+
1. In **User management**, select **Unassociated**.
53+
54+
The machine list displays:
55+
56+
- Machine ID (Docker-generated identifier)
57+
- The registry address used to predict whether a user is part of your
58+
organization
59+
- User email (only displays if the user is signed into Docker Desktop while
60+
using it)
61+
- Docker Desktop version
62+
- Operating system (OS)
63+
- Last activity date
64+
- Sign-in enforced status
65+
66+
You can:
67+
68+
- Export the list as CSV
69+
- Take actions on individual or multiple machines
70+
71+
## Enable sign-in enforcement for unassociated machines
72+
73+
> [!NOTE]
74+
>
75+
> Sign-in enforcement for unassociated machines is different from
76+
the [organization-level sign-in enforcement](/enterprise/security/enforce-sign-in/)
77+
available through `registry.json` and configuration profiles. This sign-in
78+
enforcement only requires users to sign in so admins can identify who is
79+
using the machine, meaning users can sign in with any email address. For more
80+
stringent security controls that limit sign-ins to users who are already part
81+
of your organization, see [Enforce sign-in](/enterprise/security/enforce-sign-in/).
82+
83+
Sign-in enforcement helps you identify who is using unassociated machines in
84+
your organization. When you enable enforcement, users on these machines will
85+
be required to sign in to Docker Desktop. Once they sign in, their email
86+
addresses will appear in the Unassociated list, allowing you to then add them
87+
to your organization.
88+
89+
> [!IMPORTANT]
90+
>
91+
> Sign-in enforcement only takes effect after Docker Desktop is restarted.
92+
Users can continue using Docker Desktop until their next restart.
93+
94+
### Enable sign-in enforcement for all unassociated machines
95+
96+
1. Sign in to the [Admin Console](https://app.docker.com/admin) and select
97+
your organization.
98+
1. In **User management**, select **Unassociated**.
99+
1. Turn on the **Enforce sign-in** toggle.
100+
1. In the pop-up modal, select **Require sign-in** to confirm.
101+
102+
The **Sign-in required** status will update for all unassociated machines to
103+
**Yes**.
104+
105+
> [!NOTE]
106+
>
107+
> When you enable sign-in enforcement for all unassociated machines, any new
108+
machines detected in the future will automatically have sign-in enforcement
109+
enabled. Sign-in enforcement requires Docker Desktop version 4.41 or later.
110+
Users with older versions will not be prompted to sign in and can continue
111+
using Docker Desktop normally until they update. Their status shows
112+
as **Pending** until they update to version 4.41 or later.
113+
114+
### Enable sign-in enforcement for individual unassociated machines
115+
116+
1. Sign in to the [Admin Console](https://app.docker.com/admin) and select
117+
your organization.
118+
1. In **User management**, select **Unassociated**.
119+
1. Locate the machine you want to enable sign-in enforcement for.
120+
1. Select the **Actions** menu and choose **Turn on sign-in enforcement**.
121+
1. In the pop-up modal, select **Require sign-in** to confirm.
122+
123+
The **Sign-in required** status will update for the individual machine to
124+
**Yes**.
125+
126+
> [!NOTE]
127+
>
128+
> Sign-in enforcement requires Docker Desktop version 4.41 or later. Users
129+
with older versions will not be prompted to sign in and can continue using
130+
Docker Desktop normally until they update. Their status shows as **Pending**
131+
until they update to version 4.41 or later.
132+
133+
### What happens when users sign in
134+
135+
After you enable sign-in enforcement:
136+
137+
1. Users must restart Docker Desktop. Enforcement only takes effect after
138+
restart.
139+
1. When users open Docker Desktop, they see a sign-in prompt. They must sign
140+
in to continue using Docker Desktop.
141+
1. User email addresses appear in the **Unassociated** list.
142+
1. You can add users to your organization.
143+
144+
Users can continue using Docker Desktop immediately after signing in, even
145+
before being added to your organization.
146+
147+
## Add unassociated machines to your organization
148+
149+
When users in your organization use Docker without signing in, their machines
150+
appear in the **Unassociated** list. You can add these users to your
151+
organization in two ways:
152+
153+
- Automatic addition:
154+
- Auto-provisioning: If you have verified domains with auto-provisioning
155+
enabled, users who sign in with a matching email domain will automatically
156+
be added to your organization. For more information on verifying domains and
157+
auto-provisioning, see [Domain management](/manuals/enterprise/security/domain-management.md).
158+
- SSO user provisioning: If you have SSO configured with
159+
[Just-in-Time provisioning](/manuals/enterprise/security/provisioning/just-in-time.md),
160+
users who sign in through your SSO connection will automatically be added
161+
to your organization.
162+
- Manual addition: If you don't have auto-provisioning or SSO set up, or if a
163+
user's email domain doesn't match your configured domains, their email will
164+
appear in the **Unassociated** list where you can choose to add them directly.
165+
166+
> [!NOTE]
167+
>
168+
> If you add users and do not have enough seats in your organization, a
169+
pop-up will appear prompting you to **Get more seats**.
170+
171+
### Add individual users
172+
173+
1. Sign in to the [Admin Console](https://app.docker.com/admin) and select
174+
your organization.
175+
1. In **User management**, select **Unassociated**.
176+
1. Locate the machine you want to add to your organization.
177+
1. Select the **Actions** menu and choose **Add to organization**.
178+
1. In the pop-up modal, select **Add user**.
179+
180+
### Bulk add users
181+
182+
1. Sign in to the [Admin Console](https://app.docker.com/admin) and select
183+
your organization.
184+
1. In **User management**, select **Unassociated**.
185+
1. Use the **checkboxes** to select the machines you want to add to your
186+
organizations.
187+
1. Select the **Add to organization** button.
188+
1. In the pop-up modal, select **Add users** to confirm.
189+
190+
## Disable sign-in enforcement
191+
192+
### Disable for all unassociated machines
193+
194+
1. Sign in to the [Admin Console](https://app.docker.com/admin) and select
195+
your organization.
196+
1. In **User management**, select **Unassociated**.
197+
1. Turn off the **Enforce sign-in** toggle.
198+
1. In the pop-up modal, select **Turn off sign-in requirement** to confirm.
199+
200+
The **Sign-in required** status will update for all unassociated machines to
201+
**No**.
202+
203+
### Disable for specific unassociated machines
204+
205+
1. Sign in to the [Admin Console](https://app.docker.com/admin) and select
206+
your organization.
207+
1. In **User management**, select **Unassociated**.
208+
1. Locate the machine you want to disable sign-in enforcement for.
209+
1. Select the **Actions** menu and choose **Turn off sign-in enforcement**.
210+
1. In the pop-up modal, select **Turn off sign-in requirement** to confirm.
211+
212+
The **Sign-in required** status will update for the individual machine to
213+
**No**.

‎layouts/index.robots.txt

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,7 @@
66

77
{{- if hugo.IsProduction -}}
88
User-agent: *
9+
Disallow: /unassociated-machines/
910

1011

1112
Sitemap: {{ "sitemap.xml" | absURL }}

0 commit comments

Comments
 (0)