Question bank

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

Open Settings from the main navigation, then select Question Bank. It's a workspace-level setting, 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. Select Add question to open the question editor. Twelve types are available:

• Short text: single-line free entry
• Long text: multi-line free entry
• Email
• Phone
• URL
• Dropdown: single selection from a list you define
• Single choice: radio buttons
• Multi-select: checkboxes
• Year: four-digit year picker
• Rating: a 1 to 5 scale
• NPS: a 0 to 10 Net Promoter Score scale
• Scale: a custom scale, built from the same option list you'd enter for Dropdown

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.

Conditional visibility

Any bank question can be set to appear only when another question's answer matches a value, using the optional Conditional visibility field in the question editor. Pick a controlling question and the value that should reveal this one.

Two constraints keep the rules simple to reason about. The controller picker excludes the question itself and any question that is already conditional on another, so a chain of rules can never run more than one level deep. And if you pick a controlling question, you must also pick a value: saving is rejected until you do.

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 to 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.

To build a template, open the Templates tab and select 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.

Contact field mapping

Each bank question can optionally specify a Contact field mapping, set from a picker rather than typed. The picker has two groups: Standard fields (Phone, Pronouns, Company, Job title, Industry, Career stage, City, Province / State, Country, LinkedIn URL) and, when your workspace's contacts are wired up, your Reach custom fields. If contacts isn't wired up, only the standard fields are offered.

When a mapping is set, the Sync to contacts button appears in the Bank tab header. It only appears once at least one bank question has a contact field mapping.

Selecting Sync to contacts writes the mapped question responses from registration records through to the corresponding field on the attendee's contact row. 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.