Roles and permissions
Ninth Bot uses your normal Discord permissions plus the ticket roles you pick in /setup. This page explains who can do what, for admins, staff and members.
The three groups
Admins have Manage Server or Administrator. They can run /setup, /status and /alerts, and change settings on the dashboard.
Staff covers two separate things:
- Ticket staff: members with a ticket staff or ticket admin role from
/setup, or the category staff role of a ticket category. Discord Administrator also counts. They handle tickets. - Moderators: members with the Discord permission an action needs. There is no separate moderator role:
/warnneeds Moderate Members,/kickneeds Kick Members, and so on.
Members can open tickets, report members and messages, rate their closed tickets and use /help.
Ticket staff roles don't give moderation powers, and moderation permissions don't make someone ticket staff. Give your moderators both if they should do both.
Permission matrix
| Action | Who can do it |
|---|---|
/help, open a ticket | Everyone |
| Rate a closed ticket | The ticket's opener, once |
/report, Report message | Everyone |
| Request close on a ticket | The ticket's opener, or ticket staff |
| Claim, close, add or remove users, set priority | Ticket staff |
/warn, /note, /timeout set, /timeout remove | Moderate Members |
| Moderate context menu | Moderate Members (each action button still needs its own permission) |
/case, /history | Moderate Members |
/reason and Edit reason | The case's moderator, or Manage Server |
| Review a report (Valid or Dismiss) | Moderate Members, but not the reporter or the reported member |
/kick | Kick Members |
/ban, /unban | Ban Members |
| Accept or deny a ban appeal | Ban Members |
/purge | Manage Messages in that channel |
/setup, /status, /alerts | Manage Server or Administrator |
Administrator includes every permission above.
Dashboard access
The dashboard checks your Discord roles live every time you load a page. There are two levels:
- Staff: Moderate Members, or a ticket staff or ticket admin role.
- Admin: Manage Server or Administrator.
| Dashboard page | Staff | Admin |
|---|---|---|
| Overview | Yes | Yes |
| Cases, Users, Tickets, Logs, Insights, Appeals | Yes | Yes |
| Settings | No | Yes |
| History and undo | No | Yes |
Some buttons on those pages need more, the same as in Discord: editing a case reason or its evidence needs the case's moderator or Manage Server, reviewing a report needs Moderate Members, and deciding an appeal needs Ban Members.
Members who are neither staff nor admin only see the ban appeal page, and only if they are banned somewhere that accepts appeals.
Role hierarchy rules
Before any moderation action, the bot checks these rules in order. The first one that fails is the message you see.
- You need the Discord permission for the action.
- The bot needs it too.
- You can't target yourself, the bot or the server owner.
- Only
/ban,/unbanand/notework on someone who isn't in the server. - For a warn, timeout, kick or ban of a member, their highest role must be below yours. The server owner skips this rule.
- Their highest role must also be below the bot's highest role.
- Members with Administrator can't be timed out.
/unban and /note skip the role checks. /purge only checks that you and the bot have the permissions it needs in that channel.
Server admins can change who sees a slash command under Server Settings, Integrations. That only hides or shows commands: the bot still checks the permissions above when someone runs one.
The operator
zVapor, who runs Ninth Bot, can pass the bot's own permission checks in any server to help with support. Discord's own rules, such as role hierarchy, still apply, and anything done is logged under zVapor's own name.