Cross-Server Actions
RoleLogic can manage roles across multiple Discord servers, not just where you create the rule.
What Are Cross-Server Actions?
Normally, rules work within one server. Cross-server actions let you:
- Check roles in Server A
- Add/remove roles in Server B
Use Cases
Server Networks
When someone gets "VIP" in Main Server, add "VIP-Access" in Lounge Server.
Partner Programs
When someone gets "Partner" in Server A, add "Partner-Badge" in Servers B, C, and D.
Organization Sync
When an employee gets "Team-Lead" in HR Server, add "Leadership-Access" in all department servers.
Requirements
- RoleLogic in all servers — Bot must be present with "Manage Roles" permission
- Proper hierarchy in each server — Bot's role above managed roles
- Member in both servers — Actions only work for members in both
Setup
- Open rule editor in your primary server
- Configure condition as usual
- In action section, look for roles from other servers
- Select cross-server roles
- Save
How It Works
- Member's role changes in Server A
- RoleLogic evaluates condition
- If matched, attempts role change in Server B
- Checks if member exists in Server B
- Checks hierarchy permissions in Server B
- Applies changes
Linked Guilds View
Dashboard shows Linked Guilds section:
- Servers your rules can affect
- Manage connections
- Purge option to remove all cross-server actions for a server
Limitations
- Member must be in both servers — Actions silently skip otherwise
- Quota limits — Cross-server uses role slots from quota
- Hierarchy per server — Bot may manage roles differently in each server
- Bidirectional setups — Be careful to avoid loops
Example Setup
Goal: VIP in Main → Lounge Access in VIP Lounge
- Ensure RoleLogic is in both servers
- Open dashboard for Main Server
- Create rule:
- IF: Has Some Roles → Premium
- THEN: Add Roles → Lounge Access (from VIP Lounge server)
- Save
Result: Anyone with "Premium" in Main gets "Lounge Access" in VIP Lounge.
Troubleshooting
"Bot and User Not in Guild"
- Member isn't in target server, or
- RoleLogic isn't in target server
"Cannot manage role due to hierarchy"
- RoleLogic's role too low in TARGET server
- Adjust hierarchy in that server
Actions not working?
- Check "Manage Roles" permission in target server
- Verify hierarchy in target server
- Confirm member is in both servers
Related
- Testing Sandbox — Test cross-server rules
- Plans & Pricing — Cross-server quota limits
- FAQ — Cross-server troubleshooting