Applications

The Applications module lets staff build application forms — staff applications, partner applications, whatever your server needs — post them as a panel, and let members apply through Discord's native modal forms. Submissions land in a review channel with Accept/Deny buttons.

Creating an application

/application create name:<name> review_channel:<channel> [cooldown] [max_active] [required_role] [blocked_role] [accept_role] [deny_role] [reviewer_role]

An application starts with no questions — add those next.

Adding and removing questions

/application addquestion application:<name> question:<text> [required] [max_length] [style]

An application can hold up to 25 questions. Duplicate question text (exact match, case-insensitive) is rejected.

/application removequestion application:<name> number:<n>

Removes a question by its number, as shown in /application view.

Posting a panel

/application panel title:<text> description:<text> channel:<channel> application_1:<name> [application_2] [application_3] [application_4] [application_5]

A panel can include up to 5 applications. It always posts as a dropdown ("Make a selection") in the target channel, even if you only add one application — the panel format doesn't change based on how many you're offering. Every application on the panel needs at least one question configured first, or the command rejects it.

Managing applications

Reviewer roles

/application reviewers application:<name> [role]

Sets which role can Accept/Deny submissions for a specific application. Admins can always review, regardless of this setting — a reviewer role adds to that, it never replaces it, so a deleted or misconfigured role can't lock admins out of their own application. Leave role empty to clear it back to admins-only.

How members apply

1. A member clicks an application in the panel dropdown
2. NexaBot checks eligibility: required role, blocked role, cooldown, and whether they already have a pending submission at the max_active limit
3. If eligible, a modal opens with up to 5 questions at a time — if an application has more than 5 questions, answering a page shows a Continue button that opens the next modal
4. On the final page, the submission is created and the member gets:
   • An in-channel confirmation showing exactly what they answered
   • A DM with a copy of the same answers (best-effort — this doesn't block submission if their DMs are closed)

How staff review submissions

Each submission posts to the review channel as an embed with the applicant's answers and five buttons:

Whichever reason is given (if any) is sent to the applicant by DM along with the decision. The accept_role or deny_role configured on the application, if any, is applied automatically — respecting role hierarchy, so NexaBot won't try to grant a role positioned above its own.

Once a submission is decided, the review card's buttons are disabled and the embed updates to show who decided it. A submission can only be decided once — if two staff members click at the same time, only the first one goes through.

Limits