Repository navigation
Conversation
Clarify token permissions, expiration, and CLI sign-in, and explain shared token behavior on the access tokens overview. Co-authored-by: Cursor <cursoragent@cursor.com>
Correct who can manage tokens, the resource scopes shown in Docker Home, and how tokens authenticate to the Hub API. Co-authored-by: Cursor <cursoragent@cursor.com>
The personal and organization pages repeated who each token is for. That choice now sits on the access tokens overview, and the personal access token page keeps its note about organization tokens. Co-authored-by: Cursor <cursoragent@cursor.com>
Best practices now follow the introduction, before the prerequisites, so the constraints are visible before the create steps. Co-authored-by: Cursor <cursoragent@cursor.com>
Personal access token permissions, organization access token scopes, and Docker Hub API support now live on one reference page, with links from the how-to pages and the overview grid. Co-authored-by: Cursor <cursoragent@cursor.com>
Address review feedback on PAT/OAT/OIDC framing, scopes, and add FAQs for auto-generated tokens and login credential errors. Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
✅ Deploy Preview for docsdocker ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Replace reference-style links and custom heading IDs with inline links and generated anchors, and quote the sign-in error in the account FAQ heading.
| | Image Pull | `scope-image-pull` | Pull images | | ||
| | Image Push | `scope-image-push` | Push images. Includes Image Pull | | ||
| | Image Delete | `scope-image-delete` | Delete images and tags through registry endpoints. Includes Image Push | | ||
| | Repository Read | `scope-repository-read` | Read repository metadata, the Dockerfile, and stars | | ||
| | Repository Edit | `scope-repository-edit` | Edit privacy, categories, Dockerfile, description, and stars. Includes Repository Read | | ||
| | Repository Admin | `scope-repository-admin` | Delete the repository. Includes Repository Edit | | ||
| | Tag Read | `scope-tag-read` | List and read tags, image lists, attestations, and compose files | | ||
| | Tag Admin | `scope-tag-admin` | Delete tags. Includes Tag Read | | ||
| | Webhook Read | `scope-webhook-read` | List webhook pipelines and delivery history | | ||
| | Webhook Edit | `scope-webhook-edit` | Create webhook pipelines. Includes Webhook Read | | ||
| | Webhook Admin | `scope-webhook-admin` | Delete webhook pipelines. Includes Webhook Edit | | ||
| | Repository Group Read | `scope-repo-group-read` | List and read repository group assignments | | ||
| | Repository Group Edit | `scope-repo-group-edit` | Create and update repository group assignments. Includes Repository Group Read | | ||
| | Repository Group Admin | `scope-repo-group-admin` | Delete repository group assignments. Includes Repository Group Edit | | ||
| | Repository Settings Admin | `scope-repository-settings-admin` | Configure immutable tag rules | |
There was a problem hiding this comment.
@dotjoshrc Are we good with exposing the scope-* prefix on these scopes?
There was a problem hiding this comment.
fwiw the current docs do this same pattern but on a limited set of scopes. not sure if that answers the question, or if this is more about adding more to the table than the 3 that are currently public.
| | Report Read | `scope-report-read` | Download organization usage reports | | ||
| | Repository Create | `scope-repository-create` | Create repositories in the organization namespace | | ||
| | Repository List | `scope-repository-list` | List all repositories in the namespace, including private ones | | ||
| | Registry Usage Read | `scope-registry-usage-read` | Read namespace-level registry usage metrics | |
There was a problem hiding this comment.
question (non-blocking): @akristen this is an ever growing list of scopes, do we have a mechanism to have these synced in some manner?
There was a problem hiding this comment.
Nothing that automates updates to doc as they scale out, but I have my own set up to keep track of changes for now. I can experiment to make it more seamless tho
Refreshing access tokens docs