Required Role: Admin Portal or Admin API Consumer
Update one or more properties of a user. The user can be identified by their user ID
or email address.
Agent Self-Edit Restrictions
When an agent edits their own profile (self-edit), the server enforces the following:
Read-only identity fields:
The following fields are always read-only for agents and cannot be modified via self-edit.
Any attempt returns 403 Forbidden:
firstName, lastName, namePrefix, nameSuffix, title, email, mobile.
These fields can only be changed by an administrator.
Auto Answer / WebHID Edit Restrictions:
- If
allowAgentEditAutoAnswerisfalseon the user record and the request includes
a change toattributes.webRTC.autoAnswer.interaction, the server returns 403 Forbidden. - If
allowAgentEditWebHIDHeadsetControlisfalseon the user record and the request
includes a change toattributes.webHID.status, the server returns 403 Forbidden. - Administrators editing other users are never restricted by these flags.
- Agents can still modify unrestricted fields (language, timezone, app theme, queues, etc.)
even when identity and Auto Answer / WebHID edits are restricted.
Agent Self-Edit Restrictions
When an agent edits their own profile (self-edit), the server enforces the following:
Read-only identity fields:
The following fields are always read-only for agents and cannot be modified via self-edit.
Any attempt returns 403 Forbidden:
firstName, lastName, namePrefix, nameSuffix, title, email, mobile.
These fields can only be changed by an administrator.
Auto Answer / WebHID Edit Restrictions:
- If
allowAgentEditAutoAnswerisfalseon the user record and the request includes
a change toattributes.webRTC.autoAnswer.interaction, the server returns 403 Forbidden. - If
allowAgentEditWebHIDHeadsetControlisfalseon the user record and the request
includes a change toattributes.webHID.status, the server returns 403 Forbidden. - Administrators editing other users are never restricted by these flags.
- Agents can still modify unrestricted fields (language, timezone, app theme, queues, etc.)
even when identity and Auto Answer / WebHID edits are restricted.
Disabling a User
A user can be disabled by performing an update to set the status property to disabled.
This can normally only be done if:
- the user is not logged in
- the user has no active interactions
- the user has no pending interactions in their personal queue
and a request to do so in any of those conditions will fail with a 422 error. This can be
overridden by setting theforceDisablequery parameter.
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
