Skip to main content
PATCH
Change a member's role
A signed-in human administrator is required. API keys and MCP credentials cannot replace that session. Sensitive operations can also require recent authentication. Changes the current role while protecting the last active administrator. A role change revokes that human’s MCP grants. Request conventions · API keys · MCP connections

Authorizations

posted_session
string
cookie
required

Signed-in human browser session; mutation requests also need the exact UI Origin

Headers

Origin
string<uri>
required

The exact configured Posted UI origin. Required for browser mutations carrying session cookies.

Path Parameters

id
string<uuid>
required

The id from the corresponding list, record or authorization response.

Body

application/json
role
enum<string>
required
Available options:
admin,
member,
viewer

Response

Successful response. Examples are illustrative; field values vary by record.

member
object