Applications
Applications are your whitelist, staff and department forms. Members answer the questions in their DMs one at a time, staff review the finished submission in a channel with Accept and Deny buttons, and the accept role is handed out automatically.
Where: Dashboard โ Support desk โ Applications ยท In Discord: /apply for members, /application for admins
#How it works
- A member starts a form: from the application panel, or with
/apply. - FiveUnity DMs them a confirmation with Start application and Cancel application.
- The questions arrive one at a time in the DM. They have 3 hours to finish.
- At the end they see every answer and press Submit application.
- The submission is posted to that form's review channel with Accept and Deny buttons.
- A staff member decides, optionally with a reason. The role is applied and the member is DMed the outcome.
#Set it up
- Under Create application form, give it a Short name (used by
/applyand in the dashboard), a Title, an Accept role and a Review channel. Leave the accept role empty and anApplicantrole is created for you. - The form opens in the editor. Add your questions and press Save form.
- Under Publish application panel, pick a channel and a style, then press Publish panel.
#Application settings
| Setting | What it does |
|---|---|
| Module enabled | Master switch. Off, every form refuses new applications and any half-finished one cannot be submitted. |
| Default log channel | The channel you use for applications on this server. |
Each form has its own Review channel and that is where its submissions are posted. The defaults above do not override it.
An application is answered in the member's DMs and is held in memory while they answer. If the bot restarts mid-questionnaire the answers are lost; the next message the member sends gets a reply telling them so and asking them to run /apply again. Sessions also expire after three hours.
Deleting a form leaves its past submissions in place so your review history survives. Any submission still awaiting a decision is closed with the reason Application form deleted, and its review buttons are removed. If it was the last form on the server, the module is switched off.
#Forms
Open a form with Edit form to change everything in place.
| Setting | What it does |
|---|---|
| Title | The name members see on the panel and in their DMs. |
| Accept role | Given when a submission is accepted. |
| Review channel | Where submissions are posted for staff. |
| Accepting submissions | Open or Closed. Closed keeps the form but turns members away. |
| Description | Shown on the panel and in the DM confirmation. |
#Questions
Questions are asked one at a time in DMs, in the order you list them. Each has a type and a Required switch, and can be reordered or removed.
| Type | How the member answers |
|---|---|
| Short answer | Sends a message. |
| Paragraph | Sends a message. Attachments are kept alongside the text. |
| Multiple choice | Picks from a dropdown, or types one of the options. Needs at least two options; up to 25. |
| Number | Sends a number. Anything else is rejected and re-asked. |
An optional question can be skipped by typing skip, or with the Skip this question entry in a multiple-choice dropdown.
#Behaviour
| Setting | What it does |
|---|---|
| Cooldown (hours) | How long a member waits between attempts. 0 disables it; the maximum is 720 hours. |
| Ping role | Pinged in the review channel when a new submission arrives. |
| Deny role | Given when a submission is denied. |
| DM the result | DMs the applicant when their submission is accepted or denied. |
| Staff voting | Adds ๐ / ๐ buttons to each submission so staff can vote before deciding. |
| Discussion thread | Opens a thread on each submission, archived automatically when it is decided. |
#Who can apply
| Setting | What it does |
|---|---|
| Required roles | Applicants need at least one of these. Empty allows everyone. |
| Blacklisted roles | Anyone with one of these cannot apply. |
A member who already has a pending submission for a form cannot start it again until staff decide.
#Messages
Accept DM, Deny DM and After-submit message replace the built-in wording. Leave one empty for the default. Placeholders: {user}, {server}, {application}, and {reason} on the accept and deny messages. If you give a reason and your message does not use {reason}, it is appended for you.
#The application panels
A server can keep several panels, each with its own name, channel and list of forms: every form in #apply-here, a staff-only panel with the internal forms elsewhere, and so on. Each panel is published and refreshed on its own.
| Style | What members see |
|---|---|
| Buttons | One button per form. |
| Dropdown | A single menu listing every form. |
By default a panel offers every form that is open and has at least one question, up to 25. Pick forms from the dashboard's form list to narrow a panel to just those; a narrowed panel keeps offering exactly those forms when it is republished, even after newer forms are created.
Members can also skip the panels entirely and run /apply, or /apply application:<name> for a specific form. With one form open, /apply starts it straight away.
#Keeping a panel current
A panel is a snapshot: a form you add, retitle, close or delete afterwards does not change what is already posted.
Republish rewrites that panel's message in place with the forms as they stand now. The panel keeps its channel, its position in the channel and its message link, so nothing members have pinned or linked breaks, and no second panel appears beside the first. Other panels are untouched, so you can refresh the public panel without disturbing the staff-only one.
Republish is available once a panel has been published: from the dashboard, or by running /application panel again with the same panel name. If the panel message has since been deleted, Republish posts a fresh one in the same channel and tells you it did.
Publish panel posts the panel to whichever channel you pick and removes the earlier message of the panel with the same name, so a panel never has two live messages. Use it to move a panel; use Republish to refresh it where it is. Publishing under a new name adds a second panel alongside the first.
Everything happens in DMs, so a member with direct messages closed for your server cannot apply. FiveUnity tells them exactly which privacy setting to change.
#Reviewing a submission
The review message shows every answer, the applicant and the form name. Staff press Accept or Deny and can add an optional reason, up to 500 characters, which goes into the applicant's DM.
Once decided, the message is recoloured and relabelled, the buttons are removed, the role is applied, any discussion thread is archived, and the reviewer gets a private confirmation naming the role given and whether the DM landed. Only the first decision counts: a second staff member is told who already decided it.
#In Discord
Admins can do the same work with /application:
| Command | What it does |
|---|---|
/application create log-channel:<channel> | Creates an empty form. |
/application edit name:<name> | Changes the title, description, accept role, deny role, ping role or log channel. |
/application settings name:<name> | Cooldown, open/closed, required and blacklisted roles, DM on decision, voting, threads and the custom messages. |
/application questions add name:<name> | Adds a question. |
/application questions remove name:<name> number:<n> | Removes one by number. |
/application list | Lists every form and its questions. |
/application panel | Posts a named application panel. Publish again with the same panel name to replace it; another name adds a second panel. |
/application submissions | Lists recent submissions, filtered by form, status or applicant. |
/application delete name:<name> | Deletes a form. Submissions already posted stay in the review channel. |
#Tips
Put the questions that disqualify someone fastest (age, timezone, whether they have read the rules) at the top. A short form you actually read beats a long one you skim.
Set a cooldown of 24 to 168 hours on whitelist forms. It stops a denied applicant reapplying the same evening.
#Related
- Tickets: support channels, which are separate from applications.
- Permissions: who can run
/application. - Roles: the roles you hand out on acceptance.