Custom fields are the checkboxes, text inputs, and dropdowns you add to forms across the platform. The library lets you create each field once and reuse it across any booking site template, internal booking form, or waiver template. Update a field in the library and the change applies everywhere it's used.
Getting started
Navigate to Settings > Custom fields from the sidebar.
How it works
Every custom field lives in the library. You create the field once, configure its type and behavior, and then attach it wherever you need it: booking site templates, internal booking forms, or waiver templates. The field list shows each field's type, label, how many places it's attached, and any active behaviors (required, has alert, interaction required).
Fields come in three types: checkbox, input field, and dropdown. Each type has its own configuration options (policy pop-ups for checkboxes, options with follow-ups for dropdowns). Display rules decide which carts and check-ins a field shows up on, by scoping the field independently to events and to gift card purchases.
Behavior settings (Required, Requires user interaction, Creates alert) live on each surface's attachment of the field — not on the field itself. On the booking site, every template carries its own Required / Requires user interaction / Creates alert toggles per attached field, so the same library field can be required at one venue and optional at another. Waivers, internal booking forms, and payment pages still read the library values as a fallback until they migrate too.
When you update a field's label, type, options, or display rules in the library, the change is reflected everywhere the field is attached. No more hunting through individual templates to make the same edit.
Step-by-step guide
Create a custom field
- Click Create field
- Under Field basics, select the Field type (Checkbox, Input field, or Dropdown) and enter a Label
- For checkboxes, add external links or policy pop-ups that appear alongside the label
- For dropdowns, add the options customers can choose from. Toggle Follow up field to collect free-text detail for an option, or Popup content to show extra information when the option is selected
- Under Display rules, scope the field to events and (optionally) gift cards using the two segmented toggles. See Set display rules below for the full breakdown
- Click Save changes
The library editor no longer has a Behavior section — Required, Requires user interaction, and Creates alert are set per attachment on each booking site template instead (see Attach a field to a booking site template below). Waiver, internal booking, and payment-page surfaces still read the library's fallback values until they migrate.
Set display rules
Display rules decide where a field actually shows up at checkout or check-in. Open the field's editor and scroll to the Display rules section. The hint at the top reads: "Scope this field to events or gift cards."
There are two independent toggles, Events and Gift cards. Each has the same three-option pattern: None, the catch-all option (All events or Any gift card), or a Specific... option that adds a multi-select for narrowing down. The two toggles combine, so a single field can target events only, gift cards only, specific events plus specific gift card types, or every cart at once.
| Toggle | Option | When the field appears |
|---|---|---|
| Events | None | Never on event checkouts or check-ins |
| Events | All events | Every event checkout and check-in |
| Events | Specific events | Only when a selected event is in the cart (multi-select picker appears below) |
| Gift cards | None | Never on gift card purchases |
| Gift cards | Any gift card | Whenever any gift card is in the cart |
| Gift cards | Specific types | Only when a selected gift card type is in the cart (multi-select picker appears below) |
The Gift cards toggle is hidden until you have at least one gift card type configured in Purchases > Gift cards; a hint points you there until then. To make a field appear on every cart, pick All events AND Any gift card. To temporarily disable a field without detaching it, pick None on both. Click Save changes when you're done.
Validation runs on save. Picking Specific events without choosing any event shows the error "Pick at least one event, or switch to 'All events' or 'None'." The same rule applies to gift card types.
Attach a field to a booking site template
- Open Bookings > Booking site settings and select the template
- Go to the Content tab and select the Customer info section
- Click + Add custom field and pick the field from the dropdown
- On the field's card, flip Required (input/dropdown) or Requires user interaction (checkbox) on if the customer must answer to submit
- Flip Creates alert on if you want a warning icon to appear on the calendar and booking drawer when the field is filled
- Drag the card to reorder
- Toggles save in place — no separate save step
The Required, Requires user interaction, and Creates alert toggles live on each template's attachment of the field, so you can require the same library field at one venue and leave it optional at another.
Attach a field to a waiver template
- Open Waivers > Waiver settings and click Configure on the waiver type you want
- Switch to the Sections and fields tab
- Pick the section you want the field to appear in
- Click the + Add custom field dropdown at the bottom of the section and choose any field from your library
- Drag to reorder, set Required if applicable, and click Save changes
Some sections of the customer waiver, like the date picker, time slot picker, or lookup search, are interactive steps the customer can't answer. The editor hides the + Add custom field picker on those sections and shows a context-aware message explaining why fields can't be attached.
Fields are available immediately wherever you've attached them.
Filter and find fields
- Use the Field type dropdown to show only checkboxes, input fields, or dropdowns
- Use the Behavior dropdown to filter by required, has alert, or interaction required
- Toggle Show archived to include fields you've retired
Filter selections stay in the URL, so you can bookmark a filtered view or share it with a colleague.
Edit a shared field
- Click any field card to open it, or use the three-dot menu and select Edit field
- If the field is used on more than one template, you'll see a banner showing how many templates it affects
- Make your changes and click Save changes
Tip: Always review the template count before editing. Changes apply to every template the field is linked to.
Archive or restore a field
- Open the three-dot menu on any field and select Archive field
- Confirm the prompt
- Archived fields stop appearing on linked templates but stay in the library for reference
- Toggle Show archived to see them, then use the three-dot menu and select Restore field to bring one back
Settings and options
| Setting | Description |
|---|---|
| Field type | Checkbox, Input field, or Dropdown |
| Label | The text shown to customers next to the field |
| External links | For checkboxes: clickable URLs shown alongside the label |
| Policy pop-ups | For checkboxes: rich-text policies customers can open in a modal |
| Dropdown options | For dropdowns: each choice available in the menu |
| Follow up field | For a dropdown option: a text input shown when that option is selected |
| Popup content | For a dropdown option: extra information shown after the option is picked |
| Events scope | None, All events, or Specific events. When Specific events is picked, a multi-select appears for choosing which events trigger the field |
| Gift cards scope | None, Any gift card, or Specific types. The control is hidden until at least one gift card type exists. When Specific types is picked, a multi-select appears for choosing which gift card types trigger the field |
| Make field required (per attachment) | Set on each booking site template's attachment of the field. Customer must fill in this field to submit. Hidden for checkbox custom fields (the unchecked state is itself a valid response) and for opt-in fields when attached to a waiver |
| Requires user interaction (per attachment) | Set on each booking site template's attachment of the field. For checkboxes: the customer must actively click the checkbox (either way) before submitting. Shows in the field list as the Interaction required badge |
| Creates alert (per attachment) | Set on each booking site template's attachment of the field. When filled in, triggers a warning icon on the booking calendar, resource calendar, kanban, and inside the booking drawer |
Good to know
- Existing custom fields from previous templates were automatically migrated into the library and remain attached to their original templates. Nothing changed for your customers.
- Behavior is per-venue on the booking site. The Required, Requires user interaction, and Creates alert toggles live on each template's attachment of the field, not on the library field itself. A field can be required at one venue and optional at another. Waiver, internal booking, and payment-pages surfaces still read the library values as a temporary fallback.
- Alert state is captured as a snapshot. When a customer submits a response, the Creates alert flag is captured at that moment. Calendar badges, resource calendar, kanban, and the booking drawer all read from the snapshot, so changing the toggle later doesn't retroactively change what staff sees on historical bookings.
- Display rules are field-level, not per-surface. Whatever event and gift card scopes you set apply wherever the field is attached. You cannot have different scoping for the same field on different templates. If you need different visibility, create a separate field.
- Events and Gift cards are independent. A field can target events only, gift cards only, or both. To show on every cart, pick All events AND Any gift card.
- Backward compatibility: fields previously set to "Always show" now appear as All events in the new UI and continue to behave exactly as before. No data migration was required.
- Display rules are now enforced consistently across every customer-facing surface: the booking site cart, payment-page checkouts via payment links, the search-by-name waiver lookup, the multi-step kiosk check-in flow, and shareable waiver links. Previously some of these surfaces would show every linked field regardless of scope.
- Hidden fields no longer create blank response rows on submission. The Additional information section also hides completely when no fields are visible, instead of rendering as an empty container.
- Gift card scoping has no effect on waiver pages, because waivers don't have cart context.
- The Custom fields permission controls who can create, edit, or archive fields. By default, only admins have it. Grant it to custom roles as needed.
- Unchecked checkboxes are a valid response ("No" or "customer opted out"), not a missing answer. The system records the unchecked state. That's why the Required toggle is hidden for checkbox custom fields: a "no" answer is just as valid as a "yes."
- The same library powers booking site fields, internal booking fields staff fill in when creating a booking from the console, and waiver custom fields.
- Custom field answers from every source flow into the Custom fields report. Filter on the Source column (
waiver,transaction, orinternal_booking) to focus on a single channel.
FAQ
Q: What happens to existing fields I already set up on a template?
A: They were migrated into the library automatically and remain linked to the original template. No manual action needed.
Q: Can I have a field show up on one template but not another?
A: Yes. Each booking site template, internal booking form, and waiver template only uses fields you explicitly attach to it. For booking site templates, manage attachments under Content > Customer info. For waivers, use the Sections and fields tab in Waiver settings.
Q: Can I have the same field with different visibility rules on different surfaces?
A: Not currently. Event and gift card scopes are set on the field itself and apply everywhere it's attached. If you need different visibility, create a separate field with the targeting you want.
Q: I want one question for ticket purchases and a different one for gift card purchases. How?
A: Create two separate fields. Set the first to All events + None for gift cards. Set the second to None for events + Any gift card. Each shows up only in its intended cart.
Q: Where did the old "Always show" / "Show only when a specific item is in cart" dropdown go?
A: It was replaced with two independent scopes (Events and Gift cards). Fields previously set to "Always show" automatically appear as All events in the new UI and continue to behave exactly the same. No action needed.
Q: My field doesn't show up on gift card purchases. Why?
A: Check the Gift cards scope on the field. If it's set to None (the default), the field will not appear on any gift card cart. Switch to Any gift card for every gift card type, or Specific types to target only certain ones.
Q: I don't see the Gift cards scope at all when editing a field. Why?
A: The Gift cards controls are only shown when at least one gift card type exists for your group. Set up a gift card type at Purchases > Gift cards first, then return to the field editor.
Q: Can I attach a custom field to any waiver section?
A: No. Some sections of the customer waiver, like the date picker and time slot picker on traditional waivers and the lookup search and booking selection on lookup waivers, are interactive steps where customers can't answer arbitrary questions. The editor hides the + Add custom field picker on those sections and shows a message explaining why.
Q: Why doesn't my checkbox custom field have a Required toggle on a waiver?
A: A checkbox has two valid states (checked or unchecked) and either is a valid answer, so requiring one over the other doesn't make sense. If you need the customer to actively click the checkbox before submitting (regardless of which way), enable Requires user interaction on the field. The field list will show the Interaction required badge.
Q: Where do I see the answers customers submit?
A: Open any signed waiver from Waivers > Waiver history. The Custom fields section of the detail drawer lists every answer with a one-click Copy as text or Copy as CSV option. For bulk export across waivers, transactions, and internal bookings, run the Custom fields report from Reports.
Q: What happens when I archive a field that's in use?
A: It stops appearing on any attached template immediately. Its historical responses are preserved. Restore the field from the archived view to bring it back.