Discord Safety Best Practices

Keep staff above Ser Aymeric, colour roles below

In Discord, open Server Settings → Roles. Put Administrator, Moderator and any other privileged roles above Ser Aymeric’s highest role. Put only the roles it should assign below it. With Manage Roles, a bot can assign ordinary roles below its highest role; it cannot assign or edit roles at or above that position.

Give the bot only what its features need

Keep Administrator and Manage Server off for Ser Aymeric. Administrator grants all permissions and bypasses channel restrictions; placing the bot lower does not make that permission safe. Manage Server is not needed to assign colour roles or to let you configure the bot on this website.

Manage Roles is a powerful permission, but role assignment needs it. Enable it only when using automatic roles, and keep staff roles above the bot. Add other permissions only for enabled features, such as Manage Messages for message cleanup or Manage Nicknames for character names. The permissions guide below lists feature requirements.

A colour role should only be a colour

For self-selected colour roles, leave all role permission switches off and add no channel or category overrides. Check existing roles too: a harmless name such as Blue does not stop a role from granting access to a private channel or moderation tools.

The website rejects automatic-role choices with staff permissions, such as Administrator, Manage Server, Manage Roles, Kick Members or Ban Members. It also checks role hierarchy and excludes managed integration roles. These checks are an extra safeguard; keep privileged roles above Ser Aymeric anyway.

Protect who can configure the bot

The server owner and members with Administrator or Manage Server can manage Ser Aymeric on the website. Those are permissions for trusted people; the bot does not need them. A configured bot-admin role also grants access to bot settings. Keep that role above Ser Aymeric and never offer it as a reaction, joining or reward role, even if it has no Discord permissions.

Review Website access in the dashboard and remove access people no longer need. Protect event-manager roles too. Check command access in Discord’s Server Settings → Integrations separately. Use two-factor authentication for staff accounts and never share passwords or login tokens.

Before you share a role menu

1. Check every role assigned to Ser Aymeric. Remove Administrator and Manage Server, and keep its highest role below all staff, bot-admin and event-manager roles.
2. Give Ser Aymeric Manage Roles only if it needs to assign roles. Place intended automatic roles below it, without staff permissions or unintended private-channel access.
3. Review @everyone, the bot’s other roles, and channel or category overrides. Turning off a permission on one role does not remove a grant from another.
4. Test the role menu with an ordinary member account. Confirm members get only the intended role and cannot see staff channels, use restricted commands or open bot settings.
5. Repeat these checks after changing roles, channel access or your team. Use Discord’s Audit Log to investigate unexpected role and permission changes.