Skip to main content

Role Bindings - Advanced Guide

Role Bindings automatically assign Discord roles based on Roblox group membership and ranks. This guide covers advanced configurations beyond the basics in the Getting Started guide.

How Role Bindings Work

1

User verifies

User links their Roblox account with /verify
2

System checks groups

Technified checks which Roblox groups they’re in
3

Compares ranks

For each group, checks if their rank matches any binding
4

Assigns roles

Gives all matching Discord roles
5

Auto-updates

Repeats this process when ranks change

Rank Ranges

Min and Max Rank

Each binding can specify a range of ranks: Example:
  • Min Rank: 50
  • Max Rank: 100
  • Discord Role: @Member
Who gets the role:
  • Rank 50 ✅
  • Rank 75 ✅
  • Rank 100 ✅
  • Rank 49 ❌ (below minimum)
  • Rank 101 ❌ (above maximum)

Common Patterns

Min: 255, Max: 255 → @Owner
Only rank 255 gets the role (exact match)

Multiple Bindings Strategy

Non-Overlapping Ranks

Best for: Clear role hierarchy
Rank 1-49:   @Guest
Rank 50-99:  @Member
Rank 100-254: @Moderator
Rank 255:    @Owner
Advantages:
  • Clear, no overlap
  • User gets exactly one role
  • Easy to understand

Overlapping Ranks

Best for: Multiple role categories
Rank 1-255:   @Verified (everyone)
Rank 50-255:  @Member (rank 50+)
Rank 100-255: @Staff (rank 100+)
Rank 200-255: @Admin (rank 200+)
Advantages:
  • Users can have multiple roles
  • Cumulative permissions
  • @Staff inherits @Member + @Verified
Use overlapping bindings when you want cumulative roles. Use non-overlapping when you want exclusive roles.

Multiple Groups

Cross-Group Bindings

Users can be in multiple groups and get roles from each: Example:
  • User is rank 100 in “Main Group” → Gets @MainStaff
  • User is rank 50 in “Dev Group” → Gets @Developer
  • User has both roles simultaneously

Group-Specific Roles

Group 123456:
  - Rank 50-255 → @MainMember

Group 789012:
  - Rank 50-255 → @DevMember
Users get different roles depending on which groups they’re in.

Auto-Sync Behavior

When Roles Update

Roles automatically update when:
  1. User verifies (/verify)
  2. User’s Roblox rank changes (checked periodically)
  3. User manually syncs (/sync)
  4. Admin force-syncs (/force_sync @user)
  5. New bindings are created

Sync Frequency

  • Manual sync: Instant
Technified currently don’t have an automatic sync Frequency, roles will only be given if the user uses /verify or sync.

Advanced Configurations

Tier System with Base Roles

Binding Setup:
1. Rank 1-255   → @Verified     (base role)
2. Rank 50-255  → @Member       (adds member access)
3. Rank 100-255 → @Staff        (adds staff perms)
4. Rank 200-255 → @Admin        (adds admin perms)
5. Rank 255     → @Owner        (owner only)
Result for rank 200 user:
  • @Verified ✅
  • @Member ✅
  • @Staff ✅
  • @Admin ✅
  • @Owner ❌

Department-Based Roles

Main Group:
  - Rank 50-99   → @Junior
  - Rank 100-199 → @Senior

Dev Group:
  - Rank 1-255   → @Developer

Mod Group:
  - Rank 1-255   → @Moderator
Users can have roles from multiple groups based on their memberships.

Role Priority & Hierarchy

Discord Role Hierarchy

Role bindings respect Discord’s role hierarchy:
Higher in list = Higher priority

@Owner       ← Highest
@Admin
@Moderator
@Member
@Verified    ← Lowest
Important: Make sure Technified’s bot role is above all roles it needs to manage. Otherwise, it can’t assign them.

Managing Role Order

1

Open Discord Settings

Go to Server Settings → Roles
2

Drag to Reorder

Drag roles up/down to set hierarchy
3

Put Bot Role High

Ensure Technified’s role is above all managed roles
4

Save

Changes apply immediately

Troubleshooting

Check:
  • User is verified (/verify)
  • User is in the correct Roblox group
  • User’s rank falls within the binding range
  • Technified’s role is high enough in hierarchy
  • Binding is saved and active
Solution: Use /force_sync @user to manually trigger an update
Cause: You may have reached a limit or have conflicting bindingsSolution:
  • Review existing bindings
  • Consolidate where possible
  • Remove unused bindings
Cause: Multiple bindings match, or rank range is incorrectSolution:
  • Review all bindings for that group
  • Check for overlapping ranges
  • Verify min/max ranks are set correctly

Best Practices

Before creating bindings, sketch out:
  • What ranks exist in your Roblox group
  • What Discord roles you want
  • How they map to each other
This prevents confusion later.
Match Discord role names to Roblox ranks when possible:
  • Roblox: “Moderator” → Discord: @Moderator
  • Makes system easier to understand
Before going live:
  • Create bindings
  • Test with a test Discord + Roblox account
  • Verify roles assign correctly
  • Adjust as needed
Keep a document with:
  • Which bindings you created
  • What each binding does
  • Any special cases or exceptions
Makes troubleshooting easier.
As your server evolves:
  • Check bindings still make sense
  • Remove unused ones
  • Adjust ranges if group structure changed

Next Steps


Role Bindings keep your Discord roles synchronized with Roblox ranks. Set up once, forget about manual updates.