chainctl
chainctl Chainguard Control
For the complete documentation index, see llms.txt.
Chainguard provides customers with a set of built-in roles as part of its Identity and Access Management (IAM) system. These roles have different permissions and capabilities that allow them to serve specialized purposes, from general administrative access to access for specific resources like registries, APK packages, and programming language libraries.
This reference provides an overview of all Chainguard IAM capabilities and shows which built-in roles include each capability. Each capability represents a specific permission or action that can be performed within the Chainguard platform.
For more information on roles and role-bindings within Chainguard’s IAM model, please refer to our Overview of roles and role-bindings.
This guide outlines the built-in Chainguard IAM roles available to most customer organizations. You can find more info about specific roles in your organization with the following chainctl command:
chainctl iam roles listEvery role grants actions on at least one Chainguard resource. Most actions are create, list, update, or delete, and a few resources use others, such as get, accept, or call. For example, the owner role can create, delete, list, and update custom roles within Chainguard, while the viewer role can only list them.
This guide outlines the following built-in roles provided by Chainguard:
owner: Full administrative access with all capabilitieseditor: viewer access plus creating, updating, and deleting container repositories, editing Custom Assembly overlays, drafting library build requests, and managing event subscriptionsviewer: Read-only access across all resources, can pull images, and can run Guardener sessionslimited_owner: Owner of a Starter organization, with viewer access plus pull tokens, invites limited to the organization’s email domain, removing members, billing, and turning on Chainguard Checks and Chainguard Workspacesconsole_viewer: Read-only access across all resources and cannot pull images or APK packages, run Guardener sessions, or view legal termsregistry.pull: Container image accessregistry.pull_token_creator: Chainguard registry token management with additional repository capabilitiesregistry.push: registry.pull access plus pushing images, and creating, updating, and deleting repositories and tagsregistry.editor: registry.pull access plus creating, updating, and deleting repositories, and editing Custom Assembly overlaysapk.pull: Access to the organization’s APK packages, including the private APK repositoryapk.push: apk.pull access plus uploading and deleting APK packageslibraries.java.pull: Java library accesslibraries.java.pull_token_creator: Java token managementlibraries.java.push: libraries.java.pull access plus Java library uploadslibraries.python.pull: Python library accesslibraries.python.pull_token_creator: Python library token managementlibraries.python.push: libraries.python.pull access plus Python library uploadslibraries.javascript.pull: JavaScript library accesslibraries.javascript.pull_token_creator: JavaScript library token managementlibraries.javascript.push: libraries.javascript.pull access plus JavaScript library uploadsguardener.user: Minimum role for running Guardener sessions, including Guardener conversion, terms lookup, and registry pull accessguardener.admin: Extends guardener.user with permission to accept the legal terms required before Guardener sessions can startsandbox.user: Start, view, and cancel Chainguard Checks runs, and open Chainguard Workspaces sessionssandbox.identity.user: Use shared identities in Chainguard Workspaces sessionsmcp.tool_user: Call tools on Chainguard MCP serversactions.viewer: View the Chainguard Actions catalogThe 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.
For example, the apk.pull role grants list access for APK packages and groups, and get access to APK package content. This means identities with this role can pull the organization’s APK packages and retrieve information about the organization, but won’t have general access to the organization’s Chainguard registry resources.
The following table maps Chainguard resources to the built-in roles that have permissions for them. Each row represents a specific resource type (like apk, repo, identity, etc.), describes its purpose, and lists which actions each built-in role has on that resource.
| Resource | Purpose | Roles with access to this resource |
|---|---|---|
account_associations | Link cloud provider accounts to organization |
|
actions | View the Chainguard Actions catalog |
|
advisories | View security advisories for the packages in Chainguard images |
|
apk | Manage APK packages in the registry |
|
apk.blobs | Download APK package binary content |
|
billing | Manage the organization’s billing and payment method |
|
build_report | Access detailed build and scan reports for images and packages |
|
group_invites | Send and manage invitations to join Chainguard organization |
|
groups | Manage organization and hierarchical structures |
|
guardener.actions | Have Guardener migrate a repository’s GitHub Actions to Chainguard Actions by opening a pull request |
|
guardener.association | View and manage the GitHub organizations connected through the Chainguard App |
|
guardener.dfc | Convert Dockerfiles to use Chainguard images with Guardener |
|
guardener.entitlement | View the organization’s Guardener settings, such as which repositories Guardener can access |
|
guardener.images | Request and view container image migrations for a repository |
|
guardener.scan | View the dependency scans Guardener runs on connected repositories |
|
identity | Create and manage user identities, service accounts, and pull tokens |
|
identity_providers | Configure custom identity providers (OIDC, SAML) for authentication |
|
identity_providers.scim | Turn on SCIM provisioning for a custom identity provider and manage its tokens |
|
identity_providers.scim.users | View the users a custom identity provider provisioned through SCIM |
|
libraries.artifacts | View Chainguard Library artifact metadata and information |
|
libraries.aws_marketplace.subscriptions | Manage Chainguard Libraries subscriptions bought through AWS Marketplace |
|
libraries.cache | View and clear the organization’s Chainguard Libraries resolution cache |
|
libraries.entitlements | Manage access permissions for Chainguard Libraries |
|
libraries.java | Access Chainguard Libraries for Java |
|
libraries.javascript | Access Chainguard Libraries for JavaScript |
|
libraries.policy | Create and manage the cooldown and malware policies applied to upstream library pulls |
|
libraries.policy.binding | Apply Chainguard Libraries policies to the organization |
|
libraries.policy.block_event | View the library pulls a policy blocked |
|
libraries.python | Access Chainguard Libraries for Python |
|
libraries.remote_registries | Configure the upstream registries the organization’s virtual repositories pull from |
|
libraries.request_groups | Request library versions for Chainguard to build, and track those requests |
|
libraries.request_groups.items | Edit the individual libraries in a draft build request |
|
libraries.storage_usage | View how much storage the organization’s uploaded libraries use in each ecosystem |
|
manifest | Access and manage container image manifests |
|
manifest.metadata | View container image manifest metadata and attestations |
|
mcp.tool | Call tools on Chainguard MCP servers |
|
packages.entitlements | View which tier of Chainguard OS Packages the organization is entitled to, base or FIPS |
|
policies.binding | Turn image pull policies on for the organization |
|
policies.decision | View the allow and block decisions image pull policies made |
|
policies.override | Exempt a specific image from policy enforcement |
|
policies.policy | View and manage image pull policies, such as blocking end-of-life images |
|
record_signatures | View cryptographic signature verification records |
|
referrers | View the signatures, attestations, and other artifacts attached to an image |
|
registry.deployments | View the Helm charts associated with a container repository |
|
registry.entitlements | View registry access entitlements and permissions |
|
registry.entitlements.images | Add, remove, and swap the images in the organization’s registry entitlement |
|
registry.overlays | View and edit Custom Assembly overlays |
|
registry.settings | View the organization’s registry settings, such as whether unique tags and the End-of-Life Grace Period are on by default |
|
repo | Create and manage container repositories (including Custom Assembly resources) |
|
repo.blobs | Download container image binary content |
|
role_bindings | Assign roles to identities (users and service accounts) |
|
roles | Create, modify, and manage custom Chainguard IAM roles |
|
sandbox.identity | Create the Chainguard identity a Workspaces session acts through, and define and use shared session identities |
|
sandbox.run | Start, view, and cancel Chainguard Checks runs |
|
sandbox.session | Open Chainguard Workspaces sessions, and list every user’s sessions in the organization |
|
sboms | Access Software Bill of Materials for packages and images |
|
skills | View the Chainguard Agent Skills catalog and publish skills |
|
skills.entitlements | Manage which Chainguard Agent Skills the organization can access |
|
skills.harden | Submit, track, and cancel skill hardening jobs |
|
subscriptions | Manage CloudEvent subscriptions for notifications and automation |
|
tag | Manage Chainguard container image tags |
|
telemetry.containers | View the container images that connected repositories use, as Guardener observes them |
|
terms | View and accept the legal terms a Chainguard product requires before you can use it |
|
version | View version information across all resources and assets |
|
vuln | Create vulnerability reports and assessments |
|
vuln_report | Manage detailed vulnerability assessments for specific resources |
|
vuln_reports | View high-level vulnerability report summaries |
|
The following table compares the general abilities of the built-in roles described in the previous summary:
| Role | Pull Images | List Tags/Repos | View SBOMs/Diffs | Create IAM Resources | Create Pull Tokens | Libraries Access |
|---|---|---|---|---|---|---|
owner | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
editor | ✅ | ✅ | ✅ | ✕ | ✕ | ✕ |
viewer | ✅ | ✅ | ✅ | ✕ | ✕ | ✕ |
limited_owner | ✅ | ✅ | ✅ | ✅ | ✅ | ✕ |
console_viewer | ✕ | ✅ | ✅ | ✕ | ✕ | ✕ |
registry.pull | ✅ | ✅ | ✅ | ✕ | ✕ | ✕ |
registry.pull_token_creator | ✅ | ✅ | ✅ | ✅ | ✅ | ✕ |
registry.push | ✅ | ✅ | ✅ | ✕ | ✕ | ✕ |
registry.editor | ✅ | ✅ | ✅ | ✕ | ✕ | ✕ |
apk.pull | ✕ | ✕ | ✕ | ✕ | ✕ | ✕ |
apk.push | ✕ | ✕ | ✕ | ✕ | ✕ | ✕ |
libraries.java.pull | ✕ | ✕ | ✕ | ✕ | ✕ | ✅ |
libraries.java.pull_token_creator | ✕ | ✕ | ✕ | ✅ | ✅ | ✅ |
libraries.java.push | ✕ | ✕ | ✕ | ✕ | ✕ | ✅ |
libraries.python.pull | ✕ | ✕ | ✕ | ✕ | ✕ | ✅ |
libraries.python.pull_token_creator | ✕ | ✕ | ✕ | ✅ | ✅ | ✅ |
libraries.python.push | ✕ | ✕ | ✕ | ✕ | ✕ | ✅ |
libraries.javascript.pull | ✕ | ✕ | ✕ | ✕ | ✕ | ✅ |
libraries.javascript.pull_token_creator | ✕ | ✕ | ✕ | ✅ | ✅ | ✅ |
libraries.javascript.push | ✕ | ✕ | ✕ | ✕ | ✕ | ✅ |
guardener.user | ✅ | ✅ | ✅ | ✕ | ✕ | ✕ |
guardener.admin | ✅ | ✅ | ✅ | ✕ | ✕ | ✕ |
sandbox.user | ✕ | ✕ | ✕ | ✕ | ✕ | ✕ |
sandbox.identity.user | ✕ | ✕ | ✕ | ✕ | ✕ | ✕ |
mcp.tool_user | ✕ | ✕ | ✕ | ✕ | ✕ | ✕ |
actions.viewer | ✕ | ✕ | ✕ | ✕ | ✕ | ✕ |
Notes
manifest, repo, tag, and sboms resourcesapk.pull role is specialized for APK package management, not container operationslist access as viewer, but can’t pull blobs (apk.blobs, repo.blobs), view legal terms (terms), run Guardener conversions or migrations (guardener.dfc, guardener.actions, guardener.images), or list the GitHub organizations connected through the Chainguard App (guardener.association). This makes it a safe role for inviting team members who need Console visibility without the ability to pull images or APKs.The following roles are used for managing pull tokens for certain resources:
registry.pull_token_creatorlibraries.java.pull_token_creatorlibraries.python.pull_token_creatorlibraries.javascript.pull_token_creatorFor example, the libraries.*.pull_token_creator roles are focused on their respective library ecosystems and don’t have container registry access.
These roles are able to create pull tokens because of the identity.create capability. However, none of these roles have the identity.list capability, meaning that they aren’t able to view the pull tokens they’ve created.
The reason for this is that Chainguard doesn’t distinguish pull token identities from other assumable identities at the IAM level. If these roles also had the identity.list capability, they would be able to view all the identities in that scope. By not including identity.list among their capabilities, the pull token creator roles have a more limited scope, as intended.
Last updated: 2026-10-13 13:55