Forms

A form is a list of questions and a set of rules about who may answer them. Members fill it in from a button in a channel, through /form apply, on a public web page, or from a DM you send, and every submission lands in one review queue.

1Building a form

1. 1

   Switch it on

   Utilities → Forms.

2. 2

   Create a form

   Start from a template (Staff Application, Anonymous Feedback and Punishment Appeal) or from scratch with New form. Up to 10 forms per server.

3. 3

   Add questions

   Up to 25 across five pages.

4. 4

   Set the rules

   Who may submit, how often, when it is open, and where submissions go.

5. 5

   Share it

   Post it in a Form channel with an open button or a dropdown, let members run /form apply, publish a web link, or DM it to up to 100 members at a time with /form send. Any combination works, and a form reached only by DM stays invite-only.

Question types

• Every question can be required, carry a description and a placeholder, and free-text answers can have a length range and a pattern. A number can have a range.
• Choice questions take up to 25 options, and a file upload takes up to ten files.
• A form with a Discord picker or a file upload in it works inside Discord only. The web page can't offer either (a picker would publish the server's member, role and channel lists), so its web link can't be published.

Rules

Active / Paused

The switch on the form's card. A paused form keeps its message up with the button grayed out, and keeps its submissions; it just takes no new ones.

Opens at / Closes at

An optional window, in your local time zone. Members are turned away outside it.

Allowed roles and ignored roles

Who may submit. Ignored roles never can.

Minimum account age and time in server

In days, against brand-new accounts. 0 is off.

One submission per member

Or as many as they like.

Submission cooldown

On for every new form, 5 minutes by default: how long before the same member may submit again, from a minute to a year.

Stop after

Close the form once it holds this many submissions. 0 is no cap.

History kept

How many decided submissions stay on the dashboard: 1,000 per form by default, adjustable from 100 to 5,000. Past it the oldest decided ones are removed once a day. Pending reviews are never removed.

Submissions channel

Where each submission arrives as a card for review. Leave it empty to keep them on the dashboard only. Create a thread for each submission, public or private, gives reviewers somewhere to talk, and can archive itself after the decision.

When someone submits

Anonymous submissions hide the member's name and avatar from reviewers (Arclo still knows who it was, so cooldowns and one-per-member keep working). Roles can be given or taken the moment they submit, roles can be pinged in the submissions channel, and DM the confirmation sends the member a copy.

Reviewing

Every submission is in one queue on the dashboard, searchable and filtered by status, and, if you set a submissions channel, a card in Discord with Approve and Deny buttons. A decision can carry a reason, and with DM the decision on (the default) the member is told either way.

• Approval and denial each have their own roles to give and take.
• Require a reason when denying and Delete the card after a decision are switches. Collect only removes the buttons, for a form you never judge, feedback for instance.
• Submission viewer roles may read submissions and Submission manager roles may decide them, up to 10 each, set per form or for every form on the Settings tab. Neither needs dashboard access, so a recruiter can read applications without Manage Server. A Bot Master or a Forms page grant sees every submission, but approves or denies only with a manager role.
• The public page is the same form your members fill in, so what you see is what they answered.

Commands