Access

The Access tab decides who can use the bot's staff commands. There are three ways to give someone access, and you can use any mix of them:

  • Superusers can do everything.
  • /perm requests let a superuser approve access for one person at a time, from Discord.
  • Role-based access gives everyone with a chosen Discord role moderator or admin access.

Changes on this tab restart the bot so it picks them up.

Access levels

The bot sorts everyone into one of four levels. Higher levels include everything the levels below can do.

LevelWho has it
OwnerYour superusers.
AdminEveryone with the Admin role.
ModeratorEveryone with the Moderator role.
MemberEveryone else.

Someone with an approved /perm grant can use the commands in that grant, even if their level is lower.

Staff cannot use moderation commands on themselves, on a superuser, or on anyone at their own level or above. Superusers can act on anyone except themselves and other superusers.

The setup lock

Every new bot starts with the setup lock on. While it is on, only superusers can use the staff commands: moderation, cases, announcements, giveaways, quarantine and staff records. This applies to the Moderator role, the Admin role and approved /perm grants alike.

Members can still open tickets and use /report, /staffapply, /perm and /help while the lock is on. Staff who can handle tickets can still claim and close them.

When you have finished setting up, a superuser turns the lock off by typing your prefix followed by lockdown off in your server, for example ,lockdown off. Type lockdown on to turn it back on. Anyone can check whether it is on with /perm status. See General for the prefix.

Superusers

Superusers can use every command, including the owner-only ones, the text commands and the setup lock. They are also the only people who can approve or deny /perm requests.

When you first connected your bot, the owner of its Discord application became the first superuser. If a Discord team owns the application, every member of the team was added.

  • Add a superuser: type their Discord user ID and press Add. In Discord, turn on Developer Mode, then right-click the member and choose Copy User ID. A user ID is 17 to 20 digits.
  • Remove: press Remove next to their name. You cannot remove the last superuser; it shows the Last superuser badge instead.

Superusers are protected from the bot's moderation commands and are never checked by automod.

How /perm works

/perm is on when a /perm log channel is chosen, and off when it is set to None. There is no separate switch.

  • On: staff can ask for access with /perm select, choosing a group and, if they want, a single command in it. They can ask for themselves or for another member, and give a reason. The bot posts the request in the /perm log channel with Approve and Deny buttons. Only a superuser can press them. The member gets a direct message with the outcome.
  • Off: /perm select and /perm remove reply that permission requests are not enabled. Grants that were already approved keep working.

The groups you can ask for are:

GroupCommands in it
Moderationwarn, mute, unmute, kick, ban, unban
CasescaseView, caseChange
Communitygiveaway, announce
Staff recordsstaffManage
Quarantinequarantine

Leaving the command blank asks for the whole group. For example, /perm select group:Moderation command:mute asks only for timeouts, while /perm select group:Moderation asks for all six moderation commands.

/perm remove asks for an approved grant to be taken away. It must match the grant exactly: removing a single-command grant does not remove a whole-group grant, and the other way round. It also cannot remove access that comes from a Discord role.

/perm status shows your own level, whether the setup lock is on, and your approved grants. It works whether or not requests are turned on.

Approved grants appear on this tab under Approved access, with the member, what they can use and the date it was approved. Grants are removed from Discord with /perm remove, not from the dashboard.

/perm log

The channel where /perm requests arrive for a superuser to approve or deny. Choose a private channel that your superusers can see. It is also shown on the Channels tab; both places change the same setting.

Choosing a channel turns /perm on. Setting it to None turns /perm off. If the bot cannot use the channel, the member is told the approval channel is unavailable, or that the request could not be posted and to try again later, and no request is created.

Moderator role

Everyone with this role gets moderator-level access. Choose a role from the list, or None.

When set to None, nobody gets moderator access from a role. Access then comes only from superusers, the Admin role and /perm grants.

Members with this role are also:

  • able to claim and close tickets, as ticket handlers;
  • skipped by automod.

The Moderator role and Admin role must be different roles, and neither can be the same as the Role for new members on the Welcome tab.

Admin role

Everyone with this role gets admin-level access, which includes everything moderators can do. Choose a role from the list, or None.

When set to None, nobody gets admin access from a role.

Who each role can use

Once you have chosen a Moderator role or Admin role, a table appears. For each feature, choose the lowest level that may use it:

  • Moderators and above
  • Admins and above
  • Owner only

People with an approved /perm grant for that command can use it too, whatever level is chosen here. Superusers can always use every feature.

The rows are listed below, with the level a new bot starts with.

Warn members

Controls /warn, which saves a case, sends the member a direct message and logs it in the moderation log. New bots: Moderators and above.

Time out members

Controls /mute, which times a member out for a length such as 30m, 12h or 7d. New bots: Moderators and above.

Remove timeouts

Controls /unmute. New bots: Moderators and above.

Kick members

Controls /kick. New bots: Admins and above.

Ban members

Controls /ban. Give a length such as 7d for a temporary ban, which the bot lifts when it runs out; leave it blank for a permanent ban. New bots: Admins and above.

Unban members

Controls /unban, which takes a Discord user ID. New bots: Admins and above.

View moderation cases

Controls /case with the View action, which shows a saved case by its number. New bots: Moderators and above.

Edit or delete cases

Controls /case with the Edit reason and Remove from active record actions. New bots: Admins and above.

Quarantine and release members

Controls /quarantine hold, /quarantine release and /quarantine status. /quarantine setup is always for superusers only. See Quarantine. New bots: Admins and above.

Post announcements

Controls /announce, which posts your text as an announcement card in the channel you choose, or the current one. New bots: Admins and above.

Start giveaways

Controls /giveaway, which posts a giveaway with an Enter giveaway button. See Welcome. New bots: Moderators and above.

Manage staff applications and records

Controls reviewing staff applications and the /staffrecord commands view, list, appoint and remove. See Staff. New bots: Admins and above.