Bot permissions

Telegram permissions determine which moderation actions GramGroupsBot can perform.

Required for Group Connection

To connect a group with /connect:

• The command sender must be a Telegram group admin or creator.
• GramGroupsBot must be a Telegram group admin or creator.

Required for Message Moderation

To delete messages for stop words, blocked users, link rules, required words, and rate limits, the bot needs:

• Delete messages permission.

If this permission is missing, the bot can still detect the violation and attempt to emit a moderation event, but Telegram deletion fails. Network logs can show the delete failure if log delivery is configured.

Required for Mass Ban and Mass Mute

For /banall and /muteall, the bot needs:

• Admin status.
• Restrict members permission.

Groups without restrict permission are skipped during mass actions with skipped_no_permission.

Permission Status Fields

The dashboard and /status command use these stored fields:

• bot_status: creator, administrator, member, restricted, left, kicked, or unknown.
• bot_can_delete_messages: whether deletion is available.
• bot_can_restrict_members: whether ban/mute actions are available.

Check Permissions in a Group

Run this in a connected group:

/status

Example output:

Connected: yes
Group status: active
Account: Example Account
Bot status: administrator
Can delete messages: yes
Can restrict members: yes
Billable: yes

What Breaks When Permissions Are Missing

Operational Recommendation

For each managed group, make the bot admin with:

• Delete messages.
• Restrict members.

If the group is used as a network log destination and topic mode is enabled, the bot also needs enough rights to post messages and create forum topics in that destination chat.