Staff
The Staff tab, headed Staff tools on the page, sets up two things that work together:
- Staff applications: members apply to join your team with
/staffapply, and your staff review the answers in Discord. - Staff records: the positions on your team, the roles each one gives, and a record of who holds them.
Press Save changes after editing. Saving restarts the bot so it picks up the change.
Reviewing applications and managing records needs the level chosen for Manage staff applications and records on the Access tab.
Staff applications
Turns /staffapply on or off.
- On: members can apply. To turn this on you also need a Review channel and at least one position in Positions; otherwise the save is refused.
- Off:
/staffapplyreplies that staff applications are not open yet.
New bots start with applications off.
When a member uses /staffapply, a form opens with your Application questions. Every question must be answered. The bot then posts the answers in the review channel with two buttons:
- Approve and appoint lets the reviewer choose a position from a menu. The bot gives the member that position's roles and the Staff member role, creates their staff record, and sends them a direct message. The appointment is also logged in the moderation log.
- Decline marks the application as declined and sends the member a direct message.
A member cannot apply while they already have an application waiting, or while they already hold a staff position.
Review channel
The channel where new applications are posted for your staff to review. Choose a private channel your reviewers can see. It must be set before applications can be turned on.
If the bot cannot post in this channel when someone applies, the application is not saved and the member is told to ask an owner to check the settings.
Application questions
The questions on the application form, one per line. You need between one and five questions, and each can be up to 45 characters long, because Discord shows them as the labels on the form. The save is refused otherwise.
New bots start with:
- Why would you like to join the team?
- What experience do you have?
- What timezone are you in?
Staff member role
A role given to everyone appointed to any position, in addition to the position's own roles. It is useful for a general "Staff" role that every team member should have. It is taken away again when their staff record is removed.
If set to None, members only get their position's own roles.
Positions
The positions on your team, one per line, in this format:
key | Display name | role IDs | admin or owner
- key: a short name for the position, using 2 to 30 lowercase letters, numbers, hyphens or underscores, for example
mod. Each key must be different. - Display name: the name members see, up to 80 characters, for example
Moderator. - role IDs: one or more Discord role IDs given with the position, separated by commas.
- admin or owner: who may appoint to this position. With
owner, only superusers can. Withadmin, or if you leave this part out, anyone with the access level for Manage staff applications and records can.
For example:
mod | Moderator | 123456789012345678 | admin
head-mod | Head Moderator | 123456789012345678, 234567890123456789 | owner
You can list up to 25 positions. Leave the box empty for no positions, though applications cannot be turned on without at least one.
Managing staff records
Staff records are managed in Discord with /staffrecord:
/staffrecord appointappoints a member to a position chosen from your list, gives them the roles, creates their record and sends them a direct message. It is logged in the moderation log./staffrecord removeends a member's record, with an optional reason, and takes away the position’s roles and the staff member role, including any of those roles the member already had before they were appointed./staffrecord viewshows a member's record: their position, name, timezone and when they were appointed./staffrecord listlists the active staff records./staffrecord profilelets anyone with a staff record set the name and timezone shown on it, such asEurope/London. This one needs no staff access.
A member can hold only one active staff record at a time. If a position's role no longer exists in your server, appointing to it is refused until you fix the role IDs.