Module of Logging
The section settings will allow you to keep a log of actions in your group. You can log both the actions of the group's Admins and automated system actions.
Action records are saved in a SEPARATE GROUP.
For information on how to add a group, see the "Guide on Groups".
❖ Logging Settings
Set Group to Store Logs
1. Specify the group for storing Logs by clicking its number. The bot will show a list of groups added to it - so the required group must be added in advance.
2. Specify a separate Topic for storing the Group Logs. Click «Set Empty» if you do not want to use Topics. Logs of different groups can be saved in separate Topics for convenience.
Commands in Group
Enabling will allow logging of actions of admins in the group - in particular the use of commands: !mute, !ban, !unmute, !unban, !reply.
When using a command in a group, the text of the message for which the command was used will also be saved in the logs.
More information on Admin's group commands.
Anti-spam Acts
Enabling will allow logging of the Anti-spam system actions of deleting messages.
More information on Antispam system in the group.
Acts in Settings
Enabling will allow logging of admin actions in the «Members» section of the group's settings: Mute, Kick, Unmute, Add admin, Remove admin.
When dealing with users via standard group's settings, messages that caused a Ban or Mute cannot be saved in the Logs. This is technically impossible - because Telegram does not provide this data - use commands in the group if it is important for you to save the message itself.
Regular Triggers
Enabling will allow to Log the usage of Regular Triggers in group (by admins and users, depending on the settings of the Triggers themselves).
On-Entry Triggers
Enabling will allow to Log the usage of "On-Entry" Triggers in group (by admins and users, depending on the settings of the Triggers themselves).
Joining Condition
Enabling will allow Logging of the facts of triggering the function «Condition for Join Request» - it will save the data of users who were REFUSED to join the group. The button is not visible in the menu if the function is not activated for this bot.
Functionality of the «🧩Extensions» section: for the option of logging the Joining Condition, to appear in the menu, this function must be activated in your bot.
84. Condition for Join Request.
To connect, go in your bot:☞ 🔐Admin | 🧩Extensions | 📂Channels and Groups
Paid Subscription
Enabling will allow logging of the «Paid Subscription» function triggering.
The following actions are logged:
• The user was not allowed into the group (or channel) by the Paid Subscription verification module.
• The user was «Kicked» after the subscription time expired in a standard way (automatically or after manual verification).
• The user was active in the group without having a subscription and was «Kicked» by activity.
• The user, not being a BOT user, was active in the group and was «Kicked» by activity.
❖ Log's Messages
Log messages are provided with hashtags for easy navigation through the entire list of similar entries.
By clicking on a hashtag you can navigate through all messages with that hashtag. For example, you can see all "bans", all deleted "spam messages", and so on.
In general, the Log message looks like this:
#xxxx #u2222222 #a7777777
• User: ProfileNameLink
• UserCode / ID: 3333333 / 2222222
• Admin: 7777777, AdminName
• Group: GroupName
• Command: Command
Where: #xxxx - tag of the action performed for search (mute, ban, spam, etc.) #u2222222 - user tag for search #a7777777 - admin tag for search User: ProfileNameLink - link to user profile UserCode / ID: 3333333 / 2222222 - user code and user ID Admin: 7777777, AdminName - admin ID and name Group: GroupName - group's name Command: Command - used command with admin's comment