Server

This section contains parameters and settings for the current server.

Server Settings

The following settings are available in this group:

Parameter	Description
Avatar	You can upload an image for the server avatar. The avatar is displayed in the client application in the Settings > About section. The image is compressed automatically. ⚠️ The image must be square, 500×500 pixels, no larger than 60 KB. Use PNG: it compresses without quality loss.
Mobile background, Mobile dark background, Web background, Web dark background, Web high resolution background, Web dark high resolution background	Background images for chats (wallpapers) in light and dark themes, separately for mobile applications and for the web and desktop application. The Clear button above the field deletes the uploaded background. ⚠️ Wallpaper size — no more than 50 KB. The image must be square, 600×600 pixels.
Hide server name	CTS eCTS If enabled, the server name and address are not displayed to external users. For your own and trusted servers, the server name is always visible. In the user card, external users will see Corporate server instead of the address.

Locale Settings

Here you can enable additional localization languages for e-mails and HTML uploaded to the server, in addition to English: ru, de, es, fr, ar, mv, tr, uz, in, kk. English (en) is always enabled and is used by default. 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	Displays all CTS / eCTS users in the contact list. ⚠️ In organizations with more than 500 users, don't enable this setting: performance may decrease on client devices. For the changes to this setting to take effect on users' devices, turn Disable corporate phonebook on and then off. Save changes after each toggle. Then restart the client applications.
Corporate search	Contacts search on the current server, also including additional user fields (role, department, etc.).
Trust search	Search for contacts on trusted servers. Works if the trusted server has allowed trust search. The setting starts working some time after being enabled.
Enable e2e encryption by default in group chats	Determines whether end-to-end encryption is enabled by default when a group chat is created. The check box is selected by default.
Enable e2e encryption by default in channels	Determines whether end-to-end encryption is enabled by default when a channel is created. The check box is cleared by default.
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	Limits the rate of bot requests to BotX: no more than 30 requests per 10 seconds. If a bot exceeds the limit 5 times, its requests are rejected for 5 minutes. This way, bots that send requests too frequently do not overload the server software. 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

---

Notification During Logging In

Configure the custom agreement text displayed before logging into the server.

In What Order Should the User Agreement Be Configured?

1. Attach the agreement file in the field for each localization.
2. Click Save.
3. Select the Show the user when logging in checkbox.
4. 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 style attribute: 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

Users will see the text from the Under maintenance alert, ru and Under maintenance alert, en fields in the application settings. The Set default alert text button restores the text “Maintenance is underway, there may be interruptions in the work of the application”. The notification appears if it is enabled or if the client's request to settings returns error 502.

I Toggled the Notification, but Nothing Changed on the Clients. Why?

The client app shows or removes the notification only in three cases: after a restart, after the local cache is cleared, and after reconnecting 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 more, the user will receive a notification prompting them to update. For example, if the server software version is 3.65 and the lag is set to 3 versions, users with client versions 3.62 and lower will receive a notification.

Can This Feature Be Used to Manage Client App Updates?

The feature only notifies about an update. It does not affect automatic updates through app stores or update checks in the web/desktop app.

How Do I Enable Update Notifications?

1. Check the Notify about an existing update box and specify the allowable lag of client app versions behind the server software.
2. To enforce updates, enable Block application interface until update is started (available with server software version 3.32).
3. Select the client platforms where the feature will work.

The ETS App Has Not Been Released Yet, but Users Are Prompted to Update. Why?

⚠️ The feature compares the server version with the client version. If a new version of the server software is installed but the clients have not yet been released in the stores, users will receive a notification about a non-existent update. Specify a lag of 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 only in desktop apps that support automatic updates — 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 prompt the user to choose an installation source.

RTS ID, ETS ID, CTS ID

The section shows the current server ID and the ID of the / above it.

Certificates

Here you can upload certificates to the server. Details are available in the administrator documentation.

Corporate Certificates

Here you enable checking of the device's corporate status using the company client certificate. The check result is used in role model user groups. By default, checking is off.

Field	What to enter
Upgrade corporate role host	The address of the organization's web proxy that the app accesses to check the certificate.
Web-proxy header	The header in which the web proxy sends the device certificate to the server.
Upgrade corporate role callback scheme	The address scheme by which the iOS app returns from the browser after verification.

When the Enabled checkbox is selected, all three fields are required. The organization needs its own certificate authority, certificates on users' devices, and a separate web proxy. One certificate is confirmed only on one device.

Admin Info

Specify the administrator's contact details. The user will see them when they contact support or when an error occurs.

Show warning when link clicked

Here you can customize when to show a warning dialog box when following a link: Enabled for all links, Enabled only for markdown links, or Disabled. A Markdown link is a link hidden under text. A link that is displayed as an address opens without a warning in the second option. By default, Enabled only for markdown links is selected. The feature is available since version 3.42.

Message Forwarding in Confidential Mode

When Allow users to configure message forwarding in confidential mode is enabled, users in confidential mode will have a forwarding setting. It allows forwarding messages from a chat with confidential mode enabled to other chats. Introduced in the version 3.44.

Service Versions

Displays the versions of the server services.