Add sub-servers and role rules
Add sub-servers and build role rules that give or take roles across your network.
On the Sub-Servers page, click Add sub-guild for every server that should receive synced roles. Pick the server from the list — that's it.
You need access to the project and the Manage Server (or Administrator) permission on the server you add. The list shows the servers from your own Discord account: a server where you lack the permission is marked Not an admin and can't be picked, and CloudMod's bot has to be on it already. A project admin therefore needs Manage Server on each server they add, not on the main server. A server can also be a sub-server of one network only.
The optional anchor role (Advanced: set membership anchor) is for roleplay / faction setups only — leave it off for normal sub-servers. With Role Rules it is not used — then the Membership anchor switch in Project settings decides. See Anchor role.
Create role rules
Open Role Rules → New rule:
- Give it a Rule name — only you see it.
- Under If a user…, pick the condition in Check (for example Has at least one of these roles), the server it's Checked on and the Roles. Add more with Add AND condition — all of them must be true at once.
- Under Then…, pick the Action (Add roles or Remove roles), the target server (On server) and the Roles. Add action adds another one.
- Set a Priority if two rules could disagree about the same role — the higher number wins.
- Click Create rule.
A rule keeps checking: when the condition stops being true, the role it gave goes away again. Conditions and actions can use any server in your network, not just the main server.
A rule can hand out any role CloudMod is able to assign — including one that carries Administrator, Manage Server or Ban Members on a sub-server. Everyone the rule matches gets those permissions there. The role picker marks such roles with a shield and names the permissions; it warns, it doesn't block. Only people you trust should edit rules, and a sub-server owner should know which roles the network may hand out on their server.
A rule keeps checking, so it can't take away the very role its own condition is waiting for. If a user has Member → remove Member, add Account Review cancels itself: once Member is gone the condition is false, so Account Review would go away again and Member would come back. CloudMod refuses to save such a rule and tells you why. Check a role the rule doesn't touch instead — for example If a user has New → remove Member, add Account Review.
While a member holds the review role of the Account Age Filter, rules skip them: nothing is added, nothing is removed. A rule like If a user has Account Review → add Member never fires. The member gets their roles after you press Approve.
Before switching a rule on, use the Test tab: pick some roles and see exactly what would be added or removed. Nothing is written. Older one-to-one mappings stay under Classic links and keep working alongside your rules.
Once Dry-Run is off, the next role change on any server in the network is synced right away.