How to set up multiple store views and languages
A store that sells in several languages usually wants the chatbot to answer in each of them, from that language's own content. The AI Chatbot - eChat extension supports this with one eChat workspace per Magento store view: each workspace has its own knowledge base, its own widget settings and greeting texts, and its own conversation history, while all of them stay grouped under a single eChat account.
By default a store view does not have its own workspace - it inherits the global one, and the eChat configuration screen says so. The steps below give a store view its own.
1. Decide which store views need their own workspace
Give a store view its own workspace when it should:
- answer in a different language,
- answer from a different catalog or knowledge base - a different website, a different set of CMS pages,
- or use different greeting texts, appearance or behavior.
Store views that should behave identically can keep inheriting the global workspace. Each workspace is configured and synced on its own, so fewer of them means less to set up and one knowledge base to keep current.
2. Switch the configuration scope to that store view
In the Magento admin, use the scope switcher in the top-left corner of Stores > Configuration to select the store view, then open Mirasvit Extensions > eChat.
While the store view is inheriting, the Account panel shows Using global account: with the global workspace's Instance ID.
3. Give the store view its own workspace
Click Switch to Separate Account, then Connect with eChat on the Connect tab. This opens the eChat consent screen in a new browser tab, exactly as it did for the first connection, and creates a workspace for this store view.
Switch to Separate Account creates another eChat workspace for this store view - it does not ask you to open another OpenAI, Anthropic, Google or xAI account.
It does mean a separate set of settings. Each workspace is its own eChat instance: nothing is copied from the global workspace and nothing is inherited afterwards, so the AI provider and model, greeting texts, guidance and appearance are configured in each workspace of its own. Plan for that before splitting a store view off.
If you want every store view answering through the same provider account, enter the same API key in each workspace. Use a different key per workspace when you want each store view's usage billed or tracked separately.
Once one or more store views have their own workspace, the configuration screen at default scope lists them under Store-Level Overrides, each with its own Configure Chat button.
To undo it, use Reset to Global Account at that store view's scope: the store view goes back to inheriting the global workspace.
4. Sync that store view's data
Each workspace has its own knowledge base and needs its own sync. Run the sync for one store view with the --store option, using the store view's code:
bin/magento mirasvit:echat:sync --store=et
Run it once per store view that has its own workspace. With no --store, the command syncs all active stores.
See How to sync data manually and CLI commands for the other options.
5. Configure language, greetings and appearance per store view
With the store view's scope selected, click Configure Chat to open the eChat backend for that workspace - or reach the same place from the Store-Level Overrides list at default scope.
Everything that makes the widget speak a given language is set there, per workspace: the widget language, the greeting messages, the chatbot's guidance, appearance, and the AI provider and model. See How to configure the chatbot and Settings.
The language of the chat interface is resolved from the workspace: the Language set in its settings, and otherwise the locale of the store that workspace synced. A store view that inherits the global workspace therefore shows the global workspace's language, whatever language the storefront around it is rendering. That, together with the greeting texts and guidance being per workspace, is why a multi-language store needs a workspace per language.
6. Check the grouping
All workspaces created from the same Magento installation are grouped under one eChat account automatically, so they appear together rather than as unrelated workspaces. Review them in the eChat backend on the Workspaces tab.
Connecting, switching and resetting a registration requires the Mirasvit_EChat::echat_config ACL resource. An admin without it sees the connection status but none of the actions.