User Monitor
Watch a suspicious member, and every monitored user gets their own log thread.
Overview#
User Monitor is for the member you are not ready to ban but are not ready to ignore either. Add them to monitoring and the bot opens a dedicated thread in a private log channel, then mirrors their activity into it: messages, voice moves, role and nickname changes, and whatever else you asked it to watch. When you have seen enough, you close the monitor with an outcome, and the thread is archived as a record of what happened.
User Monitor may not be available on every server yet. See Beta Features if you cannot find it in your dashboard.
How to Set Up#
- Go to the dashboard and select your server
- Navigate to the User Monitor section
- Click Create Log Channel. The bot makes a private channel where the monitor threads will live
- Click Monitor User, pick the member, and write a reason
- Choose a duration and which event categories to capture
- Start monitoring. The thread is created immediately
Moderators can do the same thing from Discord with /monitor add. Both routes require the Moderate Members permission.
What Gets Captured#
Each monitor watches the categories you pick. Everything the bot records lands in that user's thread, in order, so you can read the whole picture in one place instead of hunting through your audit logs.
| Category | What it records |
|---|---|
| Messages | Messages sent, edited and deleted by the user |
| Voice | Voice channel joins, leaves, moves, mutes and streams |
| Member | Nickname, role, avatar and timeout changes |
| Reactions | Reactions added and removed by the user |
| Threads | Threads the user creates, updates or deletes |
| AutoMod | AutoMod rules the user triggers |
At least one category must be selected. Choosing all of them is shown as "All events" on the board.
A few rules worth knowing:
- Bots cannot be monitored
- One active monitor per user: to change what an existing monitor watches, edit it rather than adding a second one
- If no log channel has been set up yet, the monitor is still created, but it has nowhere to write until you create one
Expiry#
A monitor either runs until you close it or expires on its own.
- With a duration, the monitor closes automatically when the time is up. The bot posts an "expired" notice into the thread and archives it
- Without one, it runs indefinitely until a moderator closes it
- Expiry is checked on a short cycle, so a monitor closes within a few minutes of its deadline rather than to the second
On the dashboard, durations are offered as presets: 1 day, 3 days, 7 days, 30 days, or Indefinite. From Discord, /monitor add takes a duration like 30m, 12h, 7d or 2w, and leaving it blank means indefinite.
Closing a Monitor#
Closing asks for an outcome, which becomes the permanent record of how the situation resolved:
| Outcome | Meaning |
|---|---|
| Cleared | Nothing came of it, no further action |
| Actioned | Moderation action was taken |
| Banned | The user was banned |
| Expired | Set automatically when a monitor runs out of time |
Whichever way it closes, the bot posts a closing summary into the thread and archives it. Closed monitors stay searchable on the dashboard so you keep the history.
The Dashboard View#
The User Monitor page lists every monitor with tabs for Active and Closed, and a search box that matches on member name, username, user ID or reason.
Each row shows:
- The member, with their avatar and name
- The reason the monitor was opened
- The event categories being captured
- When it was opened
- When it expires (or, for closed monitors, the outcome)
From a row you can open the log thread in Discord, edit an active monitor's reason, categories or expiry, or close it with an outcome.
Slash Commands#
| Command | What it does |
|---|---|
/monitor add | Starts monitoring a member, with an optional duration and reason |
/monitor remove | Closes a member's monitor, asking for the outcome |
/monitor list | Lists the active monitors in the server, paged |
All three reply privately and require the Moderate Members permission.
Tips#
- Keep the log channel private. It is a moderation record of specific members and should only be visible to staff.
- Write a reason your colleagues will understand next week. "Suspected alt of a banned user: same avatar, joined 10 minutes after the ban" is a record; "sus" is not.
- Narrow the categories to what you actually suspect. Watching only Messages keeps a spam investigation readable; turning everything on makes a busy member's thread very long very quickly.
- Prefer a duration to an indefinite monitor. Monitors that expire on their own stop your list filling with people nobody has thought about in months, and you can always reopen one.
- Close with the right outcome. Cleared, Actioned and Banned are what make the closed list useful later, especially if the same person comes back.
- Read the thread before you decide. It is the whole point of the feature: the sequence of what someone did is usually more telling than any single message.
- Combine it with Warnings. Monitoring shows you what is happening; a warning is what puts it on the member's record.