Skip to content
CommandChain CommandChain CommandChain Docs

Issue a permission token

A permission token is access for something that is not a person. Settings → Governance → Tokens issues them. It needs the manage_tokens permission.

When to use one

Section titled “When to use one”

Use a token when a script, a job, or a service has to call your workspace and there is no human at the keyboard. A release script that has to reach an integration is the usual case.

Do not use one for a teammate. A person gets an invitation and a role, which is revocable, attributable, and shows up in the members list. A token shared with a person is none of those.

Issue it

Section titled “Issue it”
  1. Click + Issue Token.
  2. Issued to names the holder. Use something a reader can trace: service:summitline-release rather than token 3.
  3. Scope is the area it may act in. The four are integration:manage, approval:approve, admin:governance, and agent:execution.
  4. Capabilities narrow it inside that scope, comma separated. read, execute is narrower than read, write, delete.
  5. TTL is how long it lives, in seconds. The range is 60 seconds to 24 hours.

The token value is shown once, when it is created. There is no route that reads it back, which is the point.

Verify one

Section titled “Verify one”

A service holding a token can check it before relying on it. Verification answers whether the token is live, what scope it carries, and which capabilities it has, without revealing the value again. It is the call a receiving service makes at the top of a job so that an expired token fails loudly at the start rather than halfway through.

Revoke one

Section titled “Revoke one”

The token list shows every token, its scope, its capabilities, how long it has left, and its status. Revoke ends it immediately.

Revoking is not deleting: the row stays, marked revoked, so a later question about who held what is still answerable. An expired token needs no action at all, and its row stays too, reading Expired where the remaining time was. Nothing is swept, so the list is the history of what this workspace has minted and not only what is live right now. The audit log keeps the issue and revoke records either way.

What a token is not

Section titled “What a token is not”

A token does not raise anyone’s autonomy level and cannot approve its way past a gate that requires a person. approval:approve lets a service submit a decision it is entitled to make; it does not make an agent’s L1 action self-approving.

Next steps

Section titled “Next steps”