API access
Personal API Tokens let a user call the Customer API from scripts and remote tools. A token never grants more access than its owner’s current Workspace membership and role.
Ownership and Workspace scope
Section titled “Ownership and Workspace scope”Each token belongs to one user and one Workspace. The server checks the owner’s live membership, role, token scope, expiry, and revocation state on every request.
Removing or suspending the Workspace membership removes token access immediately. A token cannot authenticate Workspace administration, billing changes, provider setup, The Captain, MCP, or credential-management routes.
Scopes
Section titled “Scopes”supply-chain:readreads authorized posture, repositories, scans, findings, rules, and plan information.supply-chain:scansubmits bounded hosted scans to the token’s Workspace.
Choose only the scopes the client needs.
Secret handling
Section titled “Secret handling”The Control Plane displays a new token once. Signals Corps stores a keyed digest rather than the plaintext secret. Tokens have a name, an expiry date, and a revocation state.
Revocation takes effect immediately. Do not put a token in source control, browser storage, logs, screenshots, support tickets, or messages to The Captain.