Update an existing role's fields

PATCH 
/roles/:roleId

Updates the role identified by roleId under the tenant specified by the required tenant-id header. Use this to change a role's name or description after creation; to create a new role use POST /roles. This is a full replacement, not a partial merge: any field omitted from the request body (name or description) is cleared on the role rather than left unchanged, so callers must resend the current value for any field they do not intend to change. Returns 200 with the full updated role object (RoleResponseDto). Returns 400 if the tenant-id header is absent or blank. Note: if the role does not exist, the current implementation returns 500 rather than 404 (tracked in CP-36405).

Request

Responses

200

Role updated successfully

400

Bad request - Invalid request parameters or missing required headers

401

Authentication required - Valid authentication token is missing or invalid

403

Forbidden - User does not have the required permissions to update roles

500

Internal server error - An unexpected error occurred while processing the request. No response body is returned. Note: a non-existent role ID currently also surfaces here as a 500 rather than a 404, since not-found conditions are not distinguished from other failures (tracked in CP-36405).