Permissions
How Aurora decides who may do what: Discord permissions, Aurora permission groups and the role hierarchy.
Aurora checks permissions on the server for every command, button and dashboard change. There are three layers, and an action must pass all that apply.
1. Discord permissions#
Some commands also need a Discord permission, for example Ban Members for /ban or Manage Channels for /channel lock. Aurora needs that permission too.
2. Aurora permission groups#
A group is a set of rights you give to a Discord role. This is how a role becomes a moderator role without having Discord's Administrator permission.
| Group | What it is for |
|---|---|
ADMINISTRATOR | Configuring Aurora. The server owner and members with Discord's Administrator permission always qualify. |
MODERATOR | Moderation actions such as bans, kicks, timeouts and cases. Also satisfies Helper. |
HELPER | Light moderation: warnings, notes and case lookups. |
TICKET_STAFF | Handling tickets and reports. |
GIVEAWAY_MANAGER | Running giveaways. |
ECONOMY_MANAGER | Staff tools for Aurora Points. |
SECURITY_MANAGER | Security status, incidents, lockdown and raid tools. |
Assign a group with /permissions assign group role, remove it with /permissions unassign, and see the current assignments with /permissions list. In the dashboard, use the Permissions page. @everyone cannot hold a group.
3. The role hierarchy#
Aurora refuses to act on yourself, on the server owner, on Aurora itself, and on anyone whose highest role is equal to or above yours or Aurora's. The server owner is exempt from the hierarchy rule for their own actions.
Command rules#
Administrators can allow or deny a command in particular channels or for particular roles (/config command-channel, /config command-role), or disable it. /config and /help can never be disabled. The owner and Administrators are never locked out by these rules.
See the permission model for a more detailed description.