Anyone running a Discord network of multiple servers knows the pattern: a troublemaker gets banned on server A — and reappears on server B two minutes later. Each server has its own ban, each must be maintained individually. Cross-server bans solve exactly that.
The problem with isolated bans
Discord bans apply per server. In a network that means your mod team potentially has to ban the same troll manually on every single server. With five or ten servers that is error-prone and slow — precisely the gap repeat offenders exploit.
How network-wide bans work
With ban sync enabled, a single ban on your main server is enough. CloudMod automatically enforces it on every sub-server in the project. Lift the ban on the main server and the network bans are removed there too. The direction is main → sub only: a ban a sub-server places stays on that server, so a sub-server moderator can't lock someone out of your whole network.
Built-in safeguards
A network-wide ban is powerful, so there are clear limits. Never banned automatically:
- Server owners
- Members with the Manage Server permission (admins)
- The bot itself
- Members with a role higher than the bot
That way a single compromised server cannot lock out the moderators of the rest of the network.
Opt-in per project
Because bans are destructive, the feature is off by default. You enable it per project in the project settings — the moderation docs show the switch and every exemption. Requirement: the bot needs the Ban Members permission on every server. If it is missing somewhere, CloudMod reports it in the logs instead of failing silently.
Who benefits
Roleplay networks, esports organizations and creators with several topic servers benefit most. Anywhere the same person can cause damage across multiple servers, a network-wide ban saves real mod time — and shuts the door before the troll finds it again.