Building a Form

The Forms Builder turns a set of questions into a DM questionnaire. A member runs /submit (or clicks a configured submit reaction), answers the questions in a direct message with GiselleBot, and the finished submission is posted to an approval channel where your team can accept or reject it.

This guide builds one working form from start to finish. The Forms Builder reference covers every field and the optional Trello integration in more detail.

Before you start

You need Manage Server (or Administrator) to create and edit forms. Module authorization is not enough for the authoring side.
Members who should review submissions need the forms module enabled for their role on the Command Permissions page. Module-authorized members can accept or reject any form.
Decide which channel will receive submissions for approval. This field is mandatory.
Decide which roles may accept or reject submissions for this form. These per-form roles narrow the reviewer list further.

The forms module is manager-only by default. If your role cannot open the Forms page at all, authorize it on the Command Permissions page first - see Configuring Permissions.

Note

Premium: each server can have 3 forms by default, 10 with Base, and 20 with Power. See Premium Perks.

Step 1: Open the Forms page

On the dashboard, choose your server and open Forms. The page has four parts:

Current Forms - the list of forms and their ON/OFF state.
Guild Form Settings - the server-wide Auto-Delete Submit Messages toggle.
Reaction Messages - messages that start a submission when a member reacts.
Blacklist - users who cannot see or submit any of the server's forms.

Trello pairing appears on the same page when the Trello integration is available.

Step 2: Create the form

Choose Add New Form. The form editor opens with a blank form and no questions.

Fill in the basic settings first:

Form Title - what members see when they choose a form.
Form Color - the embed color used in the submission message.

Leave Enable Form off until the form is finished. A disabled form is not offered to members.

Step 3: Choose the approval channel

Under Channel Settings:

Forms Approval Channel - where every submission is posted for review. This is mandatory; the form will not work without it.
Accepted Forms Forward Channels - optional extra channels that receive a summary after a submission is accepted. Leave empty if the approval channel is enough.

Make sure GiselleBot can send messages in each channel you select.

Step 4: Add the questions

Under Form Steps, choose Add Step for each question. Every step has the same building blocks:

Question Type - Open-ended accepts a written answer, Multiple-choice offers a set of answers.
Question - the text sent to the member in the DM.
Possible Answers (multiple-choice only) - a semicolon-separated list, up to 20 entries, for example Yes; No; Not applicable.
Validation Words (open-ended only) - an optional semicolon-separated list. The answer is rejected unless it contains at least one of the words. Leave empty to accept any answer.
Question Alias - an optional short label used in the posted submission instead of the full question. Recommended when the question is long.
Characters Limit (open-ended only) - an optional minimum and maximum answer length.
Trello Mapping - optional; choose what this answer becomes on a Trello card when Trello share mode is used.

Use the arrow buttons to reorder steps and the trash button to delete one. The order on screen is the order members answer them in.

Warning

A form with no steps cannot be used. Add at least one question before enabling it.

Step 5: Decide how submissions behave

Under Mention Settings and Form Behavior, choose what happens around a submission:

Role Authorized to Accept Forms - the roles that may accept or reject this form's submissions. Module-authorized members can review any form regardless; this field narrows the list for this form.
Mention Authorized Roles on Form Submissions - pings those roles when a new submission arrives.
Role Mentioned on Form Accepted - optionally pings a role when a submission is accepted.
Enable Upvote / Enable Downvote - adds vote reactions to the posted submission.
Highlight Attachments - calls out attachments in the posted submission.
Enable Priority Selection - lets reviewers assign a priority to a submission.
Anonymize Public Submissions - hides the submitter's identity on the public summary.
Anonymize Rejection Messages - hides the reviewer's identity in the rejection DM.

Pick only the options you will actually use. Each extra option adds noise to the approval channel.

Under Trello Integration, choose the Share Mode:

Discord - the default. Submissions stay in Discord and are posted to the approval channel.
Trello - accepted submissions become Trello cards. This requires pairing the server with a Trello team and selecting a board, and the form cannot be saved in Trello mode without one.

The Forms Builder reference covers pairing, the 6-digit verification step, and the 5-minute timeout. If you are building your first form, start with Discord mode and add Trello later.

Warning

Form settings are fixed once a submission is in the approval queue. Changing the form later does not change submissions that already exist - including which Trello board they use. Finish the settings before you ask members to submit.

Step 7: Enable the form

Turn on Enable Form, then choose Update Form to save. The form now appears in the list as ON and is offered to members.

If you only want to check it first, leave it disabled while you review the questions and channels, then enable it once everything looks right.

Step 8: Collect submissions

Members can start a submission in two ways:

Run /submit in the server and pick the form in the DM that follows. This only works inside a server, not in a DM with the bot.
React with the configured emoji on a message set up under Reaction Messages.

Reviewers accept or reject each submission from the approval channel. Accepted submissions are forwarded to any forward channels you configured. With Auto-Delete Submit Messages enabled, the message that started the submission is deleted after it is submitted.

To stop someone from using the forms, add them to the Blacklist on the Forms page. Blacklisted users cannot see or submit any of the server's forms.

Summary

A working form needs four things: a title, an approval channel, at least one question, and the form enabled. Everything else - filters, voting, Trello, anonymization - is optional tuning.