Connections to other servers

A connection links one of your servers with a server that belongs to another project. Roles on one server decide who gets roles on the other. Both owners agree, nobody needs access to the other's dashboard, and either side can end it at any time.

Use it when two communities that don't share a network still want to treat each other's members as friends — for example "everyone with Staff on server A gets Guest on server B".

Who does what

A connection has two sides:

• Receives roles. Members of the other server get roles on this server. This side releases the roles that may be handed out. Nothing else on this server is touched.
• Roles count. The roles on this server decide who gets roles on the other server. This side builds the rules.

Each side needs Manage Server on its own server. CloudMod checks that live at Discord whenever you create, accept or change something.

Set one up

1. Open Connections (under Network & Sync) and choose New connection.
2. Pick what your server should do — receive roles, or let its roles count — and which of your servers it is. Create invitation shows a one-time code. It is valid for 7 days and is displayed only once.
3. Send the code to the owner of the other server. They open Connections, choose Enter a code, pick their server and Accept. Their server takes the opposite side.
4. The receiving side opens Release roles and picks the roles that may be handed out (up to 25).
5. The other side opens New rule: if a member has certain roles on their own server, then add or remove released roles on the other. Rules use the same conditions as Role Rules and can be switched on and off, but they can only name released roles.

Members get their roles when their roles change, when they join either server, and in a regular full check every 30 minutes.

What can't be released

• @everyone.
• Roles managed by Discord or an integration (bots, boosters).
• Roles with Administrator or management permissions (Manage Server, Manage Roles, Manage Channels, Manage Webhooks, Ban Members, Kick Members).

Why: the other side hands released roles out automatically, to everyone who matches its rules. A role that can manage your server or its members would give someone else that power on your server.

The Release roles window greys these roles out and says why, and it lists what every role you pick can do (for example Moderate Members). It can't show channel access a role gets through channel permissions — check that in Discord before you release a role.

If a released role later gets one of these permissions, CloudMod stops handing it out. A role can be released on one connection at a time, and it can't be a target of one of your own rules or role links while it is released.

What the other side sees

Only the server name and the names of released roles. Never your project, your network, your account or the people behind it. The rules and the roles they look at are visible to the side that built them only. Role changes are logged in the log channel of the receiving server and never name the other side.

What a connection does not do

A connection moves the released roles and nothing else. It does not share a plan, add-ons or plugins, it does not make a server a sub-server, and it does not sync nicknames or bans. Each side keeps its own project, its own plan and its own limits. Rules count toward the rule limit of the side that builds them.

End a connection

Either side can end it from End connection. The rules stop working right away. By default CloudMod takes back the roles it handed out from everyone who still has them; tick Keep the roles that were already handed out to leave them as they are. Roles an owner handed out by hand, outside the rules, always stay.

Ended connections stay in the list for 7 days. Use Remove from list on an ended connection to delete it right away. It disappears for both sides, and no roles change. That works once CloudMod has finished taking back the handed-out roles. Otherwise CloudMod deletes ended connections — with their released roles and rules — 14 days after they ended, and an invitation nobody accepted 7 days after it expired.

A connection also ends when one of its servers leaves its network or project. If the server that builds the rules leaves, the handed-out roles are taken back as above; if the receiving server leaves, nothing is changed on it.

When a role doesn't arrive

• The role is above CloudMod's own role in the receiving server's role list, or CloudMod lacks Manage Roles there. Move CloudMod's role up. The rule shows Needs attention on the building side.
• Either project is in test mode (dry run): CloudMod only reports what it would do and changes no roles. The Connections page of a project in test mode says so. Switch it to live in the project settings.
• The member is still waiting at the receiving server's verification gate — they get the role once they pass it.
• The member has an open account age review on either side.
• CloudMod isn't on both servers, or a server is no longer part of its project.

See also Main server vs. sub-server for how networks differ from connections.