> ## Documentation Index
> Fetch the complete documentation index at: https://docs.inceptia.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Users

> Create users, define what they can access and which bots or queues they are assigned to

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.

> [!NOTE]
>
> 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:

| | Who they are | What they solve |
| - | - | - |
| **Customer Admin** | Someone in **your organization**, with this screen enabled. | User onboarding and offboarding, accesses, assigned bots and queues. |
| **Customer Success** | Your contact at **Inceptia**. | Whatever the platform doesn't let you edit, and each bot's configuration. |

> [!NOTE]
>
> 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.

> [card] 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:

| Option | What it does |
| - | - |
| **Two-factor authentication** | On every sign-in the user is asked for a verification code sent to their email |
| **Sign in with Azure** | They sign in with your organization's corporate account |

> [!WARNING]
>
> **Both cannot be active at the same time.** If you try to save with both switched on, the form won't let
> you.

> [!WARNING]
>
> 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**

| Access | What it enables |
| - | - |
| **Bots** | Create, edit and manage voice or text campaigns |
| **Reports** | View and download campaign reports |
| **AI Agent Designer** | Build and edit their own bots |

**Human Chat permissions**

| Access | What it enables |
| - | - |
| **Agent** | Handle conversations in one or more assigned queues |
| **Supervisor** | See the dashboard and the conversations of the assigned queues |

> [!WARNING]
>
> **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.

> [!TIP]
>
> 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:

| Step | When it shows up |
| - | - |
| **1. User details** | Always. Name, email, language and the accesses |
| **2. Bot assignment** | Only if you chose Bots, Reports or AI Agent Designer |
| **3. Queue assignment** | Only if you chose Agent or Supervisor |
| **4. Summary** | Always. You review everything before confirming |

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.

> [!NOTE]
>
> 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

> [accordion] I gave them the Bots access and they don't see any bot
>
> The access enables the module; bots are assigned separately. Check **Assigned bots** in the user's
> detail.

> [accordion] Can I change a user's email?
>
> 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.

> [accordion] What's the difference between deactivating and removing the accesses?
>
> 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.

> [accordion] The user signs in with the company account — can I reset their password?
>
> No, and you don't need to: that password is managed from the corporate account. The option doesn't
> appear for those users.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.