Update RBAC Role
Edit a role's name, description, priority, permissions, or default-assignment flag. Changes take effect on the next request from any client holding this role.
Be careful with permission changes — narrowing permissions is felt by everyone with the role. To stage the change, create a new role with the new permissions, migrate clients over, then delete the old one.
Path parameters
uuid from /endpoints.uuid from /rbac/roles. Resolved under this endpoint only.Deprecated: the legacy integer id is still accepted in the path until the sunset, answered with Deprecation and Sunset headers. Use the uuid.
Request body
Same fields as create. name is required. Omitting priority or is_default keeps the existing value; sending an empty/zeroed permissions object keeps the existing permissions (it is not cleared).
Response (200 OK)
The updated role (same shape as list entries).
Deprecated: until the sunset this response also carries the legacy integer id and *_id fields. Don't use them; read uuid and the *_uuid fields.
Errors
name, invalid JSON, or a duplicate role name (surfaced as an update failure, not a dedicated 409). An integer role id after the sunset (integer_id_unsupported).endpoints:update permission in the active account.role not found).