Everyone who can sign in to this tenant, listed with their name, email, phone,
status, whether they are active, and their role.
Adding someone
New User asks for four things:
There is no password field. You are not creating credentials for someone else:
the account is created and the person sets their own password through an
activation link sent to the address you entered.
This is deliberate and worth preserving as a habit. A password you typed is a
password you know, and an account whose owner cannot honestly say only they
could have used it is not much of an account.
Status and active
The list shows two separate columns, and they mean different things.
Status tracks the account’s lifecycle — whether the invitation has been
accepted and the account completed.
Active is the switch you control. Turning it off blocks sign-in while
keeping the account, its role, and everything it has done. That is what you want
when someone leaves or goes on extended leave: deleting the user would take their
history with them.
One role each
A user has exactly one role. There is no way to combine two, and no per-user
exception to a role’s permissions.
That constraint is what makes access reviewable: to know what someone can do you
look at one role, not at a role plus a list of adjustments. When somebody needs a
combination that no existing role covers, create the role — see
Roles and permissions.
Editing
Edit on a row changes the same fields, including the role. Changing a role
takes effect on the person’s next request; they do not need to sign in again.
When the platform’s support team helps you, they enter your tenant as one shared
account marked Platform support in the list. Nobody can edit, deactivate or
delete it, and it does not count towards your user limit.
Every such visit is recorded. In the new admin interface, Support access,
next to Users in the menu, lists who from support entered, their email and IP,
and when they entered and left — newest first, and read only. It is open to anyone who can manage users.
Limit notices
When a limit of the account (assistants, flows, channels, staff, active contacts, outgoing messages,
calls or media storage) turns work away, every active administrator gets a notification and an email
saying which limit it is, how much is used, what was turned away and who to ask for more. For limits
on how many things can exist, the same notice comes when the last free place is taken.
The email is written in the language the administrator last chose in the console. Until they choose one, it is the language they first signed in with; later sign-ins do not change it.
Each limit is announced once per billing period, or, for limits on how many things can exist and on
stored media, once for each limit value with a reminder every seven days while work keeps being turned
away. Other roles do not get these notices.