Telegram Modlog: How to Track All Admin Actions in Your Group

When you have multiple administrators in a Telegram group, things can get confusing fast. Who banned that user? When was the word filter updated? Why was someone muted yesterday? Without a record of admin actions, these questions lead to finger-pointing, misunderstandings, and inconsistent moderation.

A modlog solves this by recording every moderation action with timestamps, the admin who performed it, and the affected user or setting. It is a core part of every good group admin's toolkit. OmniGest provides a built-in modlog that works automatically.

What the Modlog Tracks

OmniGest's modlog records a comprehensive list of admin and bot actions. Every entry includes the date, time, the admin who performed the action, and relevant details.

User Moderation Actions

• Bans -- When a user is banned from the group, including who issued the ban.
• Unbans -- When a previously banned user is allowed back.
• Mutes -- Temporary or permanent mutes, including duration.
• Unmutes -- When a muted user has their permissions restored.
• Warns -- Warning issued to a user, including the reason.
• Kicks -- When a user is removed from the group without being banned.

Automated Actions

• Anti-spam triggers -- When the bot automatically removes spam.
• Anti-flood triggers -- When a user is muted for flooding messages.
• Word filter matches -- When a message is deleted for containing blocked words.
• Captcha failures -- When a new member fails the captcha verification.
• AI moderation flags -- When the AI content detection system identifies problematic content.

Configuration Changes

• Settings updates -- Changes to group configuration through /config.
• Night mode activations -- When night mode turns on or off.
• Custom command changes -- When commands are added or removed.

Using the /modlog Command

The /modlog command lets administrators review recent moderation history directly in the group chat.

/modlog

This displays the most recent moderation actions in a clean, formatted list. Each entry shows:

• The timestamp of the action
• The type of action performed
• The administrator or system that triggered it
• The affected user (if applicable)
• Any additional context or reason

For detailed usage options, see the Modlog documentation.

Setting Up a Log Channel

While the /modlog command is useful for quick checks, many groups prefer a dedicated log channel where all actions are recorded in real time. This keeps the main group chat clean and provides a permanent, searchable record.

To set up a log channel:

1. Create a private Telegram channel (e.g., "Group Name - Mod Logs").
2. Add OmniGest bot as an administrator of that channel.
3. Use /config in your group and navigate to the Log Channel section.
4. Set the channel as your log destination.

From that point forward, every moderation action is automatically posted to the log channel as it happens. Admins can review the channel at any time without cluttering the main group.

Learn more about log channel configuration in our log channel setup guide.

Why a Modlog Matters

Accountability

When every action is recorded, administrators think more carefully before acting. Combined with a progressive warning system, the modlog ensures fair and consistent moderation. A modlog creates a natural accountability mechanism. If an admin bans someone unfairly, the record is there for other admins to review and reverse if necessary.

Dispute Resolution

Users sometimes claim they were banned or muted unfairly. With a modlog, you can look up the exact action, who performed it, and when. This turns "he said, she said" disputes into factual discussions based on recorded evidence.

Training New Admins

When you add new moderators to your team, the modlog serves as a learning tool. They can review how experienced admins handle situations, what actions are typically taken for certain violations, and what the group's moderation standards look like in practice.

Pattern Detection

Over time, modlog data reveals patterns. You might notice that most spam happens during certain hours, that a specific type of content keeps getting flagged, or that one admin handles 80% of the moderation load. These insights help you adjust your moderation strategy.

Practical Scenarios

Scenario: Late-Night Ban Review

An admin bans a user at 3 AM. The next morning, other admins are unsure why. They check the modlog and see the ban was triggered by the word filter after the user posted prohibited content three times. The ban was justified, and no further action is needed.

Scenario: Configuration Audit

Your group settings seem different -- welcome messages changed, night mode schedule shifted. The modlog shows exactly which admin made the changes and when. You can discuss the changes and revert them if they were not agreed upon by the team.

Scenario: Spam Wave Analysis

Your group gets hit by a spam wave over the weekend. Monday morning, the modlog shows the bot automatically caught and removed 47 spam messages, muted 12 accounts, and banned 8 confirmed spam bots. You can see exactly what happened and whether any legitimate users were affected.

Modlog Data Retention

OmniGest retains modlog entries according to its data retention policy. A background process runs daily to clean up old entries, keeping the database efficient while maintaining enough history for practical moderation needs.

For groups that need longer retention, the log channel approach provides a permanent record in Telegram itself, independent of database retention schedules.

Getting Started

The modlog is enabled by default in OmniGest -- there is nothing to configure. As soon as the bot is added to your group with admin permissions, it begins recording actions automatically.

For the best experience, set up a dedicated log channel so you have a permanent, searchable record of all moderation activity.

Add @OmniGest_bot to your group today and never wonder "who did what" again. See the Getting Started guide for a full setup walkthrough.