Skip to content
First requestVisit website ↗
Navigation

Atomically replace a staff MCP key's workspace grants

Platform admins may assign read grants; write grants and any replacement on a global-write key require a platform owner. Replacement is transactional; failure preserves the previous grants and read overrides. Requires the atomic-grant migration; no non-atomic fallback.

PUT
https://api.channelautomation.com/api/admin/mcp-permissions/keys/{keyId}/workspaces

Authorization

  • BearerAuth
    HTTP Bearer (JWT)
    required

Path parameters

  • keyId
    string
    required
    format: uuid

Request body JSON required

  • permissions
    array of
    object
    required
    • workspaceId
      string
      required
    • role
      read
      or
      write
      required

Returns

200

Entire grant set replaced

400

Invalid permission set

401

Invalid session

403

Insufficient platform role

404

Key not found

500

Replacement failed; previous grants retained

Type to search…

↑↓ navigate↵ selectEsc close