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
Organization and company owners can assign roles to individuals giving them different permissions in the organization. This guide outlines Docker's organization roles and their permission scopes.
12
+
This guide outlines Docker's organization roles and their permission scopes.
15
13
16
14
## Roles
17
15
18
-
When you invite users to your organization, you assign them a role. A role is a collection of permissions. Roles define whether users can create repositories, pull images, create teams, and configure organization settings.
16
+
When you invite users to your organization, you assign them a role. A role is a
17
+
collection of permissions. Roles define whether users can create repositories,
18
+
pull images, create teams, and configure organization settings.
19
19
20
20
The following roles are available to assign:
21
21
22
-
- Member: Non-administrative role. Members can view other members that are in the same organization.
23
-
- Distributor Member: Restricted-access role. Distributor Members can only view and pull from repositories they’ve been explicitly granted access to. They cannot view other members or teams.
24
-
- Editor: Partial administrative access to the organization. Editors can create, edit, and delete repositories. They can also edit an existing team's access permissions.
25
-
- Organization owner: Full organization administrative access. Organization owners can manage organization repositories, teams, members, settings, and billing.
26
-
- Company owner: In addition to the permissions of an organization owner, company owners can configure settings for their associated organizations.
22
+
- Member: Non-administrative role. Members can view other members that are in
23
+
the same organization.
24
+
- Editor: Partial administrative access to the organization. Editors can
25
+
create, edit, and delete repositories. They can also edit an existing team's
26
+
access permissions.
27
+
- Owner: Full organization administrative access. Owners can manage organization
28
+
repositories, teams, members, settings, and billing.
27
29
28
30
Owners can manage roles for members of an organization using Docker Hub or the Admin Console:
31
+
29
32
- Update a member role in [Docker Hub](/manuals/admin/organization/members.md#update-a-member-role)
30
33
- Update an organization's members or company in the [Admin Console](/manuals/admin/company/users.md#update-a-member-role)
31
34
- Learn more about [organizations and companies](/manuals/admin/_index.md)
@@ -34,15 +37,18 @@ Owners can manage roles for members of an organization using Docker Hub or the A
34
37
35
38
> [!NOTE]
36
39
>
37
-
> Company owners have the same access as organization owners for all associated organizations. For more information, see [Company overview](/admin/company/).
40
+
> Company owners have the same access as owners for all associated organizations. For more information, see [Company overview](/admin/company/).
38
41
39
42
The following sections describe the permissions for each role.
40
43
41
44
### Content and registry permissions
42
45
43
-
The following table outlines content and registry permissions for member, editor, and organization owner roles. These permissions and roles apply to the entire organization, including all the repositories in the namespace for the organization.
46
+
The following table outlines content and registry permissions for member,
47
+
editor, and owner roles. These permissions and roles apply to the entire
48
+
organization, including all the repositories in the namespace for the
49
+
organization.
44
50
45
-
| Permission | Member | Editor |Organization owner|
| Star, favorite, vote, and comment on content | ✅ | ✅ | ✅ |
@@ -59,45 +65,52 @@ The following table outlines content and registry permissions for member, editor
59
65
| View teams | ✅ | ✅ | ✅ |
60
66
| Assign team permissions to repositories | ❌ | ✅ | ✅ |
61
67
62
-
When you add members to a team, you can manage their repository permissions. For team repository permissions, see [Create and manage a team permissions reference](/manuals/admin/organization/manage-a-team.md#permissions-reference).
68
+
When you add members to a team, you can manage their repository permissions.
69
+
For team repository permissions, see [Create and manage a team permissions reference](/manuals/admin/organization/manage-a-team.md#permissions-reference).
63
70
64
-
The following diagram provides an example of how permissions may work for a user. In this example, the first permission check is for the role: member or editor. Editors have administrative permissions for repositories across the namespace of the organization. Members may have administrative permissions for a repository if they're a member of a team that grants those permissions.
71
+
The following diagram provides an example of how permissions may work for a
72
+
user. In this example, the first permission check is for the role: member or
73
+
editor. Editors have administrative permissions for repositories across the
74
+
namespace of the organization. Members may have administrative permissions for
75
+
a repository if they're a member of a team that grants those permissions.
65
76
66
77
67
78
68
79
### Organization management permissions
69
80
70
-
The following table outlines organization management permissions for member, editor, organization owner, and company owner roles.
71
-
72
-
| Permission | Member | Editor | Organization owner | Company owner |
0 commit comments