Skip to content

docs: clarify sandbox PAT permissions #26236

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
dave123981 wants to merge 1 commit into
base: main
Choose a base branch
from
+7 −0
Open

docs: clarify sandbox PAT permissions #26236

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: 7 additions & 0 deletions content/manuals/ai/sandboxes-api/authentication.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -50,6 +50,13 @@ for CI jobs and unattended applications. When creating the token, select the
`sandbox:use` permission in your Docker account's personal access token
settings. Registry permissions alone don't grant Cloud Sandboxes access.

The `sandbox:use` permission authorizes the PAT to access Cloud Sandboxes, but
it doesn't grant the account's granular permissions. Each API operation also
checks the permissions required for that operation. For example, creating a
sandbox requires `sandboxesCreate`, reading it requires `sandboxesRead`, and
deleting it requires `sandboxesDelete`. Your PAT must have `sandbox:use`, and
your account must have the permission required for the operation.

Provide your Docker ID and PAT to the SDK. For example, read them from your
application's environment:

Expand Down
Loading