Skip to main content
The Users screen is where you define who gets into the platform and what they can do once they’re in. Every user has three things: their personal details, their accesses — which modules they see — and their assignments — which bots or queues they work on.
This screen belongs to your organization’s Customer Admin: the person who manages who gets into the platform and what they reach. If you don’t see it in the menu, your user doesn’t have that permission: ask your Customer Admin for it, or Customer Success if your organization doesn’t have one yet.

Who to ask for what

There are two routes, and they aren’t interchangeable:
A Customer Admin can only grant the accesses their own profile has enabled. If they tell you the option doesn’t show up, they aren’t refusing: the request goes on to Customer Success.

The list

It shows your organization’s users. Clicking anywhere on the row opens the detail — you don’t need to look for an edit button. This is also where you create a new user, with Add user.

View and edit a user

The detail opens in a side panel, without leaving the list. It has three blocks, and each one is edited separately: while you’re editing one, the others stay locked, so changes don’t overwrite each other.

Personal details

First name, last name, email and language. The email is also the user’s identifier within the platform.

Reset password

You neither see nor set the password: the user gets an email with the steps to choose one. If the user signs in with their corporate account, the password is managed there and the option doesn’t appear.

How the user signs in

Beyond the details, the user record defines which method they use to get into the platform. These are two switches, and they work one at a time:
Both cannot be active at the same time. If you try to save with both switched on, the form won’t let you.
With Sign in with Azure on, the user is authenticated only against Azure AD: they have no password of their own in the platform and cannot recover one. That’s why Reset password doesn’t appear in that case either.
Both options can be changed later from the user’s detail.

Accesses

Which modules they can use. They split into two families: Bot Manager permissions Human Chat permissions
Agent and Supervisor cannot be combined with each other. A Human Chat user is one or the other: picking one unticks the other.
The two families do combine: the same user can have Bots or Reports and also be an Agent or a Supervisor. In that case the wizard asks for both assignments, the bots and the queues.

Assigned bots and queues

The access says what they can do; the assignment says what on. A user with Bots but no bot assigned gets into the module and sees nothing.
  • Users with Bot Manager accesses have assigned bots.
  • Human Chat users have assigned queues.
In both cases you search them by name and add or remove them from the same panel.

Activate and deactivate

From the bottom of the panel. Deactivating doesn’t delete the user: they can no longer sign in, but they keep their accesses and assignments, and you can activate them again whenever you need to.
Deactivating is what you want when someone leaves the team or is away for a while. The history of what they did is kept.

Create a user

Creating a user goes through a wizard that only shows you the steps that apply, based on the accesses you choose: A Human Chat user, for example, goes from step 1 to step 3 and then to the summary: the bots step isn’t shown, because it doesn’t apply.
You need at least one access to be able to create the user. And if you chose Agent or Supervisor, you need at least one queue.

If something fails while assigning the accesses

The user is created anyway, and you’ll see a notice saying which access couldn’t be assigned. You don’t have to start over: you fix it from the user’s detail. In some cases the accesses take a few minutes to show up.

Frequently asked questions

The access enables the module; bots are assigned separately. Check Assigned bots in the user’s detail.
The email identifies the user in the platform. It isn’t edited from here: if you need to change it, write to Customer Success before doing anything.
Deactivating blocks sign-in and keeps everything. Removing the accesses leaves the user signing into a platform where they can’t do anything. For an offboarding, deactivate.
No, and you don’t need to: that password is managed from the corporate account. The option doesn’t appear for those users.