Skip to main content

Actions (Add & Remove Roles)

Actions are the "THEN" part of your rules. They define what happens when a member matches your condition.

What Is an Action?​

An action is an instruction to change a member's roles. RoleLogic supports two types:

  1. Add Roles — Give the member one or more roles
  2. Remove Roles — Take away one or more roles

When a rule's condition matches, RoleLogic immediately performs the action for that member.

Add Roles​

The Add Roles action assigns roles to members who match your condition.

How It Works​

When the condition is true:

  • RoleLogic checks if the member already has each role
  • Any roles they don't have are added
  • Roles they already have are left unchanged

Example​

Rule: IF member has "Server Booster" → THEN add "VIP", "Booster Perks"

What happens:

  • Member gets "Server Booster" role (from Discord)
  • RoleLogic sees they match the condition
  • RoleLogic adds "VIP" and "Booster Perks" (if not already present)

When to Use Add Roles​

  • Granting rewards for achievements
  • Unlocking access based on qualifications
  • Building role hierarchies automatically
  • Onboarding new members with starter roles

Remove Roles​

The Remove Roles action takes roles away from members who match your condition.

How It Works​

When the condition is true:

  • RoleLogic checks if the member has each role
  • Any roles they have from the list are removed
  • Roles they don't have are ignored

Example​

Rule: IF member has "Verified" → THEN remove "Unverified", "New Member"

What happens:

  • Member gets "Verified" role
  • RoleLogic sees they match the condition
  • RoleLogic removes "Unverified" and "New Member" (if present)

When to Use Remove Roles​

  • Cleaning up temporary or starter roles
  • Enforcing mutual exclusivity (can't have both X and Y)
  • Demoting based on changes
  • Removing access when conditions change

Combining Actions​

You can add one additional action type to a single rule, allowing you to add AND remove roles at the same time.

How It Works​

Click "Add Combined Action" to add a second action. You can:

  • Add some roles AND remove others in one rule
  • Remove some roles AND add others in one rule

Example​

Rule: IF member has "Promoted to Mod" → THEN add "Moderator" AND remove "Trial Mod", "Helper"

What happens in one rule:

  1. Member gets "Promoted to Mod" role
  2. RoleLogic adds "Moderator"
  3. RoleLogic removes "Trial Mod" and "Helper"

Why Combine Actions?​

  • Cleaner organization: One rule handles the complete transition
  • Atomic updates: All changes happen together
  • Easier maintenance: One place to update, not two rules

Selecting Roles​

Choosing Roles to Add/Remove​

  1. Click the role selector in the action section
  2. Search or scroll to find roles
  3. Click to select (click again to deselect)
  4. Selected roles appear with checkmarks

You can select multiple roles in a single action.

Important Considerations​

Role Hierarchy: RoleLogic can only manage roles below its own role in your server's role list. If you select a role that's too high, the action will fail for that role.

Learn more about role hierarchy →

Cross-Server Roles: You can select roles from other servers where RoleLogic is present. This is called a cross-guild action.

Learn more about cross-guild actions →

Action Behavior​

Idempotent Actions​

Actions are idempotent, meaning running them multiple times has the same result as running once:

  • Adding a role someone already has = no change
  • Removing a role someone doesn't have = no change

This prevents errors and duplicate operations.

Real-Time Execution​

Actions execute immediately when conditions match:

  • No delay or scheduling
  • Changes appear in Discord within seconds
  • Affected members see their new permissions instantly

Cascade Effects​

When an action changes a member's roles, it might trigger other rules:

  1. Rule A adds "VIP" to a member
  2. Rule B says: IF has "VIP" → add "VIP Lounge Access"
  3. Rule B now fires because of Rule A's action

RoleLogic handles this automatically, processing all triggered rules in priority order.

Examples by Use Case​

Reward System​

Condition: Has some of [Achievement-1, Achievement-2, Achievement-3] Action: Add [Achiever Badge]

Anyone with any achievement gets a badge.

Role Cleanup​

Condition: Has some of [Verified] Action: Remove [Guest, Unverified, Pending]

Verified members lose all pre-verification roles.

Tier Upgrade​

Condition: Has all of [Gold Tier, Loyalty Badge] Action: Add [Platinum Tier] AND Remove [Gold Tier]

Gold members with loyalty get upgraded and cleaned up in one rule.

Access Revocation​

Condition: Has some of [Banned, Suspended] Action: Remove [Member, Verified, VIP, All-Channels]

Banned users lose all access roles.

Mutual Exclusivity​

Condition: Has all of [Team Red, Team Blue] Action: Remove [Team Red]

If someone somehow has both team roles, remove one.

Best Practices​

Be Specific​

Only include roles that need to change. Don't add unnecessary roles "just in case."

Test First​

Use the testing sandbox to verify actions work as expected before going live.

Consider Cascades​

Think about whether your action might trigger other rules. This can be powerful but also confusing if unexpected.

Document Your Logic​

Use rule descriptions to explain why certain roles are added or removed. Future you will thank present you.

Check Role Hierarchy​

Before creating rules, ensure RoleLogic's role is positioned correctly to manage all the roles in your actions.

Troubleshooting Actions​

Action Not Working?​

  1. Check role hierarchy: Is RoleLogic's role above the target role?
  2. Verify permissions: Does RoleLogic have "Manage Roles" permission?
  3. Confirm condition: Is the condition actually matching?
  4. Check rule status: Is the rule enabled?

Unexpected Results?​

  1. Review cascades: Is another rule interfering?
  2. Check priority: Is a higher-priority rule running first?
  3. Test in sandbox: Isolate the behavior with specific role combinations

Next Steps​