Configure Discord Roster roles
Choose individual or shared Roster roles, free role slots safely, and recover interrupted changes.
- Who this is for
- League Owners, working with a Discord manager when permissions need changing
- When you’re done
- The League uses the intended Discord role mode, with any old-role cleanup explicitly reviewed.
This setting applies to a Discord-integrated League. Independent Team webhooks only send notifications and do not manage Discord roles.
1. Open Discord Roster roles
For an existing League, the League Owner opens Manage League → Discord → Discord Roster roles. During League setup, the choice appears with the Discord checks after Heir is installed. A web-only League does not need Discord roles to manage its Rosters. Organizers can review the League's other management sections, but changing this role mode is owner-only.
If the integration is paused, resume it before applying role changes. Heir needs Manage Roles, View Audit Log, and a role position above the roles it manages. Use Update bot permissions or ask a Discord manager to correct them manually, then refresh the preview. Slash-command access is checked through roles in Heir.
2. Choose a mode
| Mode | Discord behavior | Choose it when |
|---|---|---|
| Individual Roster roles | One named, colored role per Roster; supports Roster-specific mentions and configured channel access. | You want each Roster represented separately and have sufficient role slots. |
| Shared Roster role | One On a Team role for Players with a current League Roster Seat. No new role is needed for each Roster. | You expect many Rosters or need to conserve Discord role slots. |
The picker shows the current role count against Discord's 250-role limit. At 175 or more roles, Heir recommends shared mode; below that it recommends individual roles. This is a suggestion, not an automatic switch. If the count is unavailable, Heir does not guess a recommendation.
Both modes preserve Heir's Teams, Rosters, Enrollments, and competition history. Organizer, Captain, and Free Agent roles remain managed. Shared mode grants On a Team only to rostered Players, not every independent Team Member, reserve, or blocked player. Manually assigning a Discord role does not make someone eligible to play.
A shared role cannot distinguish one Roster from another for private channel access. Do not substitute it for a Roster-specific permission rule unless you intend every holder to receive that access.
3. Review old roles when choosing shared mode
Selecting Shared Roster role reveals Remove old Discord roles when old Roster roles exist. Cleanup is optional:
- Select only the roles you intend to delete. Select all … available for removal selects the removable entries, not protected ones.
- Entries under Must stay for now explain why removal is blocked. They may control channel access, grant additional permissions, or be managed by another integration. Review the dependency with a Discord manager; do not remove access rules merely to dismiss the warning.
- Roles you keep retain their current members and access, but stop following Roster changes. Review them separately if they grant access that should no longer remain.
If On a Team does not already exist as a verified managed role, one free role slot is needed to create it before cleanup. Selecting old roles for deletion does not eliminate that requirement.
4. Confirm the exact change
Choose Review changes. Read the chosen mode, retained roles, and exact names and IDs selected for deletion. Confirm with the displayed action, such as Use shared role or Switch & delete … roles.
Role deletion is permanent. Recreating a role later gives it a different ID; other bots and integrations using the deleted ID may stop working. Deleting a Discord role does not delete its Heir Roster or results.
Wait for the operation to finish. Change requested means Heir accepted the request, not that Discord has completed it. The pending view saves progress and provides Refresh status; you can leave the page and return.
If a change fails
Read the specific error and refresh the preview. Some Discord changes may already have completed. Heir rechecks role ownership, permissions, and channel dependencies before deletion; a role becoming unsafe between preview and confirmation can stop the operation.
Correct only the reported issue, review the current mode and remaining choices, then retry. Do not blindly repeat deletions or create replacement roles by name to repair an uncertain operation. If Heir cannot establish ownership safely, contact support with the League, operation time, and error—not credentials.
Switching back to individual roles
Choose Individual Roster roles → Review changes → Use individual roles. Heir checks whether enough role slots are available for active Rosters. Previously deleted role IDs do not return, so review any external integrations and channel permissions afterward.
Next: Understand Seats and eligibility, connect a Discord, or troubleshoot Discord commands.