Developer access and tokens
Control API keys, webhooks, personal API tokens, installed tools, and personal tool handoffs.
- WhoOwners and admins
Control developer access
Set separate creation policies for workspace API keys and webhooks, then limit the scopes a new or rotated key may request.
- Disabled
- Blocks new credentials for that capability without revoking existing resources.
- Owner only
- Only the workspace owner can create them.
- Admins and owner
- Workspace admins and the owner can create them.
- All members
- Members other than viewers can create resources they own.
- Scope allowlist
- Limits new and rotated keys to approved API scopes. Write access includes read access for the same resource.
- Ownership
- Members manage resources they created. Admins and owners can manage all workspace developer resources.
Control personal API tokens
Under Developer access, Personal API tokens decides whether personal tokens owned by members may target this workspace. It does not affect workspace API keys. Installed tools follow the same setting.
- Allow
- Members can use their personal tokens and connect installed tools in this workspace.
- Require approval
- An owner or admin must approve each token or installed tool before it works here.
- Deny
- Personal tokens and installed tools cannot access this workspace.
Review personal tokens for this workspace
Personal tokens for this workspace lists each token with its owner and a status of Waiting for approval, Approved, or Revoked. Use the row menu to Approve, Deny, Revoke, or Restore a token. Revoking a token also covers any replacement created by rolling it.
Control personal tool handoffs
Personal tool handoffs lets members connect their own tools and approve task requests. Allow handoffs turns the feature on. Turning it off stops existing handoffs, and turning it on again requires new requests.
Allow unattended handoffs lets members' tools take open handoffs without approval or result review. Turn it on only if you trust everyone in the workspace.