Moderation log

Set up in the Mini App#

Open Settings in your private chat with @defendy_bot, select the group under My groups and check its name at the top.

1. Open Logging. If no destination is connected, the setup wizard appears.
2. Choose the option to add the logging bot to a group or channel, select your destination and make @defendy_logs_bot an administrator.
3. Return and select the detected chat. If it is missing, enter its chat ID manually and an optional topic ID, then tap Check.
4. After verification succeeds, tap Done. The connection check may send a test message.
5. The wizard enables logging when it connects the destination. Verify that it remains enabled after saving, then choose event categories. For forum groups, configure a shared topic or separate topic IDs for individual categories.

Switches and selectors save when changed. In a separate form with a Save button, save before leaving. If a request fails, reopen the section to check its actual values.

In short#

The moderation log sends selected events to a separate chat, channel or forum topic so administrators can audit automatic actions.

How it works#

1. Defendy creates an event when moderation, a filter, membership or an administrator action occurs.
2. The event category selects the main log destination or its forum-topic override.
3. The formatted record is sent only if that category is enabled and the bot can write to the destination.

Every setting explained#

Enable logging#

Default: Off.

Main switch for sending moderation log events.

Destination type#

Default: Not set.

Chat, group, topic or disabled destination.

Destination chat ID#

Default: Not set.

Telegram chat or channel ID where logs are sent.

Destination topic ID#

Default: Not set.

Forum topic ID when the destination is a topic.

Moderation events#

Default: On.

Bans, mutes, kicks and warnings.

Filter events#

Default: On.

Anti-spam, profanity and stop-word triggers.

Member events#

Default: On.

Joins, leaves and captcha-related events.

Admin events#

Default: On.

Role, pin, delete and settings events.

Other events#

Default: Off.

Lower-signal events such as boosts.

Topics by event category#

Default: All use the main topic.

For a forum destination, moderation, filters, members, admin and other events can each be routed to a separate topic. An empty override falls back to the main log topic.

Practical example#

Send all logs to a private moderator group, then route filters and member events to separate topics. Trigger one test warning and one join to verify both paths.

Recommendations#

• The bot must be added to the log destination before verification succeeds.
• Topic destinations require both chat ID and topic ID.

Troubleshooting#

• Check the selected group, destination and logging switch.
• The destination must contain @defendy_logs_bot. In a channel, it needs administrator permission to post; in a group, it must be able to send messages.
• Confirm the relevant event category is enabled and its destination topic exists.
• Create a harmless test event after fixing the setup and look for its record. A missing record does not prove the bot action did not happen.