Mod Network
Link servers together to share bans, warnings and watchlists between moderation teams.
Overview#
A Mod Network links several servers so their moderation teams can see each other's records. When a linked server bans someone, your moderators get an alert with the reason and the source server, and decide for themselves whether to apply it here. You can look a user up across every linked server before you promote them, and be warned when someone with a record joins.
Nothing is shared automatically the moment you connect. Every server chooses what it contributes, what it receives, and, server by server, who it will exchange data with at all.
Mod Network may not be available on every server yet. See Beta Features if you cannot find it in your dashboard.
What a Network Is#
A network is a named group of servers with one owner server. The owner holds the invite code and approves every server that asks to join. Any member server can leave at any time; only the owner can disband the whole network.
Being in a network does not, by itself, share anything. Each member server has its own sharing settings, and data only flows where both sides allow it.
How to Set Up#
- Go to the dashboard and select your server
- Navigate to the Mod Network section
- Either create a network (give it a name, and this server becomes its owner) or join one by pasting an invite code from another server's owner
- If you created it, share the invite code with the admins of the servers you want in, then approve each request as it arrives
- Set up a network log channel so incoming ban alerts appear in Discord and not only on the dashboard
- Choose this server's sharing mode and turn on the record types you are willing to share
- Optionally tighten things per server under Per-server sharing
Joining Is a Request, Not an Entry#
Joining with an invite code puts your server in a pending state. No moderation data flows in either direction until the network owner approves the request. The same is true from the owner's side: a pending member neither sees nor contributes anything.
Sharing Modes#
Every member server picks one mode for each network it belongs to:
| Mode | Behavior |
|---|---|
| Both ways | Share this server's data and receive from linked servers |
| Broadcast | Share data outward but receive no alerts or lookups |
| Receive | Get alerts and lookups without sharing anything |
What Gets Shared#
Within your chosen mode, you decide which record types leave this server:
| Setting | Description |
|---|---|
| Share bans | Let other members see and mirror bans issued in this server |
| Share warnings | Show this server's active warnings in linked-server lookups |
| Share watchlist | Show this server's user monitors in linked-server lookups |
| Screen joins | Alert when a joining user has records in linked servers |
| Auto-apply bans | Apply incoming network bans immediately without moderator review |
Moderator identities are never shared. A lookup shows what happened and where, not who did it.
Per-Server Sharing#
Beyond the network-wide mode, you can switch Send or Receive off for one specific server, useful when you trust most of a network but not all of it. If either side turns a direction off, that direction stops; there is no way to override the other server's decision.
How a Ban Travels#
This is the part worth being precise about: a ban in one server does not ban the user in yours. It creates something your moderators act on.
- A moderator bans someone in a linked server
- Every server that receives from it gets a pending ban alert
- The alert is posted to your network log channel with Apply Ban and Dismiss buttons, and appears in the Incoming ban alerts list on your dashboard
- Nothing happens to the user in your server until one of your moderators presses Apply Ban (from Discord or from the dashboard, they do the same thing)
- Dismiss closes the alert without banning. A dismissed alert stays dismissed and is never raised again
The alert carries the user, the server that banned them, the network it came through, and the reason. When a ban is applied here, it is recorded locally with the network and its original reason, so the ban list shows where it came from.
An alert can only be resolved once. If two moderators press Apply at the same time, the second one is told it was already handled rather than the ban being applied twice.
Auto-Apply#
Auto-apply bans is the exception, and it is off by default. With it enabled, incoming network bans are applied straight away and the log channel gets a notice: no buttons, because there is nothing left to decide.
If the automatic ban fails, most often because the bot lacks the ban permission or sits too low in the role list, the alert falls back to the normal Apply/Dismiss message so your moderators can still act on it.
If You Have No Log Channel#
Without a network log channel, incoming ban alerts only appear on the dashboard. The dashboard offers to create the channel for you when it notices one is missing.
Join Screening#
With Screen joins on, the bot checks every new member against the linked servers and posts a summary to the network log if they have any records (bans, active warnings, or watchlist entries), showing which server each came from.
Screening is informational only. It never blocks a join and never acts on its own; your moderators decide what to do with it.
Looking a User Up#
/lookup checks a user's active bans, warnings and watchlist entries across the servers linked to yours and replies privately. The same search is available on the dashboard by Discord user ID.
A clean result says so explicitly, which is just as useful as a hit when you are deciding whether to hand someone a role.
Slash Commands#
| Command | What it does |
|---|---|
/network create | Creates a network with this server as its owner and returns the invite code |
/network join | Requests to join a network with an invite code: pending until the owner approves |
/network info | Lists the networks this server belongs to, their members, and who is still pending |
/network leave | Leaves a network. The owner server cannot leave; disband it from the dashboard instead |
/lookup | Checks a user's records across the linked servers |
Creating, joining and leaving require the Administrator permission. Viewing network information and running lookups require the Moderate Members permission.
Managing the Network#
From the dashboard, the owner server can:
- Approve or remove member servers
- Copy the invite code, or rotate it: rotating stops the old code working immediately
- Disband the network, which removes shared visibility for everyone at once
Every member server can leave on its own, which stops shared visibility immediately in both directions.
Tips#
- Only link servers whose moderation standards you actually trust. A network is a statement that another team's judgement is good enough to act on.
- Leave auto-apply off unless the network is small and tightly trusted. The review step exists because one server's ban reason is not always another server's banning offence.
- Set up the network log channel before you invite anyone. Alerts that only exist on the dashboard get missed.
- Start in Receive mode if you are joining an established network. You get the benefit immediately and can start sharing once you are comfortable.
- Write ban reasons for strangers. Your reasons are read by moderators in other servers with no context at all, so "raid: posted scam links in 6 channels" beats "you know what you did".
- Use per-server sharing instead of leaving when one member of a network is the problem. You keep the rest of the network and cut off just that link.
- Rotate the invite code whenever a member server leaves or the code has been posted somewhere public.
- Run
/lookupbefore promotions, not just when someone is causing trouble. A clean check takes seconds.