Features Docs Premium Trust Center Lookup Feed Dashboard Add to Discord
Documentation

Command Reference

Full reference for every slash command - parameters, permission levels, and usage examples.

Command Catalog

Every Blacklist Terminal command, in one place.

This live catalog is pulled from the Blacklist Terminal API so the website can reflect the same evidence, case management, moderation, premium, and safety tools available inside Discord.

71 commands shown

Core blacklist tools

Submit, check, and manage blacklist records.

/report user

Submit a blacklist report with required evidence.

Access: Approved staff / authorized servers Required: discord_id, category, reason, evidence_summary, evidence Optional: evidence2, evidence3, evidence4, evidence5, expires
/checkuser

Check whether a Discord user is blacklisted.

Access: Server users Required: discord_id Optional: None
/listusers

View blacklist database entries.

Access: Staff Required: None Optional: None
/removeuser

Remove a Discord user from the blacklist.

Access: Staff Required: discord_id Optional: None
/listevidence

List evidence connected to a blacklisted user.

Access: Staff Required: discord_id Optional: None
/userstats

Show stored stats for a Discord user.

Access: Staff Required: discord_id Optional: None

Report guidance

Help users submit useful reports and track decisions.

/report guide

Show the evidence standards and report submission rules.

Access: Server users Required: None Optional: None
/report status

Check the current status of a report case.

Access: Reporter / staff Required: case_number Optional: None

Case management

Premium staff workflow for evidence review, audit trails, and publication control.

/case queue

List cases waiting for staff action.

Access: Staff Required: None Optional: status
/case view

View the complete private case summary.

Access: Staff Required: case_number Optional: None
/case find-user

Find cases by the reported user's Discord ID.

Access: Staff Required: discord_id Optional: None
/case find-reporter

Find cases submitted by a specific reporter.

Access: Staff Required: reporter Optional: None
/case claim

Assign an open case to yourself.

Access: Staff Required: case_number Optional: None
/case request-info

Mark a case as waiting for more information or evidence.

Access: Staff Required: case_number, request Optional: None
/case history

Show the audit history for one case.

Access: Staff Required: case_number Optional: None
/case export

Export the full private case, history, and evidence index as JSON.

Access: Staff Required: case_number Optional: None
/case edit-publication

Edit the public blacklist-feed title, summary, and category before publishing.

Access: Staff Required: case_number, title, summary, category Optional: None
/case preview

Preview exactly what an approved case will publish publicly.

Access: Staff Required: case_number Optional: None
/case publish

Publish an approved, reviewed case to the main feed or configured livefeed channels.

Access: Staff Required: case_number Optional: publish_to_all_feeds (defaults on)
/case merge

Close a duplicate case and link it to the original.

Access: Staff Required: case_number, original_case Optional: None

Evidence tools

Attach, inspect, download, and verify stored report evidence.

/evidence add

Attach a new evidence file to an existing report case.

Access: Staff Required: case_number, evidence, note Optional: None
/evidence case

List every evidence file linked to a report case.

Access: Staff Required: case_number Optional: None
/evidence download

Privately download one stored evidence file.

Access: Staff Required: evidence_id Optional: None
/evidence verify

Verify a file against its saved SHA-256 fingerprint.

Access: Staff Required: evidence_id Optional: None

Setup and admin

Configure servers, manage trusted staff, and review report decisions.

/setup server

Configure alerts, auto-actions, roles, and spam protection.

Access: Server admins Required: None Optional: alert_channel, auto_action, spam_protection, spam_action, blacklist_role, ping_role
/setup livefeed

Choose the channel where new approved reports should be posted automatically.

Access: Server admins Required: channel Optional: None
/setup announcements

Choose the channel where Blacklist Terminal announcements should be posted.

Access: Server admins Required: channel Optional: clear
/setup quarantine

Configure the quarantine role and channel permissions.

Access: Server admins Required: None Optional: None
/setup view

View the current server setup, live feed, and announcement configuration.

Access: Server admins Required: None Optional: None
/admin add

Add a co-admin who can manage reports.

Access: Owner Required: user Optional: None
/admin remove

Remove a co-admin.

Access: Owner Required: user Optional: None
/admin list

