Update Heir's Discord permissions

Who this is for

Discord owners/managers, with League Owners and Organizers coordinating the repair

When you’re done

A fresh check confirms Heir has the requested bot permissions and the urgent alert clears.

An existing installation does not automatically receive permissions added to a newer install link. Heir checks the bot's permissions and identifies what is missing. Role syncing, channel management, or announcements may fail until the missing permission is granted.

Recognize the urgent alert

Permission incidents appear under Action required in the notification dropdown, dashboard, and Inbox. The bell keeps its urgent indicator while an incident remains unresolved. Opening the notification, marking updates read, or clearing ordinary updates does not dismiss it.

Heir also sends a DM to the affected Discord's owner and, for a League connection, its Owner and current Organizers when incident DMs are enabled. Overlapping roles receive one notice per person. Repeated checks and partial fixes do not resend the same incident. Newly missing permissions or a recurrence after a verified fix can create a new notice.

If DMs are disabled or unavailable, the in-app alert remains. A delayed notice is checked again before delivery so resolved incidents and no-longer-authorized recipients are skipped.

1. Open the affected connection

Use Update bot permissions from the urgent alert or Manage League → Discord → Bot permissions. The repair page names the Discord, lists missing permissions, and shows when they were last verified.

Sign in with your own Discord account. A League role lets you coordinate the issue, but it does not grant Discord-wide permission to authorize the bot. Ask the Discord owner or a manager with the required Discord authority to complete the update if necessary.

2. Authorize the update

Choose Update bot permissions on the repair page. Discord opens with the intended Discord preselected and locked, using the permission set for its League connection. Review the requested permissions and authorize them.

Heir requests specific permissions, not Administrator. You do not need to kick the bot, install a second copy, create another League. This repair flow does not change League ownership, existing resources, or settings.

3. Wait for verification

Returning from Discord is not by itself proof that the problem is fixed. Heir performs a fresh check of the bot's current roles and permissions. Bot permissions verified means the requested bot-level permissions are present and the permission alert is resolved.

If some permissions are still missing, review the remaining list. If the check fails or Discord is rate limiting requests, keep the last-known issue in mind and use Check again later. Cancelling authorization leaves the last verified status unchanged.

Role hierarchy and channel-specific permission overrides are separate. If a feature still fails after this alert clears, run the integration health check. Heir must remain above roles it manages, and a channel override can still prevent access.

Manual alternative

In Discord, open Server Settings → Roles → Heir, enable the named missing permissions, and save. Then return to Heir and choose Check again. Do not grant Administrator merely to avoid checking the specific requirement.

Bot permissions and command access

Bot permissions control what Heir itself can do in Discord. League slash commands are visible to everyone by default, and Heir checks the caller’s League or Team authority before acting. There is no separate command-access grant. Heir still needs bot permissions such as Manage Roles and View Audit Log for the features that use them.

Next: Discord Roster roles, command permissions, or connection troubleshooting.