add rows (#25657)

Adding rows

---------

Co-authored-by: Cursor <cursoragent@cursor.com>

Author: akristen

content/manuals/enterprise/security/roles-and-permissions/core-roles.md

@@ -1,25 +1,36 @@
 ---
-title: Core roles
-description: Control access to content, registry, and organization management with roles in your organization.
-keywords: members, teams, organization, company, roles, access, docker hub, docker home, security, permissions
+title: Core roles and permissions
+linkTitle: Core roles
+description: Compare Member, Editor, and Owner permissions for content, registry, and organization management.
+keywords: core roles, member, editor, owner, permissions, organization, company, docker hub, docker home, security, oidc connections, teams
 aliases:
   - /enterprise/security/roles-and-permissions/
 ---
 
 {{< summary-bar feature_name="General admin" >}}
 
 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.
+This page summarizes permissions for each core 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](/manuals/admin/company/_index.md).
+- **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](/manuals/admin/company/_index.md).
 
 ### Content and registry permissions
 
@@ -44,14 +55,18 @@ These permissions apply organization-wide.
 | Edit build settings                                   | ❌     | ❌     | ✅    |
 | View teams                                            | ✅     | ✅     | ✅    |
 | Assign team permissions to repositories               | ❌     | ✅     | ✅    |
+| Manage OIDC connections                               | ❌     | ✅     | ✅    |
 
-You can grant repository permissions to members
-beyond their organization role:
+You can grant repository permissions to members beyond their
+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 do not grant pull access to private repositories — use team permissions for that.
+To extend access to private repositories, configure team permissions.
+Custom roles can grant organization-wide permissions to manage
+repositories (create, edit, delete) but do not grant pull access to
+private repositories — use team permissions for that.
 
 ### Organization management permissions