The Wayback Machine - https://web.archive.org/web/20260308041702/https://docs.docker.com/enterprise/security/roles-and-permissions/core-roles/
Share feedback
Answers are generated based on the documentation.

Core roles

For: Administrators

Core roles are Docker's built-in roles with predefined permission sets. This page provides an overview of Docker's core roles and permissions for each role.

What are core roles?

Docker organizations have three core roles:

  • Member: Non-administrative role with basic access. Members can view other organization members and pull images from repositories they have access to.
  • Editor: Partial administrative access. Editors can create, edit, and delete repositories. They can also manage team permissions for repositories.
  • Owner: Full administrative access. Owners can manage all organization settings, including repositories, teams, members, billing, and security features.

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.

Content and registry permissions

These permissions apply organization-wide, including all repositories in your organization's namespace.

PermissionMemberEditorOwner
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βŒβœ…βœ…

When you add members to teams, you can grant additional repository permissions beyond their organization role:

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

Organization management permissions

PermissionMemberEditorOwner
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

If you want more granular access control, you can upgrade to a Docker Business plan for custom roles and advanced permissions.

* If not part of a company

Docker Scout permissions

PermissionMemberEditorOwner
View and compare analysis resultsβœ…βœ…βœ…
Upload analysis recordsβœ…βœ…βœ…
Activate and deactivate Docker Scout for a repositoryβŒβœ…βœ…
Create environmentsβŒβŒβœ…
Manage registry integrationsβŒβŒβœ…

Docker Build Cloud permissions

PermissionMemberEditorOwner
Use a cloud builderβœ…βœ…βœ…
Create and remove buildersβœ…βœ…βœ…
Configure builder settingsβœ…βœ…βœ…
Buy minutesβŒβŒβœ…
Manage subscription❌❌βœ