Reports

Usage

To make a report, run the /report command. You then select the user or the message breaking the rules that have been set on the server.

When reporting a user, the source option indicates where the infraction was observed (text channel, voice channel, direct message or elsewhere).

You can also attach a screenshot (PNG, JPEG or GIF) or a video (MP4, WebM, MOV, within the size limit allowed by the server's boost level) through the image option, available on both variants of the command.

If the reported message was published by an application, DraftBot identifies and displays the member actually behind the content.

You can also go through Discord's context menu: right-click a member → Apps → Report this user, or right-click a message → Apps → Report this message. A form then opens to enter the reason and the source (for a user).

Managing reports

Once someone has reported a user or a message, you receive a report message in the channel you have set beforehand:

The message gathers the useful information about the reported member (date they joined the server, date the account was created, quick access to the sanction history through the View sanctions button, displayed only to the member who clicks it) as well as the context of the report (channel, source, link to the reported message).

You then have several options:

• "Take charge" ➜ Indicates that you are handling the report. If another moderator has already taken charge of the report, a confirmation is requested before adding you to it.
• "Mark as processed" ➜ Closes the report.

You can then select the outcome to give the report among the following options: Member sanctioned, Report solved, and Report rejected. If the reported member has been sanctioned within the past hour (through /ban, /mod or otherwise), DraftBot offers to link that sanction to the report in one click. Once the outcome has been selected, you can add an optional context, visible on the report message and also sent to the reporting member by DM if the corresponding detail is enabled in the notification configuration.

• "Tickets" ➜ Displays the tickets already linked to the report and lets you open a new one for the reported member or the member behind the report (only available if the ticket system is enabled).
• "Sanction the member" ➜ Sanctions the reported member directly through a predefined sanction or a custom sanction (Note, Warn, Kick, Mute, Ban). For a temporary custom sanction, you also give a duration (formats 1h, 30m, 2d, etc.). You can delete the member's recent messages over a predefined window (1h, 6h, 12h, 24h, 3 days, 7 days), attach images to the sanction, and add a context: this context is recorded in the member's sanction history (never sent to the sanctioned member) and completed automatically with a link to the report message. The selector only appears if at least one predefined sanction is recorded, or if the Custom sanction option is enabled in the configuration.

Integrations

The report system integrates several features to offer a pleasant and practical user experience.

Predefined sanctions

The system integrates predefined sanctions to sanction reported people, saving you from running the /mod command every time.

Tickets

The system also integrates tickets. It can open a ticket for the reported member or the reporting member, to talk things through or find out more about the subject of the report.

Configuration

To enable the report system, you first have to configure it. There are several ways of doing so.

Enabling the system

First of all, for your members to be able to report a user or a message, the system has to be enabled.

From the panelUsing the /config command

⫸ Open the DraftBot panel

You will then find a grey button on the left, on the same line as the title. Click it to enable the system.

Run the /config command, then select Report from the dropdown menu.

You will then find a blue button labelled Enable the system. Click it to enable the system.

Reaction

You can configure a reaction that tells the other members, or the message's recipient, that it has been reported.

Automatic thread

For the best organization, you can configure a thread to be opened automatically whenever a user or a message is reported.

Mentioned roles

To stay informed, you can add one or more roles mentioned on every new report. The global mentions @everyone and @here are supported as well.

Receiving reports

Every member report can be centralized in a single channel.

Managing reports

To make report management easier, you can grant access to a specific role for handling reports.

Limit of claims per moderator

To spread the load between moderators and stop a single one from blocking the ongoing reports, you can set the maximum number of reports the same person can take charge of at the same time (between 1 and 10).

Grouping similar reports

When this option is enabled, reports targeting the same member within a short interval (15 minutes) are grouped, to avoid having several nearly identical messages in the reports channel. New reports enrich the existing message instead.

Custom sanctions

As well as predefined sanctions, you can let moderators apply a custom sanction from the "Sanction the member" selector of the report message (note, warn, kick, mute, ban, with free reason and duration).

DM notifications for reporting members

You can automatically inform the members who made a report, by direct message, when it is closed (solved, rejected or sanctioned). You choose which details to send them among: Status, Moderator, Context and Sanction. If no detail is selected, the member only receives the confirmation that their report has been processed.

Confirmation message

You can customize the confirmation message telling your users that their reports have been sent.

You can customize your message with several variables specific to reports:

Sorting thread

You can sort your processed reports into several threads for better organization.

Here are the different threads:

• Thread for solved reports
• Thread for sanctioned reports
• Thread for rejected reports