Update a member's role and/or activation status.
PATCH /v1/organizations/members/{user_id}
Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”The UUID of the member to update
Request Body required
Section titled “Request Body required ”object
Set to true to reactivate a deactivated user.
Absent means “don’t change activation status”.
false is rejected — use DELETE to deactivate.
Names of the roles to assign (e.g. [“admin”], [“editor”, “viewer”]). Absent means “don’t change roles”.
Responses
Section titled “ Responses ”Member updated
object
Relative path to the user’s avatar endpoint, e.g.
"users/{id}/avatar?v={hash}". None when the user has no avatar.
Kind of principal an OrganizationMember represents. Always HUMAN on the
/v1/users endpoint today; included on the wire so frontend consumers have
a single discriminator regardless of which endpoint surfaced the row.
Wire format is SCREAMING_SNAKE_CASE so these read as constants (HUMAN,
SERVICE_ACCOUNT); the DB-side organization_user_kind enum stores the
snake_case form ('human', 'service_account') and gets translated by
the From<OrganizationUserKind> impl below.
Invalid request
Forbidden - insufficient permissions
User not found in organization