Timeline & Event Log

Telegram typically only keeps actions taken in your chat for up to 48 hours and is only available for admins to review. In order to extend the possibility as well as audit the events happening in your chat Modr8 supports a chat timeline which last for up to 6 months.

In addition to this timeline Modr8 also supports the possibility for an "Event Log Chat" to be connected. This type of chat is typically private for your moderation team. The bot will then log events and actions it is taking into the event log chat and your team can even moderate from this centralised log rather than needing to take action directly in the chat.

The Modr8 linked event log is very powerful and provides the ability for your community moderators to log:

  • New users joining your chat

  • Users leaving your chat

  • Users who have been banned

  • Users who have been warned

  • Users who have been kicked

  • Users who have been muted

  • Community reported messages using our reporting module

  • Filtered content

  • Achievement of new reputation levels

You are able to pick and choose which events you log to your moderation chat, as well as amend how messages are displayed with the following settings available:

  • Show filtered content messages that you can then approve to send back to chat

  • Display moderation buttons so you can quick ban, warn, mute or trust users

  • Silence moderation actions you take

How to view the Chat Timeline

  • Log into the Modr8 Platform

  • Select "Manage" on your bot profile

  • Scroll to your chat profile and select the "Timeline" button

Setup The Chat Event Log

In order to setup the chat event log, you will first need to carry out some steps on telegram and then some on our platform.

  1. Create a new private group with yourself and any admins you want to moderate with you

  2. Add your Modr8 bot as an admin to the chat. You do not need to /activate this chat.

  3. Log into the Modr8 Platform

  4. Select "Manage" on your bot profile

  5. Scroll to your chat profile and select the "Timeline" button

  6. Select the "Connect Log" button

  7. You will be shown a page that contains a command with /eventlog <<unique code>>

  8. Copy the /eventlog command and the unique code that comes with it, paste it into your private moderation group. Your bot will respond "Event log enabled".

  9. The event log web-page will update to show you the event options you can pick and choose from

Configure Event Log Settings

The eventlog configuration page is split into two areas. The first being which events you wish to report to your moderation chat and then the second being the options about what can be done with those events once reported.

We recommend turning on the following events:

  • New user

  • User Warned

  • User Banned

  • Reported Messages

  • Reported Messages

These events will give you a good view of what the bot is doing and how the chat is behaving. We also recommend to turn on:

  • Show filtered content - to be able to see messages that the bot has removed

  • Display moderation buttons - to be able to take quick action on users based on the reported events.

All of the above settings can be accessed and amended by completing the following steps:

  1. Log into the Modr8 Platform

  2. Select "Manage" on your bot profile

  3. Scroll to your chat profile and select the "Timeline" button

  4. Select the "Edit" button on the "Manage Event Logs" card

  5. Select the toggles you wish to adjust on the event log page

  6. Click "Save Changes"

FAQ & Troubleshooting

My bot is reporting events in my main chat

This happens when you have run the /eventlog command with the unique code in your main chat and not in a new private group with yourself and other moderation admins. Disconnect the current log by completing these steps:

  1. Log into the Modr8 Platform

  2. Select "Manage" on your bot profile

  3. Scroll to your chat profile and select the "Timeline" button

  4. Select the "Edit" button on the "Manage Event Logs" card

  5. Click the "Remove Chat" button to disconnect

You can now re-run the /eventlog command in your private group with its unique code to connect up the correct one.

Last updated