An Admin connects messaging services at platform level. Each user then binds their own identity and chooses notification subscriptions in their account.
Choose a channel
Platform credentials: SMTP; optional IMAP for conversations. Personal identity: Account email.
Slack
Platform credentials: Bot and app tokens. Personal identity: Member ID.
Telegram
Platform credentials: Bot token. Personal identity: Numeric user ID.
Discord
Platform credentials: Bot token. Personal identity: User ID.
Lark
Platform credentials: App ID and App Secret. Personal identity: App-scoped open_id.
Feishu
Platform credentials: App ID and App Secret. Personal identity: App-scoped open_id.
Display names, group IDs, and bot IDs are not interchangeable with personal user IDs.
Connect and verify
Follow the channel’s creation, permission, installation, and event-reception steps. Save platform credentials, enter your own identity in your account, and review your notification preferences. New bindings receive notifications by default.
For AI conversations, also configure a model. Start with a read-only question and confirm the account and deployment. Ordinary notifications do not require AI.
Entering another person’s ID can expose your notifications and account permissions to that identity. Verify your own immutable ID before saving.
Troubleshoot by layer
Check the platform app and credentials, network connection, event permissions, personal binding, subscription, and model separately. A working avatar lookup does not prove message delivery or correct account binding.
Use notification troubleshooting for role filtering, language, and delivery failures.