This article explains what each setting on a form question does, including Locked, Required, and Prefill, and who can change a locked question.
Bevy forms collect information from the people who register for, attend, or host your events. Every question on a form has its own settings, and those settings decide who answers the question, who can change it, and where the answer comes from. Administrators set these options in the Admin Dashboard, and chapter teams see the results when they open the Forms tab on an event.
Question settings
Each question on a form has the following settings:
- Required—The person completing the form must answer this question before they can submit it. Required is on by default. Text snippet and scrollable text snippet questions are never required because they only display text.
- Visible—Controls whether the question appears on the form. A question that isn't visible is never shown to the person completing the form, and it never blocks them from submitting, even if it's also marked as required.
- Locked—Prevents chapter teams from changing the question on an individual event. For details, see Who can edit a locked question.
- Pre-fill—Fills in the answer automatically with the response the same person gave to a matching question on an earlier form.
- Default—The value the question starts with when the form opens.
- Help text—A short line of guidance that appears with the question. Help text is limited to 100 characters.
Pre-fill matches an earlier answer by question type, question text, and answer options. If any of those change, the answer is no longer matched and the question appears blank.
Who can edit a locked question
Locked matters at the event level. When an administrator locks a question on a global form, that question carries the lock into every event form created from it.
Access to a locked question works as follows:
- Administrators who have permission to manage that form type can edit or remove the question, on the global form and on any event form.
- Everyone else, including chapter team members, sees the question as read-only. Bevy blocks every change to the question text, type, options, help text, and other settings.
Order is the one exception. Locking a question doesn't fix its position, so a locked question can still be moved to a different place in the form.
If a chapter organizer needs a locked question changed for their event, ask an administrator to unlock it on the global form, or add a separate question to the event form instead.
Where form questions appear
Form questions appear on the following forms:
- Pre-order—Shown when someone registers for or buys a ticket to an event.
- Post-order—Shown to an attendee after they complete an order.
- Post-event—Sent to attendees after the event to collect feedback.
- Post-event team—Sent to the chapter team after the event to collect host feedback.
Not every form type is turned on for every Bevy instance. If you don’t see one of these forms in your Admin Dashboard, it isn’t enabled for your community.
Question types
Choose a question type based on the answer you want to collect:
| Question type | Use for |
|---|---|
| Single line text | A short written answer, such as a job title. |
| Multi line text | A longer written answer, such as a comment. |
| An email address. Bevy checks the format of the answer. | |
| Number | A numeric answer. |
| URL | A web address. Bevy checks the format of the answer. |
| Check box | A single yes or no answer. When the question is required, the person must select the box. |
| Check boxes | A list where the person can select more than one option. |
| Drop down | A list where the person selects one option. |
| Multi select | A list where the person can select more than one option. |
| Radio buttons | A short list where the person selects one option. |
| Date | A calendar date. |
| Date/time | A calendar date and a time. |
| Hidden | A value stored with the response but not shown to the person completing the form. |
| Text snippet | A block of text that gives the person information. It collects no answer. |
| Scrollable text snippet | A longer block of text in a scrolling box, such as terms the person needs to read. It collects no answer. |
| Session value | A value Bevy stores automatically during the person's session. This type is used internally and collects no answer. |
Check boxes, multi select, drop down, and radio button questions need at least one answer option, and an option can't be left blank.
Text snippet—Add text anywhere between your form questions. This question type also supports the following keyboard shortcuts:
- Bold—Highlight the text, then press Ctrl+B (Windows) or Command+B (Mac).
- Italic—Highlight the text, then press Ctrl+I (Windows) or Command+I (Mac).
- Underline—Highlight the text, then press Ctrl+U (Windows) or Command+U (Mac).
- Strikethrough—Highlight the text, then press Ctrl+~ (Windows) or Command+~ (Mac).
- Code—Highlight the text, then press Ctrl+` (Windows) or Command+` (Mac).
- Link—Copy the link you want to add, highlight the text where you want it, then press Ctrl+V (Windows) or Command+V (Mac).
What happens when you change a question
Keep the following in mind when you change a form question:
- Changes to a global form apply to newly created events and to events republished after the form is updated. The updated form applies to new registrants, but not to anyone who registered before the update.
- You can't change the question type after someone answers the question.
- When you remove a question that already has responses, Bevy archives the question instead of deleting it, so the responses you already collected are kept. A question with no responses is deleted.
- Question text is limited to 250 characters and can’t end in "_id".