Skip to main content

Cross-Server Actions

RoleLogic can manage roles across multiple Discord servers, not just the one where you create the rule. This powerful feature enables coordination across server networks.

What Are Cross-Server Actions?​

Normally, rules check conditions and perform actions within the same server. Cross-server actions let you:

  • Check a member's roles in Server A
  • Add or remove roles in Server B

This bridges servers together, allowing unified role management across your Discord presence.

Use Cases​

Server Networks​

If you run multiple related servers (gaming clans, educational communities, content creator hubs), cross-server actions help coordinate member status across all of them.

Example:

When a member gets "VIP" in the main server, automatically add "VIP-Access" in the lounge server.

Partner Programs​

Manage partner benefits across communities:

Example:

When a member gets "Partner" in Server A, add "Partner-Badge" in Server B, Server C, and Server D.

Organization-Wide Roles​

Companies or groups with multiple Discord servers can sync roles across all of them:

Example:

When an employee gets "Team-Lead" in the HR server, add "Leadership-Access" in all department servers.

Event Coordination​

Run events that span multiple servers:

Example:

When a member gets "Event-Winner" in the event server, add "Champion" in the community server.

How It Works​

Prerequisites​

Before using cross-server actions:

  1. RoleLogic must be in all involved servers: The bot needs to be present and have "Manage Roles" permission in every server you want to affect.

  2. Proper role hierarchy in each server: RoleLogic's role must be above any roles it needs to manage, in every server.

  3. The member must be in both servers: Cross-server actions only work for members who belong to both the source and target servers.

Setting Up Cross-Server Actions​

  1. Open the Rule Editor in your primary server
  2. Configure the condition as usual (checking roles in this server)
  3. In the action section, look for the server selector or role list that shows roles from other servers
  4. Select roles from other servers where RoleLogic is present
  5. Save the rule

Behind the Scenes​

When a rule with cross-server actions triggers:

  1. RoleLogic detects the member's role change in Server A
  2. It evaluates the condition based on their roles in Server A
  3. If matched, it attempts to add/remove roles in Server B
  4. It checks if the member exists in Server B
  5. It checks role hierarchy permissions in Server B
  6. It applies the role changes

The Linked Guilds View​

RoleLogic provides a Linked Guilds section to help you manage cross-server relationships.

What You'll See​

  • A list of servers that your rules can affect
  • Server icons, names, and IDs
  • Options to manage the connections

Purge Function​

If you need to remove all cross-server actions for a specific linked server:

  1. Go to Linked Guilds
  2. Find the server you want to disconnect
  3. Click "Purge"
  4. Confirm the action

This removes all role actions targeting that server from your rules, but doesn't delete the rules themselves.

Limitations and Considerations​

Member Must Be in Both Servers​

Cross-server actions only work when the member exists in both the source and target servers. If a member is only in one server, the action silently skips (it doesn't cause an error).

Quota Limits​

Cross-server actions consume role slots from your quota:

  • Free plans have limited cross-server capacity
  • Premium plans expand this limit

Role Hierarchy Per Server​

Role hierarchy is enforced separately in each server. RoleLogic might be able to manage a role in Server A but not in Server B, depending on its position in each server's role list.

Bidirectional Setups​

You can create rules that work in both directions:

  • Rule in Server A: affects Server B
  • Rule in Server B: affects Server A

Be careful with bidirectional setups to avoid loops or unexpected cascades.

Example Setup​

Scenario: VIP Sync Across Two Servers​

Server A: Main Community Server B: VIP Lounge

Goal: When someone gets "Premium" in the main community, give them "Lounge Access" in the VIP lounge.

Setup:

  1. Ensure RoleLogic is in both servers with proper permissions
  2. Open the dashboard for Server A
  3. Create a new rule:
    • IF: Has Some Roles → Premium
    • THEN: Add Roles → Lounge Access (from Server B)
  4. Save the rule

Result: Anyone who gets "Premium" in the main community automatically gets "Lounge Access" in the VIP lounge, as long as they're a member of both servers.

Tips for Cross-Server Rules​

Start Small​

Test with one rule affecting one target server before building complex multi-server setups.

Document Your Setup​

With multiple servers involved, keep notes about which rules affect which servers. This helps with troubleshooting and maintenance.

Monitor Both Servers​

Changes happen in the target server, so check both servers when verifying rules work correctly.

Use the Testing Sandbox​

Test thoroughly before going live, especially for rules that affect production servers.

Consider Timing​

Cross-server actions may have slightly more latency than same-server actions, as RoleLogic communicates with multiple servers.

Troubleshooting​

"Bot and User Not in Guild"​

The member isn't present in the target server, or RoleLogic isn't in the target server. Verify both.

"Cannot manage role due to hierarchy"​

RoleLogic's role is too low in the target server. Adjust role hierarchy in that server.

Actions not working in target server​

  1. Check RoleLogic has "Manage Roles" permission in the target server
  2. Verify role hierarchy in the target server
  3. Confirm the member is in both servers
  4. Review quota limits for cross-server actions

Next Steps​