List all co-admins.

Access: Owner Required: None Optional: None
/admin transfer-owner

Transfer bot ownership to another user.

Access: Owner Required: user Optional: None
/case approve

Approve a pending user report.

Access: Staff Required: report_id Optional: None
/case reject

Reject a pending user report.

Access: Staff Required: report_id, reason Optional: None

Server safety

Manage approved guilds, blacklist dangerous servers, and run safety scans.

/guild approve

Approve a guild to submit reports.

Access: Owner Required: guild_id Optional: None
/guild remove

Revoke a guild's permission to submit reports.

Access: Owner Required: guild_id Optional: None
/guild list

List servers the bot is in.

Access: Owner Required: None Optional: None
/guild blacklist

Blacklist a guild and immediately kick the bot from it.

Access: Owner Required: guild_id, reason Optional: None
/guild unblacklist

Remove a guild from the blacklist.

Access: Owner Required: guild_id Optional: None
/guild blacklist-list

List blacklisted guilds.

Access: Owner Required: None Optional: None
/guild scan

Scan all servers and leave blacklisted guilds or guilds owned by blacklisted users.

Access: Owner Required: None Optional: None
/scanserver

Scan a server for known risk signals.

Access: Staff Required: None Optional: None

Moderation

Watchlist users, quarantine risks, lock down channels, and clean messages.

/watchlist add

Add a user to a server watchlist.

Access: Server admins Required: user Optional: reason
/watchlist remove

Remove a user from a server watchlist.

Access: Server admins Required: user Optional: None
/watchlist list

List users on the server watchlist.

Access: Server admins Required: None Optional: None
/quarantine

Strip a member's roles and assign the quarantine role.

Access: Server admins Required: member Optional: reason
/unquarantine

Restore a quarantined member's saved roles.

Access: Server admins Required: member Optional: None
/lockdown

Lock a channel, category, or entire server while saving restore state.

Access: Server admins Required: None Optional: channel, reason
/unlockdown

Restore a locked channel or all locked channels.

Access: Server admins Required: None Optional: channel
/purge messages

Delete a number of recent messages.

Access: Server admins Required: amount Optional: None
/purge user

Delete recent messages from one member.

Access: Server admins Required: user Optional: amount
/purge word

Delete recent messages containing text.

Access: Server admins Required: word Optional: amount
/purge channel

Delete up to 1,000 recent channel messages.

Access: Server admins Required: None Optional: amount

Premium and intelligence

Premium access, appeals, notes, and risk-intelligence commands.

/premium grant

Grant premium access.

Access: Owner Required: user Optional: duration
/premium revoke

Revoke premium access.

Access: Owner Required: user Optional: None
/premium list

List premium users or servers.

Access: Owner Required: None Optional: None
/appeal

Submit or manage a blacklist appeal.

Access: Users Required: None Optional: None
/note add

Add a private staff note for a user.

Access: Staff Required: discord_id, note Optional: None
/note remove

Remove a private staff note.

Access: Staff Required: note_id Optional: None
/note list

List private staff notes for a user.

Access: Staff Required: discord_id Optional: None
/botscan

Scan bot or account risk signals.

Access: Premium / staff Required: None Optional: None
/risk user

Check user risk indicators.

Access: Premium / staff Required: None Optional: None
/risk server

Check server-level risk indicators.

Access: Premium / staff Required: None Optional: None
/lookup

Look up stored intelligence.

Access: Premium / staff Required: None Optional: None
/risk multi

Check multiple users at once.

Access: Premium / staff Required: None Optional: None
/relatedusers

Find related users or linked risk signals.

Access: Premium / staff Required: None Optional: None
/invitescan

Scan Discord invites for risk.

Access: Premium / staff Required: None Optional: None
/globalchat

Global admin communication tool.

Access: Staff Required: None Optional: None
/ownerchat

Owner communication tool.

Access: Owner Required: None Optional: None
/staff announce

Post an announcement locally or to all configured announcement channels.

Access: Blacklist staff Required: title, message Optional: channel, mention_role, publish_to_feeds

Config Reference

All /setup server options and their defaults. Settings are per-server and can be changed at any time.

