Skip to content

Update Guardener role requirements on capabilities page #3329

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

Open
s-stumbo wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update Guardener role requirements on capabilities page #3329

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
7 changes: 6 additions & 1 deletion .../administration/iam-organizations/roles-role-bindings/capabilities-reference.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,7 @@ This guide outlines the following built-in roles provided by Chainguard:
* **Administrative Roles:**
* `owner` - Full administrative access with all capabilities
* `editor` - Limited administrative access with mostly read permissions and event management
* `viewer` - Read-only access across all resources and **can** pull images
* `viewer` - Read-only access across all resources, **can** pull images, and can run Guardener sessions
* `limited_owner` - Read access across all resources with ability to create identities and role bindings, and pull images
* `console_viewer` - Read-only access across all resources and **cannot** pull images, without blob access or the ability to manage event subscriptions
* **Registry and Container Roles:**
Expand All @@ -48,6 +48,9 @@ This guide outlines the following built-in roles provided by Chainguard:
* `libraries.python.pull_token_creator` - Python library token management
* `libraries.javascript.pull` - JavaScript library access
* `libraries.javascript.pull_token_creator` - JavaScript library token management
* **Guardener Roles**:
* `guardener.user` - Minimum role for running Guardener sessions, including Guardener conversion, terms lookup, and registry pull access
* `guardener.admin` - Extends `guardener.user` with permission to accept the legal terms required before Guardener sessions can start

The administrative roles are useful for user profiles that require broad, but clearly defined capabilities. The registry, container, and library roles have limited permissions, allowing them to manage only one specific Chainguard resource. These specialized, resource-specific roles grant minimal required access.

Expand Down Expand Up @@ -116,6 +119,8 @@ The following table compares the general abilities of the built-in roles describ
| `libraries.python.pull_token_creator` | ✕ | ✕ | ✕ | ✅ | ✅ | ✅ |
| `libraries.javascript.pull` | ✕ | ✕ | ✕ | ✕ | ✕ | ✅ |
| `libraries.javascript.pull_token_creator` | ✕ | ✕ | ✕ | ✅ | ✅ | ✅ |
| `guardener.user` | ✅ | ✅ | ✅ | ✕ | ✕ | ✕ |
| `guardener.admin` | ✅ | ✅ | ✅ | ✕ | ✕ | ✕ |

</div>

Expand Down