#955: How to enable Premium plan features
Отредактирована: сегодняIMPORTANT: flags without the __ prefix only work if these features are included in the license. If a feature is not in the license, the flag in .env will not enable it.
Make sure that all the following flags are enabled in /root/swarmica/.env in FEATURES:
grep FEATURES .env
FEATURES=chats,widgets,telegram,whatsapp_green,vk,max,mango_office,beeline_pbx,automations,automations_macros,automations_outgoing_emails,issue_tracker,api_keys,external_tickets,assets,time_tracking,ai,__ai_assistant,__ai_create_draft,__ai_mdxeditor,__ai_ticket_classifier,__ai_ticket_summary,__ai_mcp_agents,qa,reporting,automations_outgoing_webhooks,automations_scripts,external_search,wfm,__csat_anytime,__sensitive_data
| What is included | Flags |
|---|---|
| «Basic» plan features: chats and web widgets, messengers, telephony, automations | chats, widgets, telegram, whatsapp_green, vk, max, mango_office, beeline_pbx, automations, automations_macros, automations_outgoing_emails |
| «Pro» plan features: integration with task trackers, API, outgoing tickets, assets, time tracking | issue_tracker, api_keys, external_tickets, assets, time_tracking |
| «Premium» plan features: AI functions, quality control, report builder, outgoing webhooks, plugin scripts, external search sources | ai, __ai_assistant, __ai_create_draft, __ai_mdxeditor, __ai_ticket_classifier, __ai_ticket_summary, __ai_mcp_agents, qa, reporting, automations_outgoing_webhooks, automations_scripts, external_search |
| Additional | wfm — agent activity histogram; __csat_anytime — star rating on comments; __sensitive_data — sensitive data |
The list is designed for version 6.0 and later. In earlier versions, some flags are missing or have different names — check the article FEATURES feature flags.
In /root/swarmica/.env, check that the following authentication methods are enabled:
grep AUTH_PROVIDERS .env
AUTH_PROVIDERS=email,anonymous,code
To log in via SSO (ADFS, Keycloak, OpenID Connect), add the desired provider to AUTH_PROVIDERS and set the OAUTH2_ADFS_* or OIDC_* variables.
Telegram, VK, and MAX channels operate in separate containers: uncomment their services in docker-compose.yml.
To connect the Whatsapp channel, you must first connect the corresponding container according to the instructions, then connect Whatsapp via Green API according to the instructions.
The MCP server is connected separately, according to the article Connecting Swarmica functions to LLM using MCP.
A restart of the containers is required after all:
docker compose down && docker compose up -d