1
Branding — the logo and accent apply to the header and the login screen.
2
The organization timezone (IANA) is the default for displaying dates; users override it in their profile. Language and date format are org defaults too.
1
Conversational bot: employees ask about company knowledge in direct messages — an inbound surface, separate from the outbound
delivery channels. The toggle shuts the bot off in one move —
don’t confuse the three Slacks.
2
Bot token and signing secret are write-only: never returned to the UI or an export. “Test connection” pings Slack (auth.test); the chip shows the result of the last check.
3
Recognizes an employee by their provisioned workspace email and links them automatically (identity_mapping). Where the workspace lets users edit their own email, turn this off: only on-demand code linking remains (messenger linking).
If the email doesn’t match or auto-link is off, the bot offers to link the account with a code.
1
The toggle is the bot’s master switch: it closes the inbound surface in one move without touching the token.
2
Bot token (issued by @BotFather) is write-only: never returned to the UI or an export. “Test connection” pings Telegram (getMe); the chip shows the result of the last check.
3
Achilles generates the webhook secret itself on connection (setWebhook) — the admin never enters it manually; it authenticates inbound updates.
Sign-in and identity linking happen on the Auth screen: Telegram has no provisioned email, so there is no auto-match — only on-demand code linking.
1
The toggle is the bot’s master switch: it closes the inbound surface in one move without touching the token. Turning it on checks the server live first; a refusal rolls the switch back.
2
Bot token (a Mattermost bot account token) is write-only: never returned to the UI or an export. “Test connection” pings the server (users/me); the chip shows the result of the last check and the bot’s handle.
3
A quiet status line: whether the bot’s listener is currently connected to the server; “not connected” means messages aren’t being received.
Sign-in and identity linking happen on the Auth screen: Mattermost is linked by an on-demand code only, like Telegram — no auto-match.
Integrations and maintenance
integrations · maintenance
Integrations
Delivery channels — Slack and webhooks live together with the organization’s notificationsConfigure
MCP server lets external AI assistants (Claude Code and others) connect to the knowledge base; the switch closes the integration for everyone at once1
Maintenance mode users see a full-screen placeholder; sync and agents are paused2
Data export v2 configuration as JSON, without credentials3
1
The MCP server is open by default; the Owner locks the door with a confirmation — external assistants are rejected, while API keys stay alive. The surface and its mechanics —
MCP.
2
The Owner enables maintenance mode with a confirmation; users see a full-screen placeholder —
mode mechanics.
3
Data export — settings, data sources, and agents as JSON for backup and migration; credentials are not exported.
Delivery channels (Slack, webhooks) and the notification matrix are on the
Notifications screen.