Breaking (pre-GA contract correction, see API versioning)
POST /api/v2/users in workspaces where people manage their own profile
(is_profile_self_managed: true) invites by email: firstname, lastname and phone_number
must be omitted and are rejected with 422 users/profile-self-managed. The new user has
profile_status: PENDING and no name until the person's first sign-in. See
User.
PATCH /api/v2/users/{user_id} in those workspaces: changing another user's firstname,
lastname or phone_number is rejected with 422 users/profile-self-managed (data.user_id,
data.fields); it used to succeed. Sending the stored values back is still accepted. The user's
own change and every change in other workspaces are written to the sign-in service first, so
the operation can now answer 503 upstream-service-unavailable; retry later.
POST /api/v2/users in other workspaces: a missing or nullfirstname/lastname is now a
field-required entry for each missing name (was one field-type-invalid entry for the first),
reported after the other field errors are fixed. Blank names and everything else are unchanged.
firstname and lastname on POST/PATCH /api/v2/users, on the signup account details and
on admin tenant onboarding reject the characters the sign-in service refuses
(< > & " $ % ! # ? § ; * ~ / \ | ^ = [ ] { } ( ) and control characters) with
422 validation-failed; before, such a name failed later in the sign-in service.
User carries the required is_profile_self_managed (boolean). TenantUser (admin) and the
user.* webhook payload no longer require first_name/last_name; they are absent while
profile_status is PENDING.
can_resend_set_password_email is true in self-managed workspaces only while the invitation is
pending (profile_status: PENDING); elsewhere it still means the user never signed in.
A user who is deactivated in a workspace gets 403 user-deactivated (with data.tenant_id) on
every request to it, also with a token issued before the deactivation, which used to keep
working until it expired. Where people share one login across workspaces, the deactivation no
longer disables that login, so their other workspaces stay available. Do not refresh or sign in
again on this response; a workspace administrator has to activate the user. See
Authentication.
Improvements
User, admin TenantUser and the user.* webhook payload carry profile_status
(PENDING, COMPLETE); names are absent while PENDING.