The optional anchor role on sub-servers
When an anchor role makes sense — and when to leave it off.
By default a sub-server is a pure sync target — roles flow in, nothing flows out. This fits 90% of communities.
What the anchor does
With an anchor, leaving a sub-server costs a member their role on the main server too — which cascades to every other sub-server. In short: leaving the sub-server = losing the faction.
It kicks in when a member leaves, is kicked from or is banned on that sub-server. CloudMod then removes the roles (usually on the main server) whose rules point into that sub-server, and cleans up every role that depended on them across the network.
If one main-server role has rules into many servers, leaving just one of them removes it — and with it the roles it gave everywhere else.
How to turn it on
It depends on whether your network uses Role Rules:
| Your network | What you set | What happens on leave |
|---|---|---|
| With Role Rules | Project settings → Server setup → Advanced → Membership anchor (role graph) (off by default) | The main-server roles whose rules point into that sub-server are removed, plus everything that depended on them. |
| Without Role Rules (older one-to-one links) | An Anchor role on the sub-server — Advanced: set membership anchor when adding it | That anchor role is removed on the main server and on all sub-servers. |
With Role Rules, the per-server anchor role isn't used — only the switch counts. Without Role Rules, the anchor role works on its own; the switch changes nothing there.
The Sub-Servers page shows, next to each server with an anchor role, which of the two applies.
When to use it
Only use it for tight-coupled setups like roleplay factions (e.g. "leaving the Police server should remove the Police role everywhere"). For gaming channels, booster-only servers or regional sub-servers — leave the anchor off.