Applications

Applications let people request access to your community by filling out a form you design, instead of being whitelisted by hand. Submissions land in a review queue where staff accept or decline them.

On the Applications page, build your form from question blocks: short answer, paragraph, multiple choice, and more. Set which questions are required and reorder them freely.

• /apply command: opens the form as a Discord modal (a form with more than five questions, or a question over 100 characters, opens by DM or on the web instead). A Verify with Microsoft question is answered by signing in first, never typed (an optional one can be skipped, on every surface), and an answer that fails a check comes back with Edit answers so nothing has to be retyped
• Channel panel: a button or select menu you post to a channel (create these under Applications > Panels)
• Web link: a shareable URL that opens the form in the browser. The applicant signs in with Discord and has to be a member of the server who isn't banned

Open the review queue to read each submission, then accept or decline. Accepting runs the actions you configured (role, whitelist, welcome message) atomically, so an applicant is never half-processed. The whitelist step needs a paid plan and a server whose whitelist Madsi manages; otherwise accepting still assigns the role and sends the welcome, and you add the player on the Whitelist page. If an accepted applicant is later banned from your Discord server, ban sync also takes the Minecraft account they applied with off the whitelist (unless Discord ban → Minecraft ban is off or the reason has dc-only), even after the form or the submission is deleted. Lifting the ban doesn't add it back: re-add them on the Whitelist page. The Analytics tab summarises volume and top reviewers.

Request info DMs the applicant your note with an Update my application button. It reopens their answers for editing (or, on a form too long for one Discord form, a reply box), and the submission goes back to the queue as pending.

Someone accepted through a form can't apply to it again unless the form's Allow re-applying after acceptance switch is on. To make an exception for one person, press Allow re-applying on their accepted submission.

A form with a Time limit to complete gives each applicant one window, which starts when they press Start and is shared between the web form and Discord DMs. If it runs out before they submit, the form's cooldown applies before they can start again, so set one to stop people reading the questions and starting over.

Under Data retention, choose how long the answers of accepted and of denied submissions are kept: 30 days, 90 days, 1 year or forever (the default). After that the answers are deleted and the review post in Discord is edited to drop them; a denied submission also loses its Minecraft name and the staff note, in the queue and in the audit log. A submission withdrawn because the applicant left follows the denied period. Posts already made to the Applications log channel are not edited. Who applied, the outcome and when it was decided stay. Deleting a form, or an applicant deleting their Madsi account, deletes the submissions and their review posts in Discord, with any staff thread started off a post when Madsi has the Manage Threads permission; the audit log keeps its entries about them without the staff notes or Minecraft names. Changing how long an existing form keeps answers needs the Applications · Delete permission, since it deletes answers already stored.