Open Settings → Telegram accounts to manage the accounts that actually send and receive Telegram messages, their links to the current workspace, and member access.
Connect an account
Members with connection permission can open the connection dialog and choose:
| Method | Action |
|---|---|
| QR-code sign-in | Confirm in the mobile Telegram app under Settings → Devices → Scan QR code |
| Phone-number sign-in | Choose a country code, enter the phone number, then enter the code Telegram sends to the phone or app |
| Two-step verification | If enabled on the account, also enter the Telegram two-step verification password |
Keep the dialog open during authorization and follow the current step. When the page confirms a successful connection, select Done, then check runtime status and conversation synchronization. Read the error before retrying; verification codes and QR codes can expire.
Connecting an account requires an available background Worker. If no node is available, the runtime node is offline, or authorization fails, ask operations staff to investigate rather than repeatedly signing in.
Understand account status
Account cards show authorization, workspace association, and runtime status separately. A workspace association does not mean Telegram authorization is valid, and valid authorization does not mean the Worker is currently connected.
The account must be ready before normal synchronization and sending can work. When it is offline, the Messages page may retain conversation summaries from the last sync. Use Refresh and sync account profile to update profile information, and the sync-status entry on the Messages page to check conversation sync progress.
Grant member permissions
Open member grants for the account and configure ordinary members' permissions:
| Permission | Purpose |
|---|---|
| View | Browse accessible conversations and messages; reading can trigger shared read status when the required conditions are met |
| Send | Send messages and perform supported message write operations in accessible conversations |
| Broadcast | Create and run broadcast tasks using this account |
| Manage grants | Manage member grants and enable the corresponding account management actions |
Owners and administrators inherit account capabilities; ordinary members receive explicit grants. Saving also validates membership and permission combinations. Open chats and subsequent actions are revalidated when permissions change.
Platform grants do not replace Telegram group administrator privileges, channel posting permissions, or Telegram rate limits.
Disconnect and reconnect
Only workspace owners and administrators can disconnect accounts. Ordinary members cannot disconnect them even with account management grants. Disconnecting an account card removes only the current workspace's association and access. Before confirming, review pending messages, broadcasts, auto-replies, and linked tickets in that workspace.
The same account may be used in other workspaces. Disconnecting does not delete it from every workspace or revoke all Telegram sessions. Reconnecting does not automatically restore the connection generation used by old ticket links, and it does not bypass chat exclusions.
Do not use disconnecting and reconnecting as a universal connection fix. First distinguish expired account authorization, an offline Worker, and failed conversation synchronization.
Common questions
| Symptom | What to check |
|---|---|
| Connection or grant buttons are missing | Current workspace role, capabilities, and account management grants |
| A long wait after scanning | Confirmation on the phone, two-step verification, Worker TCP authorization, and network connectivity |
| Connection succeeded, but sending fails | Runtime status, member Send permission, chat exclusions, and Telegram posting permissions |
| Account name or avatar has not updated | Refresh the profile and wait for server synchronization |
| Worker health check succeeds, but sign-in fails | Local process health does not prove a handshake with the main service; operations should check authorization expiry and source IP |
Implementation references: account page, connection dialog, and member grants. For operations details, see Worker operations.