Build a staff application

10 minutesAdmins (Administrator)

At the end you will have an application form members open with /apply. Each finished application is posted in a review channel with Claim, Accept and Deny buttons. Accepting can give roles automatically, and the applicant gets a DM either way.

Before you start

• Building a form needs the Administrator permission or server ownership.
• Make a private review channel, for example #app-reviews, that only your reviewers can see. A result channel (for example #app-results) is optional.
• Make or pick a reviewer role, for example @Recruitment Team.

Steps

1. Open the form builder

Type /apps create name:moderator. Use a short, one-word name. Members will type it when they apply.

You see: an "Application: moderator" card with three menus and the buttons Add Question, Remove Last, Intro, Roles, Rename, Save and Cancel.

2. Pick the channels

In the menus, pick:

• Review channel (where applications are sent). This one is required.
• Result channel (optional), where "accepted" or "denied" is posted.
• Ping role when an application arrives (optional).

You see: the card shows each one under "Review channel", "Result channel" and "Ping role".

3. Add questions

Press Add Question. Type the question, pick an Answer type (Short answer, Paragraph, One choice, Checkboxes, Number or Roblox username), and press Submit. For One choice and Checkboxes, list the choices one per line. Tick Optional question if it can be skipped.

You see: the question added to the list on the card. Repeat for each question.

4. Choose roles for each decision

Press Roles. Pick the roles to add when someone is accepted, for example @Trial Moderator. You can also pick roles to remove when accepted, and roles to add or remove when denied. Press Back.

5. Save the form

Press Save.

You see: "Saved moderator. Members apply with /apply moderator."

6. Add reviewers

Type /apps settings form:moderator reviewer_role:@Recruitment Team.

You see: a settings card for the form. People with this role can now press the review buttons.

7. Tell members how to apply

There is no apply button panel. Post a message in your announcements telling members to type /apply and pick moderator in the form box. When a member runs it, the questions open as a form inside Discord, five at a time, with a Continue button between pages. You see (the member): "Submitted. You'll get a DM when it's reviewed. Good luck!"

8. Review an application

Each application appears in the review channel with the member's answers, their account age, when they joined, and how many moderation cases they have.

• Press Claim so other reviewers know you have it.
• Press Accept or Deny. A box asks for a reason (optional). The reason is sent to the applicant.

You see: the card turns green or red and shows who decided. The applicant gets a DM, the roles from step 4 are given or removed, and the result is posted in the result channel.

Change it later

• Edit questions, channels or roles: /apps edit name:moderator
• Stop taking applications: /apps close form:moderator. Reopen with /apps open form:moderator.
• See all forms: /apps list
• See what is waiting: /apps queue
• Only let certain people apply: /apps settings form:moderator required_role:@Member min_days:7
• Save reasons reviewers can reuse: /apps preset form:moderator name:inactive text:You need to be more active before applying. Reviewers then type inactive in the reason box.

If something goes wrong

• "No applications are open here." No form has been saved yet. Do steps 1 to 5.
• "This application has no review channel. Tell an admin." The form was saved without a review channel. Run /apps edit name:moderator, pick one, and press Save.
• "Only reviewers for this application can do that." The person pressing the button does not have the reviewer role. Do step 6.
• "You need to have been in the server for 7 days." or "You need one of these roles to apply". These are the limits you set with /apps settings. Change them, or clear one with /apps settings form:moderator clear:Minimum days.
• "You already have an application waiting for review." Each member can have one open application per form.
• "Their DMs are closed, so they weren't told." The decision still counted. Let them know another way.
• A reviewer gets "You don't have access to this command here." on /apps queue. By default /apps is for admins. Reviewers can still use the buttons in the review channel. To let them use /apps queue, add their role to /apps on the dashboard's Permissions page. See Choose who can use each command.