How forms work

A form is a web page FlaviBot hosts for your server: you build it on the dashboard, you share its link, and the answers come back to your staff in Discord. This page answers what a form can hold, who is allowed to fill one in, and how many you get.

Staff applications, feedback rounds, event sign-ups and ban appeals are all the same object here, only configured differently.

The path a response takes

1. You build the form on the dashboard and switch it on.
2. You share its link. It looks like https://flavibot.xyz/forms/123456789, and the Copy link button on the forms list gives you exactly that.
3. Someone opens the link and signs in with Discord.
4. FlaviBot checks whether that person may answer, shows the questions, and takes their answers.
5. FlaviBot files the response on your dashboard and, if you named a staff channel, posts it there with review buttons on it.
6. A reviewer accepts, denies or dismisses it. Accepting or denying can add roles, remove roles and DM the respondent.

Where you build one

Everything is on the dashboard, under Requests > Forms. That page lists your forms with their status, their response count, a switch each, and the Copy link action.

There is no slash command for forms, and no module-level switch either: like Custom Commands and Embed Messages, Forms lights up once you create your first one. See modules and commands.

Does answering a form need a Discord account?

Yes. The fill page signs the visitor in with Discord before it shows a single question, even on a form open to everyone. That is what makes the rest possible: one response per person, the server-membership checks below, the right to edit your own answer later, and ban appeals tied to a real ban.

It also means the answers you read carry a real Discord user rather than a name typed into a box, so accepting a response can hand that person a role straight away.

Who can answer

Pick one mode, on the Access step of the builder:

Two rules apply on top of whichever mode you picked:

• Blocked roles shut out anyone holding one of them, even in a mode that would otherwise let them through. The exception is Anyone with a Discord account: that mode never looks the visitor up in your server, so FlaviBot cannot see their roles and the blocked list does nothing.
• Minimum account age turns away Discord accounts younger than the number of days you set. It reads the account's creation date, not the day they joined your server, so an old account that joined yesterday is not treated as an alt.

A form set to Ban appeal ignores the membership and role layer entirely, since the person filling it in is banned. See responses and ban appeals.

One response, or several

One response per user is on by default: a second submission is refused with "You have already responded to this form."

Let respondents edit their answer is the companion switch. With it on, someone who already answered reopens the link and sees their own answers, changes them, and saves. Staff get a fresh post titled "Edited response", and your dashboard keeps one row for that person rather than two.

Answers that were never submitted are kept in the respondent's own browser for seven days, so closing the tab halfway through a long form costs nothing. If you edit the form's questions in the meantime, that half-finished draft is dropped rather than replayed against questions that moved.

How many forms you get

The cap counts forms that are active. A draft does not take a slot, but you do have to be under the cap to create a new form at all, and switching a draft on while you are at the cap is refused with an upgrade prompt.

Switching a live form off is not a way to make room. It stops new answers, but the form stays active as far as the cap is concerned; only deleting a form hands its slot back.

Reading responses and the per-question statistics is free on every plan. Premium adds three things: CSV export of the responses, custom branding on the fill page, and reviewer roles that let people review without giving them Manage Server.

Next: building a form.