Learn how to use Single Sign-On (SSO) to authenticate agents and admin users to the Digital Agent Desk.
Attribute Name | Required | Description | Example |
---|---|---|---|
userId | yes | user’s unique identifier used for authentication. Can be a unique readable value such as user’s email or an opaque identifier such as a customer’s internal user ID. | jdoe@company.com |
firstName | yes | user’s first name | John |
lastName | yes | user’s last name | Doe |
nameAlias | yes | user’s display name. Allows an agent, based on their personal preference or company’s privacy policy, to set an alias to show to the customers they are chatting with. If this is not sent then the agent firstName will be displayed. | John Doe |
roles | yes | the roles the user has within the ASAPP platform. Typically mapped to one or more AD Security Groups on the IDP. | representative|manager |
Attribute Name | Required | Description | Example |
---|---|---|---|
groups | no | group(s) the user belongs to. This attribute controls the queue(s) that a user is assigned to. Not to be confused with the AD Security Groups (see the roles attribute above) | residential|business |
concurrency | no | number of concurrent chats the user can handle | 5 |