Skip to content

clarify roles permissions #24813

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
akristen merged 1 commit into from
Apr 17, 2026
+7 −6
Merged

clarify roles permissions #24813

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 7 additions & 6 deletions content/manuals/enterprise/security/roles-and-permissions/core-roles.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@ A company owner has the same organization management permissions as an organizat

### Content and registry permissions

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

| Permission | Member | Editor | Owner |
| :---------------------------------------------------- | :----- | :----- | :---- |
Expand All @@ -47,11 +47,13 @@ These permissions apply organization-wide, including all repositories in your or
| View teams | ✅ | ✅ | ✅ |
| Assign team permissions to repositories | ❌ | ✅ | ✅ |

When you add members to teams, you can grant additional repository permissions
You can grant repository permissions to members
beyond their organization role:
Copy link
Copy Markdown
Contributor

@craig-osterhout craig-osterhout Apr 17, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For some reason, my brain short-circuited on this part and it took me a while to understand what it was trying to convey. I'm guessing it's just saying there are 2 different permission checks. Maybe provide an example or some flow diagram of permission checks for different combinations of each.

Copy link
Copy Markdown
Contributor Author

@akristen akristen Apr 17, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm going to leave this as is but I've added it to a to do list for when I do a freshness sweep on this part of the admin docs. It's a good callout


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

To extend access to private repositories, assign a custom role to organization members or configure team permissions.

### Organization management permissions

Expand Down Expand Up @@ -79,12 +81,11 @@ beyond their organization role:
| Upgrade and downgrade plans | ❌ | ❌ | ✅ |

> [!TIP]
>
>
> If you want more granular access control, you can
> [upgrade to a Docker Business plan](https://www.docker.com/pricing?ref=Docs&refAction=DocsEnterpriseCoreRoles)
> for custom roles and advanced permissions.


_\* If not part of a company_

### Docker Scout permissions
Expand Down
Loading