Help center support eXpress
We've collected answers to popular questions to make eXpress easy and convenient to use. Didn't find the answer to your question? Contact our support team.
- Welcome to eXpress
- eXpress Support
- Introducing eXpress & Glossary
- Installation & Updates & Requirements
- Registering & Logging In
- User Profile
- Chats, Channels & Threads
- Contacts
- Tags & Tabs
- Files
- Calls & Conferences
- Push Notifications & Counters
- Fixing Background Work on Mobile
- Bots & SmartApps
- Diagnostics & Logs & Cache
- Admin Panel
- Admin Panel: General Information
- Users
- Chats
- Open Chats
- Calls
- Conferences
- Profile Change Request List
- Logout List
- Administrators
- Servers
- Bots
- Internal Bots
- External Clients Users
- UI Alerts
- Containers
- Audit
- Stickers
- Call Backgrounds
- Catalog
- Statistics
- Role Model
- Role Model Rules
- User Groups
- Call Reports
- Call Recordings
- Transcribings
- SMS Statuses
- Administrators Authentication
- Audit Settings
- Global Chat
- Global Bots
- Links to Chats/Calls
- Push Service
- File Service
- User Session
- Registration Settings
- Active Directory
- E-mail: self-registration
- OpenID
- Personal Data Visibility
- E-mail: sending emails
- Getting Started Instruction
- Blocked Users
- VoEx
- Server
- Support Info
- Network Security
- Registration Instruction
- SmartApps
- Mobile Menu Configuration
- Activations
- SMS
- Adapters
- Masks
- Security
- CAPTCHA
- Reserved Phone Numbers
- Suggests
- Kerberos Settings & Kerberos Suggests
- Jira Support Portal
- Technical Support for Admins
- Database Modifications Policy
- eXpress Documentation
- Privacy Policy
Server
- Server Settings
- Locale Settings
- Server Features
- Notification During Logging In
- Notification of Technical Works
- Update Notification
- RTS ID, ETS ID, CTS ID
- Certificates
- Admin Info
- Show warning when link clicked
- Message Forwarding in Confidential Mode
- Service Versions
Server Settings 
The following settings are available in this group:
| Parameter | Description |
|---|---|
| Server avatar | You can upload an image for server avatar (displayed in the client app under Settings > About). Image compression will happen automatically. |
| Chat backgrounds | You can upload background images for chats (wallpapers) displayed to server users in light and dark themes.
?? Wallpapers must not exceed 50 KB in size, and the image must be square (600?600 pixels). |
| Hide server name |
CTS
eCTS
Corporate server instead of the address. |
Locale Settings 
Allows you to enable additional localization languages for emails and HTML uploaded to the server, in addition to English. This setting is available starting with version 3.57 (server) and 3.60 (clients).
Server Features 
Configure the features available on the server:
| Parameter | Description |
|---|---|
| Show corporate users catalog | Enables displaying all CTS /eCTS users in the contacts list.
?? Not recommended for organizations with more than 500 users (risk of performance degradation on client devices).
For this setting change to take effect on user devices, you'll also need to toggle Disable corporate phonebook on and off, saving changes in between, and restart client apps. |
| Corporate search | Contacts search on the current server, also including additional user fields (role, department, etc.). |
| Trust search | Contacts search on the trusted servers (the trust search should be allowed on a trust server).
After enabling this setting, it does not take effect immediately; you need to wait some time.
|
| Enable e2e encryption by default in group chats | Determines whether end-to-end encryption is activated by default when creating a group chat. |
| Enable e2e encryption by default in channels | Determines whether end-to-end encryption is activated by default when creating a channel. |
| Disable corporate phonebook | Disables the corporate contacts service (phonebook) and any kind of searching for contacts completely. It blocks loading and searching for contacts when enabled, regardless other settings. |
| Allow the user to control their avatar | Users can upload new avatars when editing their corporate profile. Requires server software and client version 3.33 or higher. If disabled, user avatars will be replaced with those manually set by the administrator or synced from the corporate directory. |
| Moderate user's requests for profile changes | Avatar change requests will require administrator approval in the “Profile Change Request List” section. Requires server software and client version 3.33 or higher. |
| Activate notifications for outdated server version | When enabled, the current server version is compared periodically with the latest version of RTS . If the version on the current server is outdated, the warning "A new version X.XX is available. Please contact your provider." will be displayed. The feature introduced in 3.53. |
| Display three letters of the user's initials in the avatar instead of two | When enabled, placeholder avatars will contain three letters if the user's full name consists of three separate words (surname, first name, patronymic). Available starting from version 3.55. |
| Enable rate limiter for BotX | Enable a limit of 15 edit_event requests per 10 seconds. This resolves the issue of excessive load on the server software from bots sending such requests too frequently. Available starting from version 3.66. |
How to Configure Contacts and Search Settings?
| Show directory |
Corporate search |
Trust search |
Disable phonebook |
Result |
|---|---|---|---|---|
| On | Off | Off | Off | Corporate contacts directory is loaded. Local search only by full name in device contacts. |
| On | On | Off | Off | Corporate contacts directory is loaded. Full corporate search via CTS /eCTS , including additional fields. |
| On | On | On | Off | Corporate contacts directory is loaded. Search works on CTS /eCTS + trust servers. |
| Off | On | Off | Off | Corporate contacts directory is not loaded, shows contacts from synced phonebook. CTS /eCTS search works. |
| Off | Off | On | Off | Corporate contacts directory is not loaded, shows contacts from synced phonebook. Only trust search works. |
| Off | On | On | Off | Corporate contacts directory is not loaded, shows contacts from synced phonebook. Search works on CTS /eCTS + trust servers. |
| Off | Off | Off | Off | Corporate contacts directory is not loaded, shows contacts from synced phonebook. CTS /eCTS + trust servers search doesn't work. |
| Any | Any | Any | On | Any contacts disabled. Search disabled |
-
?Related Topics:
- Display All Corporate Contacts in the List
- Avatar, Name, and Other Profile Data
- Profile Change Request List
Notification During Logging In 
Configure the custom agreement text displayed before logging into the server.
In What Order Should the User Agreement Be Configured?
- Attach the agreement file to all localization fields — the file must be uploaded for each locale.
- Click Save.
- Select the Show the user when logging in checkbox.
- Click Save again.
Why Is the Agreement Hard to Read in Dark Theme?
Starting with server version 3.70, the agreement file is loaded separately for light and dark themes. If there is no file for the required theme, the app displays the file for the other theme. If the agreement is laid out for the light theme, in dark theme on Android its dark text blends with the dark background.
Apps for Android and iOS starting from version 3.71 request the file for their own theme. The web app currently always displays the file for the light theme.
How to Lay Out the Agreement so It Looks the Same on All Platforms?
On the sign-in screen in the iOS app, the agreement is displayed in a simplified form: lists without bullets, the same font size for headings and body text, blank lines before tables, and the text color is set by the app. After signing in, on Android, in the web app, and in the desktop app, the agreement is displayed as a web page. To make the text look the same everywhere:
- Write text in paragraphs
<p>, and subheadings as a bold paragraph<p><b>1. General Provisions</b></p>. - Write enumerations as lines within a single paragraph:
<p>• first item;<br>• second item.</p>. List bullets from<ul>and<ol>are not visible on the iOS sign-in screen. - Write terms and deadlines as paragraphs
<p><b>Operator</b> — definition.</p>instead of tables. On the iOS sign-in screen, blank space appears before a table, and in a narrow column words break letter by letter. - Do not leave empty paragraphs
<p><br></p>: on the iOS sign-in screen, each one produces a blank line. - Set the font on
<body>or a wrapper:style="font-family: -apple-system, system-ui, Roboto, 'Segoe UI', Arial, sans-serif;". Without it, the web app and iOS after signing in display text in a serif font. - Upload files for both themes. In each one, set the background and text color using the
styleattribute: in the file for the dark theme, for example,<body style="background-color: #1E1E1E; color: #E6E6E6;">. - ⚠️ On the iOS sign-in screen, the background is taken from the file, but the text color is set by the app: black in the light theme, white in the dark theme. If there is no file for the dark theme, iOS will display the file for the light theme, and white text on a light background will not be visible.
- Do not add
<title>: the server removes the tag, and its text ends up at the beginning of the agreement.
What Are the HTML Requirements?
See HTML requirements in the “Support contacts” section.
Notification of Technical Works 
If enabled or upon a 502 error in the response to the settings request from the client side, users will see the message “Maintenance is underway, there may be interruptions in the work of the application.
I Toggled the Notification, but Nothing Changed on the Clients. Why?
This notification appears or disappears only when the client app is restarted, the local app cache is cleared, or the app reconnects to the server.Update Notification 
If the client app version lags behind the server software by the specified number of minor versions (x.X.x) or above it, the user will receive a notification prompting them to update. For example, if the server software is version 3.65 and a lag of 3 versions is configured, users with client versions 3.62 and lower will be prompted to update the app.
Can This Feature Be Used to Manage Client App Updates?
This is just an additional informing, it does not affect automatic updates via app stores or update checks in the web/desktop app.
How to Enable Informing about Updates?
- Check the Notify about an existing update box and specify the allowable lag of client app versions behind the server software.
- To enforce updates, enable Block application interface until update is started (available with server software version 3.32).
- Select the client platforms where the feature will work.
The ETS App Has Not Been Released Yet, but Users Are Prompted to Update. Why?
?? If new server software is installed but clients are not yet released in stores, users will receive a notification about a non-existent client update, since the feature compares the server version with the client version. We recommend setting the lag to at least 3.
Do Update Notifications Work for the Mobile Branded ETS App?
Yes. Existing app store links are embedded into branded mobile app builds.Why Didn't the Desktop App Receive a Notification That It's Time to Update?
The feature works for desktop apps only with automatic update functionality support enabled — more details.
The Android App Was Installed Not From a Store but From an APK Package. Will the Feature Work?
Yes. If the Android OS does not have information about the store from which the app was installed, the update notification will still appear and provide the user with a choice of installation source.RTS ID, ETS ID, CTS ID 
Displays the ID of upper Certificates 
Upload certificates to the server. Details are available in the administrator documentation.
Admin Info 
Specify the administrator’s contact details — they will be displayed to the user when contacting support or encountering an error.
Show warning when link clicked 
Here you can configure the display of a warning dialog when following any links. The feature is available from version 3.42.
Message Forwarding in Confidential Mode 
Introduced in the version 3.44. When Allow users to configure message forwarding in confidential mode is enabled, users will see a new setting in their confidential mode options that permits forwarding messages from chats with the confidential mode active to other chats.
Service Versions 
Displays the versions of the server services.
You can also check the version via the link: https://the_server_FQDN/system/XX/version, where XX is the service name (trusts, messaging, voex, etc.).