alert_channel

The text channel where the bot posts blacklist alert embeds when a flagged user is detected joining. If not set, defaults to the server's system channel. If no system channel is configured, the bot uses the first text channel it has permission to send in.

auto_action

The automatic action taken when a blacklisted user joins your server:

noneAlert only - no automatic kick or ban. Default setting. Recommended for first setup.
kickAutomatically kick the user from your server when detected. They can rejoin, but will be flagged again.
banAutomatically ban the user from your server when detected. Recommended for high-security servers.
roleAssigns the configured blacklist_role to the user instead of kicking or banning. The user remains visible in the member list with restricted access - moderators can review and act manually. Requires blacklist_role to be configured first.
blacklist_role

A role to assign to users who are detected as blacklisted when they join. Useful for restricting access without a full kick or ban - lets you review the user before taking action.

ping_role

A role to ping in the alert embed when a blacklisted user is detected. Useful for notifying your moderator team immediately. Leave unset to send alerts without a ping.

watchlist_ping_role

A role to ping when a watchlisted user joins your server. Separate from ping_role so you can route blacklist and watchlist alerts to different team members.

spam_protection

Enable or disable the built-in anti-spam / raid protection system. When on, the bot monitors for rapid-fire message spam and triggers the configured spam_action automatically.

onSpam detection active. Monitors for high-frequency message bursts.
offSpam detection disabled. Default setting.
spam_action

The action taken automatically when spam is detected (requires spam_protection to be on):

muteTemporarily mute the user when a spam burst is detected. Least disruptive option.
kickKick the user from the server when spam is detected.
banPermanently ban the user when spam is detected. Recommended for raid scenarios.

Permission Levels

Blacklist Terminal uses three permission levels to control access to commands.

Everyone

Any server member who can use slash commands. Can run /checkuser, /listusers, and /userstats.

Moderator

Users with the Manage Server Discord permission. Can run /report user to submit reports and /setup server or /setup livefeed to set up the bot.

Admin

Bot admins granted by the bot owner. Can approve and reject pending reports (/case approve, /case reject) and view evidence files (/listevidence).

Frequently Asked Questions

Common questions about how Blacklist Terminal works, what it stores, and what to expect.

Is Blacklist Terminal free to use?
Core protection is free for all servers - join alerts, /checkuser, /listusers, /report user, watchlist, quarantine, notes, and /risk multi (up to 3 IDs) are available at no cost. A Premium tier unlocks advanced commands: /risk user, /risk server, /lookup, /botscan, /lockdown, /unlockdown, and expanded /risk multi (up to 10 IDs). Network features (/ownerchat) are free for approved partner servers. Subscriptions help cover hosting, but you never need to pay to use the core bot.
What permissions does the bot need?
Blacklist Terminal requests Administrator permission during the invite flow. This allows it to kick or ban users when auto-action is enabled, post alerts in any channel, and respond to all slash commands.
How do I report a user to the network?
Use /report user with the user's Discord ID, a clear reason, and optionally up to 5 evidence files (screenshots, video). You need the Manage Server permission. Reports go into a review queue and are not public until an admin approves them.
What happens after I submit a report?
Your report enters the admin review queue. Admins review the reason and evidence before any action is taken. If approved, the user is added to the global blacklist and all connected servers are notified instantly. If rejected, your server receives a notification with a reason.
My report was rejected - can I resubmit?
Yes, if you have new or stronger evidence. Resubmitting the exact same report without additional evidence will likely be rejected again. Read the rejection reason carefully before resubmitting.
How do I set up alerts in my server?
Run /setup server and set an alert_channel and your preferred auto_action (none, kick, ban, or role). Use /setup livefeed to choose where approved reports are posted. You can update settings at any time.
Does the bot read messages or monitor my server?
No. Blacklist Terminal only checks users against the blacklist when they join your server. It does not read, store, or monitor message content. The only data stored is Discord user IDs, report details, and per-server configuration.
What if I believe someone was wrongly blacklisted?
Anyone can submit an appeal through the Blacklist Terminal contact form. Appeals are reviewed by the admin team and typically resolved within 48–72 hours. See the Trust Center for the full appeal process.