Users

This section contains a list of users and bots on a server.

Can I View the Number of Licenses Currently Used by Users?

You can see how many users are registered (export the user list to CSV). There is no dedicated tool that shows purchased licenses. For information about purchased licenses, contact your account manager at eXpress (more details).

Searching for Users

In the search field on /, you can search for users by HUID, name, email, domain, and position as specified in their corporate account.
On and , you can search for users by name, phone number, as provided by the user during initial registration or later in profile settings in eXpress.

Creating Users

You can manually create a new user on the corporate server by clicking the corresponding button or set up the automatic synchronization.

How to Bulk Create Users Manually?

Use the Load from CSV button.

Migrating From Manual to Synced Accounts?

If you recently configured synchronization, delete old manual accounts with duplicate emails to avoid conflicts with new synced accounts.

What Authentication Methods Are Available for Manually Created Users?

Such a user will only be able to log in via email. To use other methods when synchronizing with a corporate directory (e.g., Active Directory), create users in the directory, not manually on the corporate server!

Can User Synchronization and Manual Creation Be Used Simultaneously?

Yes. This allows you to, for example, sync organization employees from a directory while manually adding external contractors. This only works with Email authentication — both manually created and synced users will log in using email codes.

How to Connect Users Not Listed in the Corporate Directory?

To connect external users (partners, contractors) who are not in the organization's directory to the corporate server:

1. Create profiles for external users in the Users section manually.
2. In the “Registration Settings” section, switch the authentication method to Email.

This way, both external users and those synchronized from the directory will log into their corporate account via an email code.

Is an Email Required for Syncing a User with AD/OpenID?

When authenticating with an AD login and password (the NTLM method) or with the OpenID method, the user won't need to enter an email, so syncing this field is optional. However, if you plan to use simplified authentication suggests or email-based login confirmation (the Email method), the email field must also be synced to user profiles.

How to Properly Pass Credentials to Users?

When providing corporate data, always inform users:

• To log into the app with their phone number if they have previously used it.
• A phone number can be added later, but only if there is no account already linked to it.

This preserves their chat history if they previously used a phone number, as well as when changing logins or switching to another server.

Managing User Profiles

Action	Manually created User	Synchronized User
Editing	Click the pencil button on a user in the list to edit their data.	To modify a synced user's data, edit them in the directory and perform synchronization.
Blocking	You cannot block a user through the admin panel.	Blocking via AD/OpenID is supported.
Deleting	To delete a user: Initiate and confirm their logout Click the trash button	To delete a synced user: log them out, remove their sync group in AD or role in OpenID, then synchronize — the profile will disappear from the list. ⚠️ To automatically delete OpenID accounts after logout, you need to enable the corresponding setting in advance in the OpenID section.

Which Users Can Be Edited or Deleted Manually in the Admin Panel?

You can only modify or delete users who were created manually or via self-registration with an email mask (logout is also required before deletion).

How to Change User Login Properly?

Refer to this guide.

I Blocked a User in the Directory, but They Did Not Leave the Server. Why?

In addition to blocking in the corporate directory, you also need to confirm the logout request for the user so they are no longer bound to the corporate server, or configure automatic logout.

Exporting the User List

The Download as .CSV button downloads the user list in CSV format. This list can later be imported into a group chat or channel for bulk user additions. To filter the exported list, use the search function. When clicking the button, you will be prompted to select user types for export:

User type	Description
cts_user	Registered active corporate users.
unregistered	Unregistered inactive users.
botx	Bots and Smart Apps.

User Profile

Clicking on a user opens their profile information:

Field	Description
HUID	The user’s unique identifier. ⚠️ The HUID displayed in the CTS admin panel before the user's first login is temporary. Only enter the corporate account's HUID into external systems after the employee has performed their first login to the app.
Company details, position, etc.	CTS eCTS Filled manually by the administrator or synchronized automatically.
RTS ID/ETS ID/CTS ID	the registration server ID. To determine the specific server address, find this ID in the “Servers” section.
Type of the profile	botx ( CTS / eCTS , ETS , RTS ) — bot (Smart App) account cts_user ( CTS / eCTS ) — active corporate account external_client ( CTS / eCTS ) — external client app account guest ( CTS / eCTS , and on RTS ) — guest account unregistered ( ETS , RTS ) — inactive account user ( ETS , RTS ) — personal account not linked to a corporate server
Avatar source	Introduced in version 3.67. custom — user uploaded an avatar in the client sync — avatar synchronized from AD/OpenID
Source	admin — user created in the administrator panel email — user created via email self-registration ad/openid — user created during synchronization with the corresponding system
Registration type	default — phone number registration cts_only — registration without a phone number
AD groups	CTS eCTS Displayed for users synchronized from Active Directory.
Dates of account creation, update, or deletion	Updated upon server login or synchronization

Profile Buttons

At the top, there are buttons to manage the user or view additional information.

Button	Description
Activations	Active and completed sessions: Each session is identified by UDID Contains device information, software versions, and locks information Displays permissions (Device Meta): permissions.microphone — microphone access permissions.notifications — browser/OS notifications pushes — in-app notifications permissions.contacts — contact access permissions.storage — storage access Available actions for activations: Clean chats/Clean contacts — forced cache clearance with subsequent server reload Clean all — clears chats/contacts and ends the session Delete ( RTS / ETS only) — clears cache, ends the session, and removes the activation record
Blocks	CTS eCTS List of account blocks in Active Directory and their reasons.
Keys	User's public encryption keys: Corporate users have a cts key for message encryption (paired with rts key); Public users have an rts key for message encryption (paired with cts key for public users registered in early app versions); ed25519 - session key for message signing. There may be multiple keys, distinguished by version and date/time.
Chats	RTS CTS eCTS List of all user's chats.
Recovering keys in chats	Fixes encryption key issues in chats (details). “Error restoring keys in chats. Reason: already_in_progress” — user key restoration is queued, please wait for approximately 30 minutes.
Clean cache	Clears local chat/contact cache on all user devices.
Clean all	Deletes cache and forces a return to the login screen on all user devices.
Logout	CTS eCTS Sends a request for logout from the corporate server (requires administrator confirmation in the “Logout Requests” section).

What Happens When Users Get New Keys?

New keys (cts/rts for corporate / users or rts for public users) are generated when:

• Resetting the personal encryption password.
• After account deletion and re-registration.

The ed25519 session signing keys are generated when users start a new device session.

After logout, key synchronization between servers is forced upon re-login.