You have a partner community — two creators, allied clans, a game server and its fan server. Members of one should be recognised on the other: everyone with Staff over there gets Guest over here. Discord has no way to do that between two separate servers. The usual workaround is to make the other owner an admin of your setup, and then they can see everything you configured.
A connection is the cleaner way. Both owners agree, only the roles you choose are ever touched, and nobody gets access to the other side's settings.
How a connection works
A connection links one server of yours with one server of another CloudMod project. Each side has a job:
- Receives roles. Members of the other server get roles on this server. This side decides which roles may be handed out.
- Roles count. The roles on this server decide who gets roles on the other. This side builds the rules.
Each owner needs Manage Server on their own server, and CloudMod checks that live at Discord whenever someone creates, accepts or changes something.
Set one up in four steps
- Create an invitation. Open Connections in your project, choose whether your server receives roles or lets its roles count, and pick the server. You get a one-time code that is shown once and works for seven days.
- The other owner accepts. They open Connections, enter the code and pick their server. It takes the opposite side automatically.
- Release the roles. The receiving side picks the roles that may be handed out — up to 25.
- Build the rules. The other side writes them the same way as conditional role rules: if a member has these roles on my server, give those released roles on yours.
Roles arrive when someone's roles change, when they join either server, and in a regular full check every few hours.
What stays in your hands
- Only released roles move.
@everyone, roles managed by Discord or an integration, and any role with Administrator or management permissions can never be released. If a released role later gains one of those permissions, CloudMod stops handing it out. - The other side stays a stranger. It sees your server name and the names of the roles you released — never your project, your network or your account.
- Nothing is shared by accident. A connection does not share a plan, add-ons or plugins, it does not turn a server into a sub-server, and it does not sync nicknames or bans. It is available on every plan; the rules count toward the rule limit of the project that builds them.
Ending it
Either side can end a connection at any time and the rules stop working right away. By default CloudMod takes back the roles it handed out from everyone who still has them. If you would rather keep them, tick Keep the roles that were already handed out when you end it.
When a role does not arrive
The usual causes are small: the role sits above CloudMod's own role in the receiving server's list, CloudMod lacks Manage Roles there, the receiving project is in test mode, or the member is still waiting at a verification gate. The connections guide has the full list.
Two servers inside one network work differently — that is role sync. For servers that belong to different people, Connections is the tool.