Member Reports

Overview

Anyone in the server can right-click a message, choose Apps → Report Message, and say what is wrong with it. The report lands in your reports channel as a post with buttons, and a moderator presses one. Nothing is done to anyone automatically.

The queue lives in Discord rather than on the dashboard on purpose. The people who action a report are your moderators, and the dashboard only admits owners, administrators, Manage Server holders and Aegis Admin roles, so a moderator usually cannot open it. Putting the queue where they already are means they never need to. The dashboard keeps the settings and the history.

What the Reporting Member Sees

1. Right-click a message (long-press on mobile), open Apps, and choose Report Message.
2. A form asks What is wrong with it? (required, up to 1,000 characters) and an optional Category. A category is only worth filling in when the server lists offenses under its Severity tiers, since that is what it is matched against.
3. They get a confirmation with the report number. They are not told what was done about it.

A report is refused, with the reason, when the member is reporting their own message, a bot's message, a moderator (they are told to speak to the server owner instead), or the same message twice while the first report is still open, and when they are reporting faster than the server's cooldown or have not been in the server long enough. If the message was deleted before the report was sent, Aegis cannot tell who wrote it and asks them to report another of that person's messages or tell a moderator directly.

What Moderators See

Each report is a post in the reports channel showing the reported member (name and id), who reported them, which channel it happened in, the category (with the tier your Severity tiers put it in, when it matches), what the reporter said, the message itself, and a jump link. The message text is copied when the report is filed, because it is usually deleted moments later and a report that cannot show what was said is not reviewable.

Five buttons sit under the post: Dismiss, Warn, Mute 1h, Kick and Ban. Pressing any of them needs Mod tier, and each punishment checks the same permission as its command, so a moderator who cannot run /ban is refused the Ban button.

A punishment pressed here goes through the same path as the matching command: it records a strike, counts toward Strike Automation, sends the member their DM, and posts to the moderation log. A ban from the queue sends the usual ban notice, which carries the Appeal button when Appeals are set up.

When the action goes through, the post loses its buttons and gains a Handled line naming the moderator, so the channel reads as a worked queue rather than a pile of live decisions. When it fails (the member has left, sits above Aegis in the role list, or Discord refused), the report stays open and keeps its buttons, and the moderator is told why. When two moderators press at once, the second is told who got there first.

Settings

Everything lives on the dashboard under Moderation & Security → Member Reports.

Handled reports are kept for 90 days and open ones stay until handled. Reports count as moderation data: wiping a member's data removes the reports about them, and reports they filed lose their name.