wws_…) from Settings → Service accounts. The key acts on its own labelled identity, and the admin chooses up front exactly how much of the organization it may touch:
- a set of scopes — the resources the key can read and write, and
- a destructive-operations toggle — whether it may deploy, connect a repo, or delete whole resources.
Permissions & scopes
A key carries a fixed set of scopes, chosen when you issue it. Each area has aread and a write scope, and the key holds exactly the ones you select.
A new key is read-only —
mcp:read and kb:read — until you add more scopes.Destructive operations
Some actions can’t be undone or take a running agent offline. A service-account key may perform them only when the “Allow destructive operations” toggle is enabled for that key. The toggle is off by default and is independent of the scopes above: a key withmcp:write can edit content, but it still cannot run a destructive action unless the toggle is on.
With the toggle enabled, the key may:
Deploy & connect
- Clone managed project repo to GitHub
- Connect project to a user-owned GitHub repo
- Deploy the latest commit on an environment’s branch
- Migrate a managed project to a user-owned repo
- Promote a channel
- Redeploy a past deployment’s commit
- Roll back production to a past deployment
- Delete a project
- Delete environment
- Delete environment channel
write scope and are not gated by this toggle.