|
1 | 1 | --- |
2 | | -title: Manage domains |
| 2 | +title: Add and manage domains |
3 | 3 | description: Add, verify, and manage domains to control user access and enable auto-provisioning in Docker organizations |
4 | 4 | keywords: domain management, domain verification, auto-provisioning, user management, DNS, TXT record, Admin Console |
5 | | -weight: 55 |
| 5 | +weight: 40 |
6 | 6 | aliases: |
7 | 7 | - /security/for-admins/domain-management/ |
8 | 8 | - /docker-hub/domain-audit/ |
@@ -79,56 +79,8 @@ your domain name. |
79 | 79 | {{< /tab >}} |
80 | 80 | {{< /tabs >}} |
81 | 81 |
|
82 | | -## Configure auto-provisioning |
83 | | - |
84 | | -Auto-provisioning automatically adds users to your organization when they sign in with email addresses that match your verified domains. You must verify a domain before enabling auto-provisioning. |
85 | | - |
86 | | -> [!IMPORTANT] |
87 | | -> |
88 | | -> For domains that are part of an SSO connection, Just-in-Time (JIT) provisioning takes precedence over auto-provisioning when adding users to an organization. |
89 | | -
|
90 | | -### How auto-provisioning works |
91 | | - |
92 | | -When auto-provisioning is enabled for a verified domain: |
93 | | - |
94 | | -- Users who sign in to Docker with matching email addresses are automatically added to your organization. |
95 | | -- Auto-provisioning only adds existing Docker users to your organization, it doesn't create new accounts. |
96 | | -- Users experience no changes to their sign-in process. |
97 | | -- Company and organization owners receive email notifications when new users are added. |
98 | | -- You may need to [manage seats](/manuals/subscription/manage-seats.md) to accommodate new users. |
99 | | - |
100 | | -### Enable auto-provisioning |
101 | | - |
102 | | -Auto-provisioning is configured per domain. To enable it: |
103 | | - |
104 | | -1. Sign in to [Docker Home](https://app.docker.com) and select |
105 | | -your company or organization. |
106 | | -1. Select **Admin Console**, then **Domain management**. |
107 | | -1. Select the **Actions menu** next to the domain you want to enable |
108 | | -auto-provisioning for. |
109 | | -1. Select **Enable auto-provisioning**. |
110 | | -1. Optional. If enabling auto-provisioning at the company level, select an |
111 | | -organization. |
112 | | -1. Select **Enable** to confirm. |
113 | | - |
114 | | -The **Auto-provisioning** column will update to **Enabled** for the domain. |
115 | | - |
116 | | -### Disable auto-provisioning |
117 | | - |
118 | | -To disable auto-provisioning for a user: |
119 | | - |
120 | | -1. Sign in to [Docker Home](https://app.docker.com) and select |
121 | | -your organization. If your organization is part of a company, select the company |
122 | | -and configure the domain for the organization at the company level. |
123 | | -1. Select **Admin Console**, then **Domain management**. |
124 | | -1. Select the **Actions menu** next to your domain. |
125 | | -1. Select **Disable auto-provisioning**. |
126 | | -1. Select **Disable** to confirm. |
127 | | - |
128 | 82 | ## Audit domains for uncaptured users |
129 | 83 |
|
130 | | -{{< summary-bar feature_name="Domain audit" >}} |
131 | | - |
132 | 84 | Domain audit identifies uncaptured users. Uncaptured users are Docker users who have authenticated using an email address associated with your verified domains but aren't members of your Docker organization. |
133 | 85 |
|
134 | 86 | ### Limitations |
|
0 commit comments