API keys and MCP clients follow the creator’s role
Roles are now on for every workspace. An API key acts as the person who created it, and an MCP client acts as the person who connected it, so both hold that person’s role. Scopes still apply: a call needs the scope on the key or connection, and the creator’s role must include the permission the endpoint needs. When the role lacks it, the call answers HTTP403:restriction says which permission is missing; the tables below map each value to its name in Settings → Roles.
An MCP tool fails with an error that carries the same 403 status and body.New refusals
These checks came with Roles: either the permission is new, or the endpoint did not check it before. A workspace applies them only while Roles is on, which is now every workspace.Publishing checks the steps that the publish sets up: a step it adds, or the steps of a graph it gives an automatic
trigger for the first time. Running checks every step of the published version. When
POST /v1/workflows with
publish: true is refused, the workflow is still created as a draft, and the 403 body carries status,
message and details.workflowId instead of restriction.A creator whose role lacks Manage teammates’ work reaches only the workflows they created or that are shared
with them. The workflow endpoints answer 404 for the others, and GET /v1/workflows leaves them out.Workflow steps
Refusals that already existed
These checks applied before Roles as per-member restrictions. A role now decides them, so a creator can lose one when an admin changes their role.The MCP tools built from these endpoints are refused the same way.
Fix a refusal
- A workspace admin gives the creator a role that includes the permission, in Settings → Roles.
- Or someone whose role includes the permission creates the API key, or connects the MCP client.