--- title: Connections Commands description: Complete guide to Connections module commands and features --- # 📦 Connections Commands This module allows you to connect to a chat's database, and add things to it without the chat knowing about it! For obvious reasons, you need to be an admin to add things; but any member can view your data. (banned/kicked users can't!) *Commands*: × /connect ``: Connect to the specified chat, allowing you to view/edit contents. × /disconnect: Disconnect from the current chat. × /reconnect: Reconnect to the previously connect chat × /connection: See information about the currently connected chat. × /settings: Pick a group where you are an admin and see all of its settings; values that differ from the default are marked with •. Only groups where you have written since the bot joined are listed; for others use /connect `` or send /settings in the group. *Admin Commands:* × /allowconnect : Allow users to connect to chats or not. While connected, admins can also run /captcha, /antiraid, /aispam, /anonadmin, /addreaction, /allowconnect and /lang group from PM. In PM, /rules, /notes, /filters and many settings commands, such as /lock, /setflood, /setwelcome and /setwarnlimit, take the group as their first argument: its ID, its @username, or the title of a group where you are an admin. Titles are looked up only among the connected group and the 50 most recently active groups where you have written; name any other group by its @username or ID. From PM, the owner of a group can also run /clearall, /stopall, /remallbl, /unapproveall, /resetallwarns and /unbanall, and its admins /privnote: name the group first (its title, @username or ID) or connect to it. The confirmation acts on that group and only its owner can press it. From PM, a group's admins can also run /adminlist, /invitelink, /setgtitle, /setgdesc, /timezone, /admincache and /clearadmincache: name the group first (its title, @username or ID) or connect to it. They need the same rights as in the group, and the answer comes to PM. From PM, a group's admins can also run /ban, /sban, /tban, /unban, /baninfo, /banlist, /kick, /skick, /restrict, /unrestrict, /mute, /smute, /tmute, /unmute, /warn, /swarn, /rmwarn and /resetwarns: name the group first (its title, @username or ID), then the user (@username, ID or mention), or connect to the group. While connected, only an @username or ID picks another group. They need the same rights as in the group; a reply in PM names no user, and the answer and buttons come to PM. From PM, a group's members can also see a user's warns there with /warns if the group allows members to connect (/allowconnect; otherwise only its admins can), and its admins the group's warn settings with /warnings: name the group first (its @username or ID; its admins may also use its title), then for /warns the user, or connect to the group. The answer comes to PM. You can retrieve the chat id by using the /id command in your chat. Don't be surprised if the id is negative; all super groups have negative ids. ## Module Aliases > These are help-menu module names, not command aliases. This module can be accessed using the following aliases: - `connection` - `connect` ## Available Commands | Command | Description | Disableable | |---------|-------------|-------------| | `/allowconnect` | Toggle whether users can connect to this chat | ❌ | | `/connect` | Connect to a group chat from private messages | ❌ | | `/connection` | Show current connection status | ❌ | | `/disconnect` | Disconnect from the connected group chat | ❌ | | `/reconnect` | Reconnect to the last connected group chat | ❌ | | `/settings` | Pick a group in PM and show all of its settings | ❌ | ## Usage Examples ### Basic Usage ``` /allowconnect /connect /connection ``` For detailed command usage, refer to the commands table above. ## Required Permissions - `/allowconnect` — Requires **Admin** (`IsUserAdmin`) in the target group. From PM it acts on the connected group or the group named first. - `/settings` — Lists and connects only groups where you are an **Admin**; rights are checked again when you tap a group. - `/connect`, `/disconnect`, `/connection`, `/reconnect` — Available to all users, but connection authorization depends on the target chat's settings (admins always allowed; non-admins need `allow_connect` enabled and must be current members, not kicked/left). ## A Group as the First Argument in PM Some commands take the group as their first argument in PM, so they work without `/connect`: - without arguments of their own: `/rules`, `/notes`, `/saved`, `/filters`, `/locks`, `/locktypes`, `/flood`, `/disabled`, `/reactions`, `/resetreactions`, `/resetrules`, `/resetrulesbutton`, `/blacklists`, `/approved`, `/unsetlog`, `/logchannel`, `/resetwelcome`, `/resetgoodbye`; - with arguments of their own: `/lock`, `/unlock`, `/setflood`, `/setfloodmode`, `/delflood`, `/disable`, `/enable`, `/disabledel`, `/addreaction`, `/removereaction`, `/antiraid`, `/raidtime`, `/raidactiontime`, `/autoantiraid`, `/antichannelpin`, `/cleanlinked`, `/allowconnect`, `/setrules`, `/privaterules`, `/rulesbtn`, `/addblacklist`, `/rmblacklist`, `/blaction`, `/approve`, `/unapprove`, `/approval`, `/setlog`, `/log`, `/nolog`, `/welcome`, `/setwelcome`, `/goodbye`, `/setgoodbye`, `/cleanwelcome`, `/cleangoodbye`, `/cleanservice`, `/autoapprove`, `/captcha`, `/captchamode`, `/captchatime`, `/captchaaction`, `/captchamaxattempts`, `/captchapending`, `/captchaclear`, `/setwarnlimit`, `/setwarnmode`, `/setwarntime`, `/aispam`, `/spamdb`, `/probation`, `/anonadmin`. Aliases of these commands work the same way. Name the group by its ID, its @username, or the title of a group where you are an admin (case does not matter; quote a title with spaces), for example `/notes "My Group"` or `/lock @mygroup sticker`. The group passes the same checks as `/connect`, the command checks your rights in it as it does on a connection, and the saved connection stays as it is. A title is looked up among the connected group and the 50 most recently active groups where you have written, and only the groups with that title are checked for admin rights (when more than 3 of them share it, name the group by its ID or @username), so it does not depend on the `/settings` picker's list; any other group is named by its ID or @username, which are looked up directly. A title lookup shares the `/settings` list's 5-second pause: within it a title is looked up in the last list shown, and if there is none the bot only says how long to wait. When you are connected, a command with arguments of its own takes another group only by its ID or @username: any other first word is its own argument, so `/lock sticker` locks stickers in the connected group. A user's @username or ID stays the command's argument: on a connection `/approve @someone` approves that user in the connected group. Without a group and without a connection, these commands answer with their help, an example and the groups where you are an admin. `/connect` without an argument in PM answers with its help, an example and the groups where you are an admin, with their IDs. ## Settings Summary `/settings` in PM lists up to 20 groups where you are an admin: the connected group first, then groups where you have written since the bot joined, most recently active first. Only the 50 most recently active of those groups are checked, so an admin group past them is not listed; use `/connect ` or `/settings` in that group. Groups whose admin list the bot has not cached are checked with Telegram for at most 3 seconds per list, so some of them may be missing; open the list again to check the rest. The connected group stays listed even when those 3 seconds run out. The list is built at most once every 5 seconds per user: a quicker `/settings` only shows how long to wait, and **Another group** shows the last list again. Tapping a group re-checks your rights, connects you and shows every setting of that group, one line per command (for example `/captcha — on`). Lines that differ from what a new group gets are marked with `•`. **Refresh** re-reads the settings and **Another group** returns to the list. Showing the summary never writes settings. Below the summary, a button for each on/off or few-value setting sets it to the value after its arrow (for example `captchamode → text`) and shows the summary again. A tap needs the rights the command needs, and writes the setting exactly as sending the command would: | Button | Values | Needs, besides being an admin | | --- | --- | --- | | `captcha` | on, off | bot admin; turning it off releases users a pending captcha holds | | `captchamode` | math, text | | | `captchaaction` | kick, ban, mute | | | `setfloodmode` | mute, ban, kick | bot admin | | `delflood` | on, off | bot admin | | `antiraid` | on, off | bot admin; on starts raid mode for the raid time | | `aispam` | on, off | on needs the operator to have set up the AI spam filter | | `welcome`, `goodbye` | on, off | | | `cleanwelcome`, `cleangoodbye` | on, off | the change-info right | | `cleanservice`, `autoapprove` | on, off | the change-info right; bot admin | | `reports`, `privaterules`, `antichannelpin`, `cleanlinked`, `disabledel` | on, off | bot admin | | `privnote`, `allowconnect` | on, off | | | `quietfed` | on, off | the group is in a federation (only then is the line shown) | | `anonadmin` | on, off | group creator; bot admin | A button carries the value it sets, so tapping one on an older summary sets that value, even if someone changed the setting since. `/settings` in a group (admins only) replies with a button (`t.me/?start=settings_`) that opens the same summary in PM. Admins who never wrote in the group, and anonymous admins, are not in the list; they can use `/connect ` or `/settings` in the group. ## Inline Keyboard Feature When a user is connected via PM, the `/connection` command and the connect flow show an inline keyboard with buttons driven by `connbtns`-prefixed callback data: | Button | Target | Shows | |--------|--------|-------| | **Admin Commands** | Admins only | The heading "Available Admin commands" only (no command list yet) | | **User Commands** | All connected users | The heading "Available User commands" only (no command list yet) | A **Back** button (→ `connbtns.Main`) returns to the main connection view. ## Two Connection Modes `/connect` behaves differently depending on where it's used: - **Private chat (PM)**: Extracts a chat argument, authorizes the user, and connects immediately. Shows the inline keyboard for available commands. - **Group chat**: Does not connect directly. Instead shows a deep-link button `t.me/?start=connect_` that the user must tap to connect from PM.