Main server vs. sub-server

The main server is your central Discord — where the project lives, where your admin role and log channels are, and where most settings point. Sub-servers are the other servers in your network that CloudMod keeps in sync with it.

How roles flow

With Role Rules, every server can be a source: anyone holding a source role gets the target roles on the other servers, and loses them again once no source role supports them. That keeps servers from drifting apart. The sync only ever adds or removes target roles — roles that aren't the target of a rule are never touched.

On older, mapping-based projects, roles flow from the main server to the sub-servers. If an admin manually removes a synced role on a sub-server, CloudMod removes it on the main server and all other sub-servers too.

When each sync runs, how fast it is and what the periodic check does: How the sync works.

Nicknames

With Sync nicknames on (Project settings → Server setup → Network), nicknames sync both ways: a change on the main server goes to every sub-server, and a change on a sub-server goes to the main server and from there to all other sub-servers. Each sub-server can opt out on the Sub-Servers page. All the details: Nickname sync.

Just one server?

You don't need sub-servers. Pick Single server under Project settings → Server setup and CloudMod runs on that one server without any cross-server sync.

One server, one network

A server can be a sub-server of one network at a time, never of two. It can also have its own Single server project on top of that: some plugins, such as Tickets and Welcome, work on a project's main server, so a sub-server that wants them registers itself as a single server. That project has its own plan and plugin slots, separate from the network's, and it can't be switched to Server network while the server is a sub-server.

Two communities, one shared server

Say you run Server A and Server B, and both should hand out a role on a shared Server C. You can't connect C to two separate projects, because a server is a sub-server of one network only. Use one network instead:

1. Make A the main server (Project settings → Server setup → Server network).
2. On Sub-Servers, add B and C.
3. On Role Rules, create one rule per community. Under If a user… pick Has at least one of these roles, the role all members of A hold, Checked on A. Under Then… pick Add roles, the role "Guild A", On server C. Repeat it for B.

The rules are independent. Someone who is on both A and B gets both roles on C. Someone who leaves A loses "Guild A" on C and keeps "Guild B". Two things to know:

• A rule checks for a role on the source server, not for membership. If your members don't share a role yet, create one, for example "Member".
• CloudMod only touches roles that are the target of a rule, so every other role on C stays as you set it. "Guild A" itself belongs to its rule: if you give it by hand to someone who isn't on A, the next sync takes it away again. Use a separate role, such as "Guest", for manual assignments.

Different people own the servers? Whoever adds a server to a network needs access to the project and the Manage Server (or Administrator) permission on the server being added. CloudMod checks this against that person's own Discord permissions, so access to the project alone is never enough. If another person owns Server B, that person has to add it themselves: invite them as a project admin (Project settings → project admins, using their Discord ID), have them invite the CloudMod bot to B, and let them add B under Sub-Servers. A project admin can see and edit everything in the project, including all rules and sub-servers, but cannot delete the project or change the admin list. Only do this with someone you trust.

A new network starts in test mode. Check who a rule would touch on the Test tab of Role Rules first, then switch test mode off. B can still run Tickets or Welcome on its own as described above. The details of the rules are in Add sub-servers and role rules.