Moderation log

Tip: change one option at a time and verify the result in the group so false positives are easy to spot.

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.

Set it up step by step#

1. Open Defendy in Telegram and choose the group you want to configure.
2. Compare the current values with the defaults explained below.
3. Change one option at a time; use the least disruptive value that meets your goal.
4. Check the result in the group after saving.

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 that Defendy is still an administrator in the group.
• Refresh the settings panel and make sure you are editing the correct group.
• If a setting is saved but does not work, check the bot permissions in Telegram.
• If you are not sure what happened, open the moderation log.