🔨Moderation

The Moderation page holds the settings behind FiveUnity's member-facing safety tools: where ban evidence is filed, which roles survive a member leaving, the verify gate on your front door, and the status blacklist. Your staff's day-to-day moderation commands in Discord are covered here too.

#Ban logs and sticky roles

Sticky roles solve the oldest trick in the book: leaving the server to shed a punishment role. When a member leaves, FiveUnity saves any of these roles they were holding; when they come back, it puts them straight back on and clears the saved copy. Roles that are not on the list are not saved.

You can manage the same list from Discord:

• /stickyrole add role:@Role: make a role sticky.
• /stickyrole remove role:@Role: stop tracking it.
• /stickyrole list: show the current list.

#Verification

Verification puts a Verify button in a channel. A member clicks it, gets your verified role, and loses the unverified role in the same step.

Two pages edit the same verification settings, so pick the one that suits what you are doing:

• This page is where you set the channel, the verified role, the unverified role and the welcome DM.
• Dashboard → Server setup → Core settings → Booster & verification has the same fields plus a Post verification panel button that publishes or updates the panel message in the chosen channel. See Core settings.

In Discord, /verification setup posts a verify panel in the channel you run it in and switches verification on. It refuses to post if no verified role has been chosen yet.

#Queen verification

Where the Verify button above is pressed by the member themselves, /queenverify is run by a staff member on somebody else: they name a member, that member gets one role, the channel sees a message saying so, and the pair of names goes to a log channel. Communities use it for the checks a button cannot do.

Both messages take the same placeholders: {verifier} becomes the staff member, {user} the member verified, {role} the role given and {server} your server name. Square brackets work as well, so [user] this queen has been verified. does the same thing as the curly form. Anything FiveUnity does not recognise is left as you typed it.

Only the verified member is pinged by the announcement. A role mention or an @everyone in the template is posted as text and notifies nobody.

The log entry names the member, who verified them, the role given and the channel the command was run in, so "who verified who" is answerable months later. It is separate from the shared Command log on purpose: verification lists are usually read by a smaller group than the one that reads every staff command.

Nothing is DMed to the member, and the command refuses a member who already holds the role, so running it twice cannot double-post or double-log somebody.

#Status blacklist

The status blacklist is built around a Quarantined role and a single quarantine channel, for members whose Discord custom status carries something you do not allow.

/blacklist setup in Discord builds the whole thing for you: it creates a Quarantined role with no permissions, creates a 🚨-quarantine channel that only that role can see (read-only), denies View Channel to the Quarantined role on every existing category, and turns the system on. It reports how many categories it hid.

The quarantine channel opens with a notice explaining to the member why they are there and telling them that access returns once the prohibited words are removed from their custom status.

The rest of the list is managed with /blacklist add word:…, /blacklist remove word:…, /blacklist list and /blacklist toggle. Words are stored in lower case and matched without regard to case.

#The moderation toolkit in Discord

Who can run each of these is set in Dashboard → Server setup → Permissions; see Permissions. Full option lists are in Moderation commands.

#Bans that reach further than one server

Two options on /ban cover the bans you cannot place with a right click:

• userid: bans a Discord user ID. The account does not have to be in your server, or to have ever been in it, so somebody named in an intelligence share can be turned away at the door rather than after they arrive.
• cross:Yes repeats the ban in every side Discord linked to this one, on the PRO plan. Run it on the main server; a side Discord is refused, because banning across the network is not one department's call. The reply names each linked Discord and what happened there, every ban that lands opens a case in that Discord credited to you, and /massunban ... cross:Yes lifts the lot again. See Linked servers.

/massban is the same thing for a whole list: up to 100 IDs a run, the same per-ID checks, the same cross:Yes, one report at the end. Nobody on a mass list is DMed.

#Mass ban on the website

Dashboard → Safety → Moderation → Mass ban is the one place on the website that acts on members instead of settings. It exists for the job a slash command is a poor fit for: pasting a long list of IDs out of a spreadsheet, a partner community's ban list or an intelligence share, and reading the outcome as a table.

It is Administrator-only. Manage Server opens every other page on the dashboard and is refused here, because a ban list is not a setting. The panel does not even appear for anyone else, and the bot refuses the request whether or not it appeared.

Everything else matches /massban exactly, because it is the same code: the same 100 per run, the same hierarchy checks, the same Also ban in linked Discords switch on the PRO plan, and a case opened in each server crediting the admin who pressed the button. There is no undo button on the website: lift a mass ban with /massunban in Discord.

When FiveUnity cannot act (the member sits above it in the role list, or a permission is missing) it says which of the two is the problem instead of failing quietly. /purge skips messages older than 14 days, because Discord will not bulk delete them.

#Cases

Every ban, kick, warn, timeout and lifted timeout opens a numbered case. Numbering starts at 1 and is per server, and two moderators acting at the same instant can never be handed the same number. The command reply quotes the number back to you.

There is no /case command: case lookup lives under /modlogs:

• /modlogs user user:@Member: the member's full history with per-action totals.
• /modlogs case number:42: one case in full, including its source and any evidence links.
• /modlogs recent action:ban: the server's latest actions, optionally narrowed to one kind.

Bans and unbans placed straight from the Discord client are picked up too and marked as coming from the Discord client, so they are not missing from the ledger. An action taken with /ban is not double-recorded. /ban-evidence attaches any web links from the evidence box to the case, so /modlogs case shows them inline.

Every case is also readable on the website. See Staff. Automod actions land in the same ledger; see Protection.

#What gets logged where

FiveUnity writes to the log channels you set in Dashboard → Server setup → Core settings → Logging channels:

• Member log: bans, unbans, kicks, joins and leaves.
• Command log: a summary line for /warn, /kick, /timeout and /untimeout, including the case number, the moderator and the reason.
• Staff log: /purge, and gang strikes.
• Ban log channel: /ban-evidence evidence only, from this page.
• Verification log channel: /queenverify, from this page. Its own channel rather than one of the shared ones.

Whether a moderation DM actually reached the member is recorded too, so you can tell the difference between "they were told" and "their DMs are closed".

#DMs to the member

/ban, /kick, /warn and /timeout all DM the member first, with the reason and (for a timeout) how long it lasts and when it expires. /untimeout does not send a DM. If a member has DMs closed the action still goes ahead; only the notification is lost.

#Related

• Protection: automod filters, anti-raid and anti-nuke.
• Staff: the same case ledger on the website, plus gang strikes and staff metrics.
• Moderation commands
• Permissions
• Core settings