Admin
Translate the Aysali Bot admin area (dashboard, conversations, settings labels, and system strings) so agents can work in their preferred language.
The help link on Settings → Admin → Automatically translate admin area points here.
Step 1 — Add your translations
Before changing how the admin language is selected, translate the strings you need:
- Open Settings → Translations in the admin panel.
- Translate texts into your language (or click New translation to add entries).
- Enter the English source text in the first field (original text must be in English). Use
\nfor line breaks. - Enter the translation in the second field.
You can translate custom content such as rich messages, built-in messages, departments, chat header text, and more. If Artificial Intelligence is enabled, you can also use multilingual via translation to generate translations automatically from the Translations area.
Add a new language file
To register a new front/admin language code:
- On the server, go to
resources/languages/frontinside your bot installation. - Duplicate
source.jsonin the same folder. - Rename the copy to the ISO 639-1 language code (two letters, e.g.
ar,es). - Open Settings → Translations — the new language should appear.
Step 2 — Set the admin area language
You have three options for which language the admin UI uses:
Option 1 — Automatically translate admin area (recommended)
Enable Settings → Admin → Automatically translate admin area.
When this is on, the admin area language is resolved in this order:
- Agent profile language — if the agent has a language set on their user profile
- Browser language — otherwise the agent’s browser language is used
This option does not require editing server files and works on hosted Aysali Bot workspaces.
Option 2 — Force a fixed language in config.php
For self-hosted installations, you can force one admin language for all agents:
- Edit
config.phpin your bot installation directory (on Aysali, this is the tenantconfig.phpprovisioned for your workspace — change only if your deployment allows it). - Add at the end of the file:
define('SB_ADMIN_LANG', 'ar');
Replace ar with a two-letter language code (e.g. es, not es_ES). When SB_ADMIN_LANG is defined, it overrides automatic detection.
Option 3 — Agent profile language only
Leave Automatically translate admin area off, and set each agent’s Language on their user profile (in the Users area). The admin UI uses the profile language when present; otherwise it falls back to English (or your cloud default language code if configured).
Combine with Settings → Translations so strings exist for that language.
Related admin settings
| Setting | Description |
|---|---|
| Automatically translate admin area | Match admin UI to profile or browser language (Option 1) |
| Do not translate settings area | Keep the Settings screens in the default language even when the rest of the admin is translated |
Chat widget language (separate)
Visitor-facing chat language is configured separately under Settings → Chat → Language (Default, Multilingual, or a fixed language). Admin language settings do not change the website widget language.