You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
| 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/). |
62
-
| 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. |
63
-
| 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. |
64
-
| 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. |
65
-
| Active users (graph) | The view over time for total active users. |
64
+
| 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/). |
65
+
| Total organization members | The number of users that have used Docker Desktop, regardless of their Insights activity. |
66
+
| 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. |
67
+
| Active users (graph) | The view over time for total active users. |
Copy file name to clipboardExpand all lines: content/manuals/admin/organization/manage-a-team.md
+34-33Lines changed: 34 additions & 33 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,37 +10,36 @@ aliases:
10
10
11
11
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.
12
12
13
-
A team is a group of Docker users that belong to an organization. An
14
-
organization can have multiple teams. An
15
-
organization owner can then create new teams and add members to an existing team
16
-
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.
13
+
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.
17
14
18
15
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.
19
16
20
17
## Organization owner
21
18
22
-
An organization owner is an administrator who is responsible to manage
23
-
repositories and add team members to the organization. They have full access to
24
-
private repositories, all teams, billing information, and org settings. An org
25
-
owner can also specify [permissions](#permissions-reference) for each team in
26
-
the organization. Only an org owner can enable [SSO](../../security/for-admins/single-sign-on/_index.md)
27
-
for
28
-
the organization. When SSO is enabled for your organization, the org owner can
19
+
An organization owner is an administrator who has the following permissions:
20
+
21
+
- Manage repositories and add team members to the organization.
22
+
- Access private repositories, all teams, billing information, and organization settings.
23
+
- Specify [permissions](#permissions-reference) for each team in the organization.
24
+
- Enable [SSO](../../security/for-admins/single-sign-on/_index.md) for the organization.
25
+
26
+
When SSO is enabled for your organization, the organization owner can
29
27
also manage users. Docker can auto-provision Docker IDs for new end-users or
30
28
users who'd like to have a separate Docker ID for company use through SSO
31
29
enforcement.
32
30
33
-
The org owner can also add additional org owners to help them manage users, teams, and repositories in the organization.
31
+
The organization owner can also add additional organization owners to help them manage users, teams, and repositories in the organization.
34
32
35
33
## Create a team
36
34
37
35
{{< tabs >}}
38
36
{{< tab name="Docker Hub" >}}
39
37
40
-
1. Go to **Organizations** in Docker Hub, and select your organization.
41
-
2. Select the **Teams** tab and then select **Create Team**.
42
-
3. Fill out your team's information and select **Create**.
43
-
4.[Add members to your team](members.md#add-a-member-to-a-team).
38
+
1. Sign in to [Docker Hub](https://hub.docker.com).
39
+
2. Select **Organizations** and choose your organization.
40
+
3. Select the **Teams** tab and then select **Create Team**.
41
+
4. Fill out your team's information and select **Create**.
42
+
5.[Add members to your team](members.md#add-a-member-to-a-team).
44
43
45
44
{{< /tab >}}
46
45
{{< tab name="Admin Console" >}}
@@ -61,19 +60,18 @@ The org owner can also add additional org owners to help them manage users, team
61
60
Organization owners can configure repository permissions on a per-team basis.
62
61
For example, you can specify that all teams within an organization have "Read and
63
62
Write" access to repositories A and B, whereas only specific teams have "Admin"
64
-
access. Note that org owners have full administrative access to all repositories within the organization.
63
+
access. Note that organization owners have full administrative access to all repositories within the organization.
65
64
66
-
To give a team access to a repository
65
+
To give a team access to a repository:
67
66
68
-
1. Navigate to **Organizations** in Docker Hub, and select your organization.
69
-
2. Select the **Teams** tab and select the team that you'd like to configure repository access to.
70
-
3. Select the **Permissions** tab and select a repository from the
67
+
1. Sign in to [Docker Hub](https://hub.docker.com).
68
+
2. Select **Organizations** and choose your organization.
69
+
3. Select the **Teams** tab and select the team that you'd like to configure repository access to.
70
+
4. Select the **Permissions** tab and select a repository from the
71
71
**Repository** drop-down.
72
-
4. Choose a permission from the **Permissions** drop-down list and select
72
+
5. Choose a permission from the **Permissions** drop-down list and select
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.
78
76
79
77
### Permissions reference
@@ -110,8 +108,10 @@ you automatically have "Read-only" permissions:
110
108
111
109
To view a team's permissions across all repositories:
0 commit comments