Update a custom organization role
Rename a custom role in your organization or replace the capabilities it grants.
Authorizations
Runpod API key authentication. Generate an API key in the Runpod console and send it in the Authorization header as Bearer <api_key>. Keys are scoped to the permissions granted when created; requests may return 403 when a valid key lacks access to the requested resource or action.
Console sessions (Clerk JWTs) act for the signed-in user. To act for a team instead, also send X-Team-Id: <team_id>; it applies only when the user owns or belongs to that team, otherwise the request runs against the user's own account. API keys created inside a team already act for that team and do not need the header.
Body
The fields to change; omitted fields are unchanged. capabilities replaces the role's whole grant set rather than adding to it.
Response
OK
- Option 1
- Option 2
A role an organization member or invite can hold: one of Runpod's built-in roles, or a custom role the organization defined.