Community
Forms, questions, submissions, staff review, and logging.
Applications are structured forms. You define questions, members submit answers, staff approve or reject, and the decision can be logged.
/applicationsCreate and manage applications./settingsApplication module options and logs.Run /applications to create a form. Give it a name staff will recognise in review queues. Limit who can submit if the form is for a specific department.
Add the questions you actually need. Question types depend on the installed version (short text is the baseline). Do not invent field types that the command does not offer.
Members submit through /applications or a published panel. They should receive an acknowledgement if the version supports one. Duplicate submission policy is version-specific.
Staff with permission open the submission, read the answers, and approve or reject. Approval does not automatically assign Discord roles unless your configuration says so — confirm rather than assume.
When logging is enabled, submissions and decisions write to the configured channel. Keep that channel staff-only; applications often contain personal answers.