Docker core roles and permissions

Table of contents

For: Administrators

Docker organizations use built-in Member, Editor, and Owner roles with predefined permissions. This reference compares their permissions across Docker products. To assign a different combination of permissions, use custom roles instead.

Core roles

Docker organizations have three core roles:

Owner provides full administrative access. Owners can manage all organization settings, including repositories, teams, members, billing, and security features.
Editor has partial administrative access. Editors can create, edit, and delete repositories. They can also manage team permissions for repositories.
Member has basic, non-administrative access. Members can view other organization members and pull images from repositories they have access to.

A company owner has the same organization-management permissions as an organization owner. Content and registry permissions, such as repository pull and push, don't apply to company owners. For more information, see Company overview.

Permissions reference

Content and registry

These permissions apply organization-wide.

Permission	Member	Editor	Owner
Explore images and extensions	✅	✅	✅
Star, favorite, vote, and comment on content	✅	✅	✅
Pull images	✅	✅	✅
Create and publish an extension	✅	✅	✅
Become a Verified, Official, or Open Source publisher	❌	❌	✅
Edit and delete publisher repository logos	❌	✅	✅
Configure DVP analytics settings	❌	✅	✅
Observe content engagement as a publisher	❌	❌	✅
Create public and private repositories	❌	✅	✅
Disable public repositories	❌	✅	✅
Edit and delete repositories	❌	✅	✅
Manage tags	❌	✅	✅
View repository activity	❌	❌	✅
Set up Automated builds	❌	❌	✅
Edit build settings	❌	❌	✅
View teams	✅	✅	✅
Assign team permissions to repositories	❌	✅	✅
Manage OIDC connections	❌	✅	✅

You can grant repository permissions beyond a member's organization role:

Role permissions: Applied organization-wide (member or editor)
Team permissions: Additional permissions for specific repositories

To extend access to private repositories, configure team permissions. Custom roles can grant organization-wide permissions to manage repositories (create, edit, delete) but don't grant pull access to private repositories. Use team permissions for that.

Organization management

Permission	Member	Editor	Owner
Create teams	❌	❌	✅
Manage teams (including delete)	❌	❌	✅
Configure the organization's settings (including linked services)	❌	❌	✅
Add organizations to a company	❌	❌	✅
Invite members	❌	❌	✅
Manage members	❌	❌	✅
Manage member roles and permissions	❌	❌	✅
View member activity	❌	❌	✅
Export and reporting	❌	❌	✅
Image Access Management	❌	❌	✅
Registry Access Management	❌	❌	✅
Namespace access control	❌	❌	✅
Set up Single Sign-On (SSO) and SCIM	❌	❌	✅ *
Require Docker Desktop sign-in	❌	❌	✅ *
Manage billing information (for example, billing address)	❌	❌	✅
Manage payment methods (for example, credit card or invoice)	❌	❌	✅
View billing history	❌	❌	✅
Manage subscriptions	❌	❌	✅
Manage seats	❌	❌	✅
Upgrade and downgrade plans	❌	❌	✅

Tip
For more granular access control, upgrade to a Docker Business plan to use custom roles.

* If not part of a company

Docker Scout

Permission	Member	Editor	Owner
View and compare analysis results	✅	✅	✅
Upload analysis records	✅	✅	✅
Activate and deactivate Docker Scout for a repository	❌	✅	✅
Create environments	❌	❌	✅
Manage registry integrations	❌	❌	✅

Docker Build Cloud

Permission	Member	Editor	Owner
Use a cloud builder	✅	✅	✅
Create and remove builders	✅	✅	✅
Configure builder settings	✅	✅	✅
Buy minutes	❌	❌	✅
Manage subscription	❌	❌	✅

Next steps

Custom roles: Create tailored permission sets on a Docker Business plan
Manage organization members: Invite users and assign roles
Company overview: Understand company owner permissions versus organization owner permissions

What can I help you with?

Docker core roles and permissions

Core roles

Permissions reference

Content and registry

Organization management

Docker Scout

Docker Build Cloud

Next steps