Question bank
The question bank is where you define reusable registration questions for your workspace. Questions live once at the org level; templates and ticket types reference them by ID so answers from every event land in the same column for cross-event filtering.
Updated May 26, 2026
The question bank is a workspace-level library of registration questions. Because questions are defined once and referenced by ID, every answer collected across all your events flows into the same database column — making cross-event filtering reliable.
From the bank you build sections (visual groups) and templates (reusable question bundles). Ticket types can then draw from a template or from individual questions.
Where to find it
Go to Settings → Question Bank (path: /events/settings/question-bank). This is an org-level setting — it is not scoped to any individual event.
The page has three tabs: Bank, Sections, and Templates. Work in that order when building from scratch.
Bank questions
Each row in the bank is a question definition. Click Add question to open the question editor. The nine available types are:
- Short text — single-line free entry
- Long text — multi-line free entry
- Phone
- URL
- Dropdown — single selection from a list you define
- Single choice — radio buttons
- Multi-select — checkboxes
- Year — four-digit year picker
For Dropdown, Single choice, and Multi-select, you enter the options one per line. You can also enable Allow "Other" to let attendees type a free-text answer when none of your options fit.
Each question also has a Required toggle and an optional Section assignment for grouping in the registration form.
Sections
A section is a named group of bank questions — it adds a heading and visual separation in the registration form. Each section has a name, an optional description, and an ordered list of question IDs.
Sections are optional. Small question banks often skip them. They become useful when your bank grows beyond 10–15 questions and you want to break a long form into labeled groups — for example, "Personal info", "Dietary requirements", and "Accessibility needs".
Deleting a section leaves its bank questions intact. The questions lose their grouping but remain in the bank and in any templates that reference them individually.
Templates
A template is an ordered collection of bank questions and/or sections. Ticket types can point at a template rather than listing individual questions — which means every event that uses the template stays in sync automatically.
Templates propagate live. Editing a template updates the registration form for every ticket type that uses it — including events that are already open for registration. If you need a ticket type to diverge from the template, switch it to snapshot mode — snapshot mode freezes the question list at the moment you switch and ignores future template changes.
To build a template, open the Templates tab and click Add template. Give it a name, then add entries in order — you can mix individual bank questions and entire sections. Reorder with the arrow buttons.
Deleting a template does not automatically unbind ticket types that point at it. The delete confirmation warns you of this. Switch any affected ticket types to a different template or to individual questions before deleting.
PII flag and re-encryption
Each bank question has a Contains PII toggle. When enabled, attendee answers are encrypted at rest. Only org admins and cockpit guests with the PII scope see the raw values; everyone else sees aggregate counts only.
When you toggle PII on a question that already has answers, a browser confirmation dialog appears. Confirming migrates historical answers between the plaintext and encrypted columns so the new policy applies to past registrations as well.
If you dismiss the browser confirmation, the PII flag is saved but historical answers are not migrated. The question metadata says PII, but old answers stay in the previous column until you trigger migration again by re-saving the question with the same PII state change.
Contact field mapping
Each bank question can optionally specify a Contact field mapping — a key like dietary_restrictions or custom:foo. When a key is set, the Sync to contacts button appears in the Bank tab header.
Clicking Sync to contacts writes the mapped question responses from registration records through to the corresponding field on the attendee's contact row. This button only appears when at least one bank question has a contact field key set.
The sync result shows counts of updated and skipped rows. Skipped rows are attendees whose contact record already has the correct value or where no contact record exists.