FormsPrivate applications with a reaction-powered editor.

Publishing & Review

Open a form, publish its reaction panel, and review the submissions your team receives.

Before you open a form

  • Add at least one question.
  • Set a panel channel where members can see and react to the form.
  • Set a review channel where your team will receive submissions.
  • Optionally configure reviewer roles, required roles, cooldowns, and message templates.
  • Preview the panel to check the title, description, color, image, and emoji.
Fluxer
f!forms preview StaffApp
f!forms open StaffApp
f!forms panel StaffApp

Draft status

A new form starts as a draft. The preview footer shows Draft until the form is opened, then Open or Closed as its status changes.

Publishing the panel

Opening a form makes it available to members, but it does not post the panel by itself. Run f!forms panel <form> to publish it. The bot posts a panel with the configured emoji reaction and can send it to a different channel if you include a channel argument.

Re-running the command replaces the existing panel in the configured panel channel. This is useful after changing the form name, description, color, image, or emoji.

What members see

Members react to the panel with its emoji. The bot opens a DM, introduces the form, and asks each question in order. Answers are collected privately and sent to the review channel when the last question is answered.

  • Short-text and paragraph questions are answered by replying in the DM.
  • Choice questions can be answered by reacting to an option or replying with its number.
  • Type back to revisit the previous question.
  • Type skip to leave an optional question blank.
  • Type cancel to withdraw the draft.

DMs must be open

The form is completed in DMs, so members need to allow direct messages from the community. If the bot cannot create a DM, the member sees an error and cannot start the form.

Submission rules

Before a member starts, the bot checks the form status, required roles, pending or in-progress submissions, the per-member accepted limit, and the cooldown. A member with an unfinished draft resumes it instead of starting over.

  • Multiple submissions - when off, a member with a pending submission cannot start another.
  • Accepted limit - 0 means unlimited; otherwise the cap applies to that member.
  • Cooldown - measured from the member's latest submission.
  • Required roles - members without one of the configured roles cannot start.

Reviewing a submission

Finished submissions are posted in the review channel. Reviewers can use the reaction controls directly on the review message, or manage reviews with commands. Review messages show up to ten questions per page; the arrow reactions page through longer submissions.

  • ✅ Accept - approves the submission and updates the review embed.
  • ❌ Decline - asks the reviewer for a reason, then declines the submission.
  • Reason - saved with the submission and included in the decline DM.
  • Repost - restores a pending review message if the original was deleted.
Review commands
f!forms submissions StaffApp
f!forms submission 123456789012345678
f!forms reason 123456789012345678 Not enough availability
f!forms repost 123456789012345678
f!forms withdraw 123456789012345678

Applicant notifications

Accepted and declined applicants are DMed when applicant decision DMs are enabled. Custom accept and decline templates can include {form}, {user}, and {reason}.

Closing, editing, and deleting

Closing a form stops new submissions but lets pending reviews finish. You can reopen it later with f!forms open <form>. Deleting a form is permanent and also removes its panel and submissions.

Fluxer
f!forms close StaffApp
f!forms list
f!forms view StaffApp
f!forms delete StaffApp confirm
To change questions or settings after publishing, open Form Menu again with f!forms edit <form>. Republish the panel afterward if the panel content changed.