Skip to main content

Update a User

PATCH 

/rise/Users/:id

Supported paths: active, roles — only these produce observable changes. Operations on non-persisted attributes (displayName, externalId) return a silent 200 no-op; an operation changing userName fails the whole request with 400 invalidValue (including any other operations batched in it); unknown or miscased paths (e.g. Roles) fail 400 invalidPath. Send active changes and roles changes as separate PATCH requests — combined in one request, the deactivation wins and the role change is silently discarded (the 200 response echoes the old roles). Email addresses (userName) are immutable post-creation — to change a user's email, delete and re-create. Setting active to false removes the user from RSC (deletion). Reactivation by active: true is not supported — re-create the user via POST. PATCHing active: true against a previously-deleted RSC user returns 404 (detail Resource: <id> wasn't found), not a friendly "not supported" message. Azure AD add operations on the roles path are automatically rewritten to replace for Entra ID compatibility.

Request​

Responses​

User updated