Application management
Submitt Applications are built from one simple editor. Create the Application with a name, add questions, choose the Application channel and review channel, select reviewer roles, optionally choose the role given when accepted, then save and publish. Required/blocked roles, extra role automation, Paths, custom review stages and Multi-Panels stay under Advanced Settings.
Adding, editing, or deleting an Application question updates the builder immediately without reloading the page. Other unsaved editor changes are saved before structural changes are applied.
Discord limits one modal to five components, so Submitt automatically splits longer Applications across multiple modal pages. Long question prompts can use two components—a full prompt display plus the answer input—so nine long questions may appear as five Discord pages. The applicant continues through every page before the Application is submitted.
Use Copy to Server to reuse an Application on another licensed server. Submitt copies the Application content, questions, Paths, stages, decision messages, cooldown and limits, then creates a disabled draft on the destination. Discord channels, reviewer/eligibility roles, approval roles, role automation, published message IDs and submission history are intentionally cleared so they can be remapped for the target server.
Use Duplicate to clone the current Application's channels, reviewer and eligibility roles, Paths, questions, stages, role actions, decision messages and limits. The duplicate starts disabled and unpublished and does not copy submissions, reviews or the published Discord message.
Applications vs Multi-Panels
One independent questionnaire and review workflow such as Support Team Application, Recruitment Team Application, LSPD Application or Civilian Application. It owns its questions, reviewers, eligibility, cooldowns, stages, decision messages, role automation and history.
One public Discord embed that groups 2–25 existing Applications behind buttons or a dropdown menu. It owns presentation only; the Applications remain independent.
An Application can be published individually, included in one or more Multi-Panels, or both. Deleting a Multi-Panel never deletes its Applications or submission history.
Create an Application
Choose Add Application from the Applications manager to open a dedicated Application builder instead of creating it inline. Setup is divided into collapsible sections for Appearance, Discord & Review, Decision Messages, Access Control, Role Automation, Application Limits, and Questions & Paths.
Open Dashboard → Applications, type the Application name, and press Create. Submitt immediately opens the Application editor. There is no setup wizard and no requirement to configure channels, roles, Paths or review stages before you start writing questions.
The Application editor
The normal setup lives on one page. Questions are at the top because they are the core of the Application. The remaining settings are grouped into Application, Discord, Role Settings and Messages. The editor uses one Save All Changes action for every edited section on the page, including advanced role settings and existing Path edits. Saving happens in place without reloading the editor.
Press Add Question, enter the question, choose the answer type and decide whether it is required. Help text, validation, ordering and Path assignment stay under Advanced options.
Edit the internal name, public description and Open/Closed state. Public title, cooldown and max-active limits are tucked under Advanced application options.
Choose the public Application channel, private review channel, reviewer roles and the optional role automatically given when an applicant is accepted.
Required/blocked roles and extra add/remove actions on submit, accept or deny are hidden under Advanced Settings so normal Application setup stays short.
Set the default accepted and denied messages without changing the staff review controls.
Once the Application has questions, is open and has an Application Channel, publish it from the editor header.
Application Paths, custom review stages, CSV export and deletion controls are collapsed under Advanced Settings. Most servers never need to open that area.
Adding, editing, or deleting a question, Path, or review stage automatically saves other changed Application sections first. Publishing also saves pending changes before updating Discord, so a small action elsewhere on the page does not wipe fields you were still editing.
Deleting an Application
You can delete an Application even after people have submitted it. Deleting removes the Application from normal configuration, disables new submissions, removes its individual Discord launcher, and removes it from Combined Panels. Historical submissions are intentionally retained, including answers, reviewer actions, decisions, applicant history and timestamps, so past records remain available in the review/history views.
Submitt always shows a confirmation dialog before an Application or Application Multi-Panel is deleted. Nothing is removed until you explicitly confirm the deletion.
Create a Multi-Panel
When several Applications belong together, create a Multi-Panel instead of publishing several separate embeds into the same Discord channel. For example, a single Paradise Network Team Applications Multi-Panel can contain Support Team, Application Team and Recruitment Team Applications.
Removing an Application from a Multi-Panel, deleting the Multi-Panel, or publishing the Application somewhere else does not alter the Application configuration or its submission history.
Application Questions
Questions are the primary content of an Application. Press Add Question to open the compact question editor. Question prompts can be up to 250 characters. The normal view asks only for the question, answer type and whether it is required. Choice questions also ask for the choices. Help text, placeholder text, validation, ordering and optional Path assignment are available under Advanced options.
Optional Application Paths
Application Paths are an advanced option inside one Application. Use them only when variants share the same overall review workflow but need different questions or decision messages. For genuinely separate applications such as Support Team and Recruitment Team, create separate Applications and group them with a Multi-Panel instead. When Paths are configured, Submitt asks which Path the applicant wants before showing shared questions plus Path-specific questions.
Decision-message variables are {user}, {username}, {server}, {application}, {role} and {reviewer}. Normal Applications use the default approval/denial DMs from Application settings. When a Path supplies its own message, that Path-specific message overrides the default.
Question types
Best for concise answers such as age requirement confirmation, username or short identifier.
Best for motivations, scenarios, experience and other detailed written answers.
Applicant selects one option from up to 25 configured choices.
Applicant can select multiple options, with a configurable maximum number of selections.
Each question can include help text, placeholder text, required/optional behavior and validation. Text questions support minimum/maximum length. Choice questions support up to 25 options. Discord's native Label component has a shorter prompt limit, so Submitt automatically renders questions longer than 45 characters as a Text Display above the answer control instead of truncating them. Modal pages are packed automatically within Discord's component limit, and draft progress can be resumed during the configured draft window.
Eligibility rules
Use required roles when only certain members should be allowed to apply. If multiple required roles are selected, the applicant must have every selected role. Use blocked roles to stop members with any selected role from submitting. Typical examples include blocking already-employed members from applying again or requiring a Verified Member role.
Opening and closing applications
The form can be enabled or closed without deleting it. Closing a form preserves existing submissions and configuration while preventing new applications. This is preferable to deletion for seasonal recruitment or departments that temporarily stop hiring.
Custom review stages
Stages let your staff represent the real process instead of jumping directly from Submitted to Accepted. Examples include Initial Review, Interview Required, Interview Complete, Command Review and Final Decision. Reviewers can move applications through these stages from the dashboard/Discord review flow.
If you use a stage containing “Interview”, Submitt recognizes that as an interview-oriented stage for workflow presentation. Keep stage names clear enough that every reviewer understands what action is expected next.
Claiming applications
Reviewers can claim a submission so the team knows who is actively handling it. Claiming helps prevent duplicate work but should not be used to hide an application from other authorized reviewers. Owners can still see the complete queue and history from the dashboard.
Decision actions
Reviewers can accept, deny, waitlist, archive or reopen according to the current status. Denials can require a reason so the decision remains auditable. Reopening restores a previously finalized application when an owner or reviewer needs to continue the workflow.
Applicant profiles and history
Every submitted applicant has a server-specific profile that brings together their application history across all forms. Reviewers can press Applicant History directly on the Discord review card for an ephemeral history summary, or open the full dashboard profile from the review queue, submission page or Discord card to see previous outcomes, stages, reviewer decision notes and links back to the original submissions.
This is useful for recurring staff, faction, whitelist or development-team applications because reviewers can see whether the same Discord user was previously accepted, denied, waitlisted or reviewed on another form before making a new decision.
CSV submission export
Each Application can export its submitted application history as CSV from the form configuration page. The export includes applicant identity, status, stage, dates, claim/decision information, review actions and the answers to that form's questions.
Role automation
Each form can configure Discord role additions/removals on submission, acceptance and denial. For example, submitting an LEO application could add an Applicant role; acceptance could remove Applicant and add LEO; denial could remove Applicant and add a temporary cooldown/status role if your community uses one.
The Submitt bot role must be above every role it is expected to add or remove. If automation does not fire, check Dashboard → Setup before editing the application logic.
Temporary Discord API or bot outages do not erase reviewer roles, eligibility roles, or role automation if you save other Application settings while channel/role data is unavailable.
Publishing Applications and Multi-Panels
Choose an Application Channel in the editor, save your changes, then press Publish Application in the editor header. Publishing again updates the existing message. Multi-Panels remain an advanced option on the main Applications page when several independent Applications should share one public Discord message.
Applicant experience
Form lifecycle and historical data
Forms with submission history should be closed rather than deleted. Submitt protects historical application records so decisions and answers remain auditable. Use descriptive internal names when creating replacements so staff can tell old and current forms apart.