Skip to main content

Fix DiscordSRV role hierarchy without granting Administrator

Applies to: DiscordSRV; match the linked maintainer documentation to your installed platform and release.
Documentation checked .

A bot can send chat successfully while failing to update roles. Discord channel permissions and role-management rules are separate, so a working chat bridge does not prove rank synchronisation has sufficient access.

Prepare the test

Use a private test channel and two test identities before changing the public bridge. Keep bot tokens, linking codes and staff console output out of screenshots and public support messages.

Make the change

  1. Identify one failing mapping and copy its target role ID into a private note. Confirm the linked Minecraft and Discord test accounts are correct before changing the bot’s permissions or your rank configuration.
  2. In Discord server settings, inspect the bot’s effective permissions and its role position relative to the target role. Follow DiscordSRV’s setup guidance for the permissions needed by the feature you actually use.
  3. Move the bot role above the intended manageable member role where appropriate. Keep owner and protected staff roles outside this test, and avoid granting Administrator to bypass an unknown hierarchy problem.
  4. Run a controlled membership change for the test account. Read the corresponding DiscordSRV log entry and compare the role ID, direction and result with your recorded mapping, then test removal as well as assignment.

Check the result

The selected role should appear and disappear as the mapping requires, while the bot still cannot manage roles you intended to protect. Verify that public chat continues to work after the permission change.

If the test fails

Restore the previous role position if unrelated roles become manageable. If the target remains unchanged, inspect the mapping’s authority and linked identity rather than repeatedly expanding bot privileges until the warning disappears.

An integration-managed Discord role may have separate restrictions. Use an ordinary disposable role for the first test so those restrictions do not obscure whether the bot’s normal hierarchy is correct.

References and related help

Check the official DiscordSRV documentation against your installed release before using a command or setting from another version.

No comments to display