Incident Reports & Strike Management
Incident Reports is an optional Submitt moderation module for communities that need a formal staff-review process before discipline is applied. Communities define the report format and strike policy in the dashboard; reports are completed in Discord, evidence can be attached, and no punishment runs until an authorized reviewer approves the report.
A submitted incident report does not automatically punish anyone. Pending reports must be Approved or Denied. Denied reports are archived with no punishment. Approved reports are processed against the configured strike level.
Enable or disable the module
Go to Dashboard → Incident Reports and turn on Enable Incident Reports. This switch controls only Incident Reports. Turning it off does not disable Tickets, Applications, Anti-Spam, Anti-Nuke or the rest of Moderation & Safety.
The server's main Moderation & Safety switch must also be enabled for Discord incident panels and punishments to operate. This prevents an incident module from silently bypassing a server-wide moderation shutdown.
Build strike & punishment policies
Each community chooses what every strike level means. Strike numbers do not have a universal Submitt punishment; the dashboard policy controls the action.
Approve and preserve the incident without an automatic Discord punishment.
Create a warning/moderation case for the member.
Timeout the member for the configured number of minutes.
Temporarily ban/remove the member, automatically unban them when the duration expires, save their eligible roles, and restore those roles when they rejoin if role restoration is enabled.
Remove manageable member roles while preserving the incident case.
Add a configured suspension/discipline role.
Remove the member from the Discord server without banning them.
Ban the member for the configured duration and automatically unban when it expires.
Ban the member until an authorized moderator later removes the ban.
For example, a server can configure Strike 1 as a 2-day Timeout, Strike 2 as a 2-day Temporary Server Removal with saved-role restoration, and Strike 3 as a permanent Ban.
Discord cannot force a removed member to rejoin automatically. Submitt unbans them when the punishment expires; if they later rejoin, Submitt restores the saved eligible roles that still exist and remain manageable by the bot. If New-Member Quarantine is enabled, saved-role restoration waits until the member completes /verify so restored access roles cannot bypass quarantine.
Create an incident-report panel
Each Incident Panel can have its own public panel channel, staff-only review channel, reviewer roles, button label and custom report questions. When evidence is enabled, Submitt creates a private evidence thread under the public panel channel so the reporter can upload files without gaining access to the staff review channel. This lets one community run separate panels such as Staff Misconduct, Player Misconduct, Internal Discipline or Rule Violations.
- Create an Incident Panel in the dashboard.
- Choose a normal Discord text channel where the public File Incident Report button should be posted. Submitt uses this channel as the parent for private evidence threads.
- Choose the staff-only review channel where approval/denial controls are posted.
- Select the Discord roles allowed to approve or deny reports.
- Add the community-specific report questions.
- Publish the panel to Discord.
Custom report format
Submitt automatically asks for the reported member and requested strike level. Administrators then add up to 25 custom Short Text or Long Text questions. Discord presents larger report forms in multiple modal steps so communities are not limited to one five-field modal.
Examples include Incident Date, Rule Violated, Detailed Description, Witnesses, Prior Coaching, Staff Notes or any other field the community needs.
Removing a custom question only removes it from future incident forms. Existing reports keep their historical answers. Likewise, deleting a panel that already has report history archives/disables the panel instead of erasing past incidents.
Screenshots, videos and evidence
When evidence is enabled, finishing the report questions creates a private incident evidence thread under the public panel channel. The reporter and configured reviewer-role members are added to that private thread. The reporter can upload Discord attachments such as screenshots, images, clips or videos. Submitt records the attachment URL, file name, content type, size and Discord message reference with the report.
The panel controls the maximum number of evidence files. After uploading evidence, the reporter presses Submit for Review.
Review workflow
The normal workflow is:
Draft → Evidence → Pending Review → Approved or Denied → Processed
- Draft: answers are saved while the reporter finishes the Discord form/evidence step.
- Pending: reviewer roles can inspect the questions and evidence.
- Denied: the decision/reason is stored and no strike punishment is applied.
- Approved: Submitt processes the strike policy and creates a linked moderation case.
- Processed: the configured Discord punishment completed successfully.
Reviewers can approve/deny from the staff-only Discord review-channel message or from Dashboard → Incident Reports. The private evidence thread remains a separate evidence workspace.
History and moderation cases
Incident reports remain associated with the reported Discord ID, strike level, reporter, reviewer, evidence, decision, selected policy and resulting moderation case. This creates a durable discipline history instead of relying only on messages in a staff channel.
Discord permissions and intents
Member notifications
Each strike policy can optionally DM the disciplined member when an approved incident is processed. Administrators can provide a custom message and use {server} and {strike}. Failed DMs do not roll back an otherwise successful incident decision.