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
description: Learn about Docker's built-in Member, Editor, and Owner roles with predefined permissions.
@@ -34,9 +34,9 @@ Docker provides two types of roles to meet different organizational needs:
34
34
35
35
Core roles are Docker's built-in roles with predefined permission sets:
36
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.
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
40
41
41
### Custom roles
42
42
@@ -52,6 +52,7 @@ Use core roles when:
52
52
- Your access control needs are standard and don't require fine-grained permissions
53
53
54
54
Use custom roles when:
55
+
55
56
- You need specific permission combinations not available in core roles
56
57
- You want to create specialized roles like billing administrators, security auditors, or repository managers
57
58
- You need department-specific access control
@@ -61,13 +62,13 @@ Use custom roles when:
61
62
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:
63
64
64
-
1. Role permissions: Applied organization-wide (core or custom role)
65
-
2. Team permissions: Additional permissions for specific repositories when users are added to teams
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.
66
67
67
68
This layered approach gives you flexibility to provide broad organizational access through roles and specific repository access through team memberships.
68
69
69
70
## Next steps
70
71
71
72
Choose the role type that best fits your organization's needs:
Core roles are Docker's built-in roles with predefined permission sets.
14
-
This page provides an overview of Docker's core and permissions for each role.
14
+
This page provides an overview of Docker's core roles and permissions for each role.
15
15
16
16
## What are core roles?
17
17
18
18
Docker organizations have three core roles:
19
19
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.
23
-
24
-
## 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.
25
23
26
24
> [!NOTE]
27
25
>
28
-
> 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/).
29
27
30
28
### Content and registry permissions
31
29
32
30
These permissions apply organization-wide, including all repositories in your organization's namespace.
0 commit comments