Applications

Application forms collect answers from members who want to join a team, such as staff or event hosts. Staff set forms up with /application in Discord or on the dashboard page Moderation → Applications. /application needs the Manage Server permission; the dashboard page, like the rest of the dashboard, needs the server owner or the Administrator permission.

Set up a form

1. Create the form: /application create name:Staff application. Choose where members answer with type: in DMs, on the website, or both.
2. Add questions with /application question add.
3. Choose the pending, accepted and denied channels with /application settings. The bot warns you when it is missing a permission in one of them (View Channel, Send Messages, Embed Links, and the thread permissions when staff threads are on).
4. Check everything with /application view. Use section: to see the roles, messages or questions in full.

Start typing in the form option and Discord suggests your forms. A form can be turned off with /application disable, renamed with /application rename and deleted with /application delete, which asks you to confirm first and also removes the form’s submissions.

Questions

Each form can have up to 25 questions, asked in order. Change the order with /application question move. There are three kinds:

• Text: a written answer. Set the shortest and longest answer with min-length and max-length (up to 1024 characters).
• Multiple choice: 2 to 25 choices, separated by | or new lines. min-selections and max-selections set how many can be picked (one by default).
• Role select: members pick from up to 25 roles. grant decides whether the picked roles are given never, when the application is submitted, or when it is accepted.

Mark a question optional with required:false. Options that do not fit the question type, such as choices on a text question, are refused with an explanation.

Roles

Add roles with /application roles add. Each form has these lists:

A role cannot be in both lists of a pair (given and removed at the same moment, or both required and restricted).

Messages

Each form has five messages: start, confirmation, completion, accepted and denied. Write one with /application messages set. Without text it opens an editor; with text, type \n for a new line. /application messages preview shows the result and reset goes back to the built-in wording. These variables are filled in:

Applying

Members apply with /apply (start typing and Discord suggests the forms that are open) or from a panel. If they can’t apply yet, the bot says exactly why: submissions are closed, a required role is missing, they have a restricted role, the cooldown hasn’t passed (with the time they can apply again), an earlier application is still waiting for review, the form has no questions, or they already have an application in progress (with buttons to jump to it or cancel it).

• In DMs: the bot sends a Start application message (valid for 15 minutes). Questions then come one at a time: text questions are answered by replying, multiple choice and role select questions with a menu, and optional questions have a Skip Question button. The last step lists every answer with Submit and Cancel. Typing cancel stops at any time. A member can answer for one server at a time in DMs.
• DMs closed: if the bot can’t DM someone, it explains how to turn on Direct Messages for the server (Server menu → Privacy Settings → Direct Messages), and offers the website link when the form allows it.
• On the website: website forms reply with an Apply on the website button; forms set to both offer it alongside DMs.
• Time limit: the clock starts when the member presses Start. When it runs out the application is removed and the member gets a DM saying so.

Panels

A panel is a message members apply from. /application panel create channel:#apply form:Staff application posts one with a menu (type:select, the default) or one button per form (type:button). Add or remove forms, and change the title, text ( for a new line), color, image, footer or menu placeholder with /application panel edit; none clears the color, image, footer or placeholder. Saving updates the posted message, or posts it again if it was deleted. /application panel send posts a copy elsewhere, list shows every panel, and delete removes the panel and its message. Up to 25 panels per server and 25 forms per panel; renaming, opening, closing or deleting a form updates its panels.

Reviewing

New applications are posted in the pending channel with the applicant, their account age, join date and roles (unless Show stats is off), every answer, and the ping roles mentioned. Very long answers are shortened to fit Discord’s limits; Full answers shows them all, and the staff thread (when Staff thread is on) gets them in full too. Without a pending channel, applications wait for /application review and the dashboard.

Accept and Deny ask for an optional reason, which the applicant sees in their accepted or denied message. Only application managers and members with Manage Server can review, and nobody can review their own application (except administrators). If two staff decide at once, only the first decision counts. Accepting gives the accepted roles and role select picks set to “on accept”; denying gives the denied roles; both remove the pending roles and the roles in the matching “removed” list. Any role the bot couldn’t change is listed for the reviewer. The staff message then moves to the accepted or denied log channel (without the answers when Hide answers is on), or is updated in place when no log channel is set. /application review submission: does the same from a command.

Leaving the server

When a member leaves, their applications in progress end (they get a DM). With When an applicant leaves → Deny automatically, their pending applications are also denied and the staff message says so; no roles change and no DM is sent.

History and export

/application history user:@member lists a member’s applications with the outcome, reviewer and reason, 10 per page. /application export form:Staff application sends a CSV file (opens in Excel, Google Sheets or Numbers) of up to the newest 10,000 submissions, optionally only pending, accepted or denied ones. The dashboard Application submissions page lists, filters and exports them too (see below).

On the dashboard

Three dashboard pages under Moderation manage applications:

• Applications: build forms. Questions can be put in order with the up and down arrows on each question. The page also links each website form (with a Copy button).
• Application submissions: every submitted application. Filter by form, status (pending, accepted, denied) and applicant user ID, sort newest or oldest first, and choose 10 to 100 per page. The counters at the top (total, pending, accepted, denied) follow the form and applicant filters; click one to filter by it. Click an application to read every answer, the applicant (with their avatar and whether they are still in the server), the reviewer and reason, links to the staff messages, and their previous applications. Accept and Deny ask for an optional reason and do exactly what the Discord buttons do: roles change, the staff message moves or is updated, and the applicant gets their DM. The page then lists the roles given and removed, any role the bot couldn’t change, whether the DM was delivered and where the decision was logged. Owners and administrators can also Delete an application; deleting a pending one removes its pending roles and the Accept and Deny buttons from the staff message. Choose a form to Export CSV.
• Application panels: create, edit and delete panels without commands: the channel (choosing another one moves the panel and removes the old message), menu or buttons, title, text, color, image, footer, menu placeholder, and which forms it lists in which order. Send copy posts an untracked copy in another channel.

Who can review on the dashboard

Building forms and panels needs the server owner or the Administrator permission, like the rest of the dashboard. The submissions page is open to more people: members with Manage Server see every form, and members who hold a form’s Application managers role see that form only. They open it from the server in their dashboard (or from an Open in dashboard button) and get just the submissions page for the forms they manage. Nobody can accept or deny their own application unless they are an administrator.

Applying on the website

Forms set to On the website or Both have a link, /apply/<server id>/<form id>, shown on the Applications page and on the Apply on the website buttons the bot sends. Members sign in with Discord, see the start message and press Start application. They then have the form’s time limit, or 24 hours when it has none, to answer every question, review their answers and submit. Answers are kept in their browser until they submit. A member can have one application in progress per server, whether in DMs or on the website; the page explains why if they can’t apply (with the same reasons as /apply) and offers to cancel an application already in progress. Submitting does exactly what submitting in DMs does: the same answer checks, pending roles, the post in the pending channel with the ping roles, and the staff thread.

Members can see their own applications, with the outcome and the reason, at /apply/<server id>. Staff names and messages are never shown there.

Limits

• 25 forms per server and 25 questions per form.
• Form names are up to 100 characters and must be different from each other (capital letters do not count).
• Cooldown: how long a member waits between applications, up to one year, or none.
• Time limit: how long a member has to finish, from 1 minute to 7 days, or none.
• Messages are up to 2000 characters; questions up to 500.