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
Copy file name to clipboardExpand all lines: content/manuals/docker-hub/release-notes.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -47,13 +47,13 @@ known issues for each Docker Hub release.
47
47
48
48
## 2023-08-28
49
49
50
-
- Organizations with SSO enabled can assign members to roles, organizations, and teams with [SCIM role mapping](scim.md#set-up-role-mapping).
50
+
- Organizations with SSO enabled can assign members to roles, organizations, and teams with [SCIM role mapping](scim.md#set-up-role-mapping).
51
51
52
52
## 2023-07-26
53
53
54
54
### New
55
55
56
-
- Organizations can assign the [editor role](roles-and-permissions.md) to members to grant additional permissions without full administrative access.
56
+
- Organizations can assign the [editor role](/manuals/enterprise/security/roles-and-permissions/_index.md) to members to grant additional permissions without full administrative access.
Roles control what users can do in your Docker organization. When you invite users or create teams, you assign them roles that determine their permissions for repositories, teams, and organization settings.
25
+
26
+
Docker provides two types of roles to meet different organizational needs:
27
+
28
+
-[Core roles](/manuals/enterprise/security/roles-and-permissions/core-roles.md) with predefined permissions
29
+
-[Custom roles](/manuals/enterprise/security/roles-and-permissions/custom-roles.md) that you can tailor to your specific requirements
30
+
31
+
## Docker roles
32
+
33
+
### Core roles
34
+
35
+
Core roles are Docker's built-in roles with predefined permission sets:
36
+
37
+
-**Member**: Non-administrative role with basic access. Members can view other organization members and pull images from repositories they have access to.
38
+
-**Editor**: Partial administrative access. Editors can create, edit, and delete repositories, and manage team permissions for repositories.
39
+
-**Owner**: Full administrative access. Owners can manage all organization settings, including repositories, teams, members, billing, and security features.
40
+
41
+
### Custom roles
42
+
43
+
Custom roles allow you to create tailored permission sets by selecting specific permissions from categories like user management, team management, billing, and Hub permissions. Use custom roles when Docker's core roles don't fit your needs.
44
+
45
+
## When to use each role
46
+
47
+
Use core roles when:
48
+
49
+
- Docker's predefined permission sets match your organizational structure
50
+
- You want simple, straightforward role assignments
51
+
- You're getting started with Docker organization management
52
+
- Your access control needs are standard and don't require fine-grained permissions
53
+
54
+
Use custom roles when:
55
+
56
+
- You need specific permission combinations not available in core roles
57
+
- You want to create specialized roles like billing administrators, security auditors, or repository managers
58
+
- You need department-specific access control
59
+
- You want to implement the principle of least privilege with precise permission grants
60
+
61
+
## How roles work together
62
+
63
+
Users and teams can be assigned either a core role or a custom role, but not both. However, roles work in combination with team permissions:
64
+
65
+
1.**Role permissions**: Applied organization-wide (core or custom role). Custom roles can grant permissions to both organization-wide settings and repository access.
66
+
2.**Team permissions**: Additional repository-specific permissions when users are added to teams. This is a separate permission system from role-based permissions.
67
+
68
+
This layered approach gives you flexibility to provide broad organizational access through roles and specific repository access through team memberships.
69
+
70
+
## Next steps
71
+
72
+
Choose the role type that best fits your organization's needs:
Roles control what users can do in your organization. When you invite users, you assign them a role that determines their permissions for repositories, teams, and organization settings.
13
+
Core roles are Docker's built-in roles with predefined permission sets.
14
+
This page provides an overview of Docker's core roles and permissions for each role.
14
15
15
-
This page provides an overview of Docker roles and permissions for each role.
16
+
## What are core roles?
16
17
17
-
## Organization roles
18
+
Docker organizations have three core roles:
18
19
19
-
Docker organizations have three main roles:
20
-
21
-
- Member: Non-administrative role with basic access. Members can view other organization members and pull images from repositories they have access to.
22
-
- Editor: Partial administrative access. Editors can create, edit, and delete repositories. They can also manage team permissions for repositories.
23
-
- Owner: Full administrative access. Owners can manage all organization settings, including repositories, teams, members, billing, and security features.
24
-
25
-
## Permissions by role
20
+
-**Member**: Non-administrative role with basic access. Members can view other organization members and pull images from repositories they have access to.
21
+
-**Editor**: Partial administrative access. Editors can create, edit, and delete repositories. They can also manage team permissions for repositories.
22
+
-**Owner**: Full administrative access. Owners can manage all organization settings, including repositories, teams, members, billing, and security features.
26
23
27
24
> [!NOTE]
28
25
>
29
-
> An owner role assigned at the company level has the same access as an owner role assigned at the organization level. For more information, see [Company overview](/admin/company/).
26
+
> A company owner has the same organization management permissions as an organization owner, but there are some content and registry permissions that company owners don't have (for example, repository pull/push). For more information, see [Company overview](/admin/company/).
30
27
31
28
### Content and registry permissions
32
29
33
30
These permissions apply organization-wide, including all repositories in your organization's namespace.
0 commit comments