Completev1.5.0 · updated 2026-11-04

Attendee fields

Decide what registration asks for, what each attendee can see or change in the app afterwards, and what an attendee record holds — the standard fields, the ones you add, and the rules each one answers to.

The gist

One list that is both the registration form and the shape of an attendee record — change it here and both move.
Every row has four switches in two pairs: Registration form — Ask, then Required; Attendee app — Show, then Can edit (what they can do in Edit Profile). The second of each pair only works while the first is on. Your team always sees and edits every field in the dashboard.
Do this before the registration campaign goes out. Required only applies to people who register after you set it.
A field's Field name is its storage key: the CSV column, the import mapping. Renaming the label never changes it.
Email is fixed: always asked, Required and shown read-only in the app, because it is how a person signs in.

What it is

A single ordered list of fields. Each one is a question on the registration form, a line in the attendee's Edit Profile in the app, a row on the attendee record, and a column in the export — the same field, seen from four places. Four switches per field decide the attendee's two surfaces: whether registration asks it (and must it be answered), and whether the attendee can see it in the app (and change it). Standard fields (name, email, company, job title, ticket type…) are built in and map to real columns — the ones in use are rows, the rest wait as one-click chips under Add to form. Anything you add is a custom field and is stored alongside them.

When to use it

It is the shape of everything downstream. What you do not ask for here does not exist anywhere — not on the badge, not in the export, not in the attendee directory, not as something an import has anywhere to put. And "is it on the form?" and "can they change it later?" really do have different answers: a dietary need asked once and never shown back, a LinkedIn URL nobody is asked for at sign-up, a lucky draw number your team assigns and the attendee may only look at, a VIP flag that stays internal. It is a day-one job, because the one thing this screen cannot do is go back and ask 340 people who already registered.

Catering needs numbers
Add a Dropdown with your four meal options. A closed list means you can count the answers; a text box means reading 900 of them.
The badge needs a job title
Job title is a standard field and is on the form by default — check its Ask switch is on, and turn on Required if the badge cannot do without it. It already maps to a column; you are switching it on, not creating it.
A mobile number for day-of SMS
Click + Mobile under Standard fields in the Add to form panel. It joins the list asked and editable — no custom field, no new column to map.
A consent line the lawyers asked for
A Checkbox (yes/no) with Ask and Required on. Nobody registers without ticking it, and the answer is on the record if it is ever asked for.
A follow-up question that only sometimes applies
Ask "Any allergies?" only of people who chose something other than "No requirements" — a condition on the Advanced tab, rather than a question everyone has to skip.
A lucky draw number or a table the attendee should see
Ask off, Show on, Can edit off. You import or type the number; they see it locked in Edit Profile.
A dietary need asked once and never shown back
Ask on, Show off. Registration collects it, your team sees it, and the attendee does not see it again.
Something attendees should never see
All four switches off. Notes, tags, VIP flags: your team fills them in from the attendee record or an import. The row is badged Team only.
A spreadsheet with a column you have nowhere to put
Add the field first, then import. The upload can only map onto fields that already exist.

Before you start

Ideally, registration not yet open — this is the one screen where being early actually matters. Read the guide

Try it — this is a sandbox, nothing here is real

Add a dietary requirements field to an event where 340 people have already registered, using the four switches — and meet the things that surprise people: Required that cannot reach back, an answer the attendee can never see again, and a follow-up that leaks to everyone.

The field list. Every row has four switches: Ask and Required under Registration form, Show and Can edit under Attendee app. The standard fields not in use wait as chips in the Add to form panel. The settings icon opens a field; the bin beside it removes it (Email has none). Your team always sees every field in the dashboard.

Asked at registration

Attendee can edit

Attendee can view only

Internal (team only)

#	Field	Registration form		Attendee app
#	Field	Ask	Required	Show	Can edit
1	First name * Text · Standard					Settings Bin
2	Last name Text · Standard					Settings Bin
3	Email * Email · Standard · switches locked, no bin					Settings
4	WhatsApp number Phone · Standard					Settings Bin
5	LinkedIn profile URL · Standard					Settings Bin
6	Company Text · Standard					Settings Bin
7	Job title Text · Standard					Settings Bin

Add to form

Standard fields

+ Mobile+ Category+ Ticket type+ Ticket ID+ Bio+ Profile photo

Built-in fields every event understands. Click one to put it on the form. Custom question

Question

Dietary requirements

Type

Dropdown

+ AddMore options

New fields are asked at registration and editable in the app. Change that with the switches on the field's row.

340 people have already registered. Keep that in mind — it changes what "Required" can mean.

Who sees itGeneralOptionsValidationAdvanced

REGISTRATION FORM

Ask on the registration form
Registrants fill it in when they sign up.

Required
They can't register without answering.

ATTENDEE APP

Show in their profile
They see their answer in Edit Profile.

Let them change it
Off = they can look but not edit.

Optional at registration. Attendees can see and change it in the app.

Your team always sees and edits this field in the dashboard.

Email is always asked, Required, and read-only in the app

Its four switches are locked — Ask, Required and Show on, Can edit off — and its Advanced tab has no Delete field and no Remove from form. It is how a person is identified and how they sign in. Registration matches on it, an import updates the row that already has it, and the magic link that gets someone into the app is sent to it. An attendee changing it in the app would change who can sign in, so they see it locked.

Every other standard field
Remove from form, on the Advanced tab — every switch goes off, it goes back under Add to form, and its data is kept Remove from form

Fields you added yourself
Delete field, on the Advanced tab Delete

#	Field	Registration form		Attendee app
#	Field	Ask	Required	Show	Can edit
4	Company Text · Standard · Required locked					Settings Bin

The second switch of a pair needs the first

A question the registration form doesn't ask can't be required, so Required stays locked until Ask is on. Can edit works the same way with Show. Turning the first off clears the second; turning Show on starts view-only, so turn Can edit on again if they should change it.

Add to form

Standard fields

+ Mobile+ Company+ Bio

Fields (6). Before you saved, the row stayed put with a Not used badge.

The switches are about attendees, not about you

The row's bin (Remove from form) would have done the same in one click — straight back to the chips, with Undo on the toast.

They only decide what attendees are asked and shown. Your team still sees Company on every attendee record in the dashboard, and the answers 340 people already gave are kept and still exported.

What does change: it is off the registration form, off Edit Profile, off the business card, and out of the import sample CSV. Click + Company to bring it back — asked and editable — with its data intact.

Answered

340

Blank, and staying blank

Required is a rule about the form, not about the people

It stops the next registration going through empty. It cannot reach back into the 340 who registered before it existed, and nothing will ever prompt them.

Ask them, once
An announcement pointing at Edit Profile in the app — they can answer there, because Show and Can edit are on

Or fill them in yourself
Registration → the person → edit, if you have the answers elsewhere

Next time, before the campaign
This screen is a day-one job, not a week-three one

Edit Profile, in the app

[email protected]

You can't change these here. Ask the organizer if one is wrong.

First name

Mei

Company

Harbour & Co

"I said I was vegan — where did that go?"

Ask on with Show off means registration collects it and the attendee never sees it again. The answer is on the record and your team sees it; the attendee cannot check it or correct it, and some will register a second time to be sure.

That is right for something sensitive you never want shown back. For a meal choice they may want to change, turn Show and Can edit on — or just Show, if they should see it but not change it.

The registration form

Dietary requirements

Vegetarian

Edit Profile, in the app
Show and Can edit are on, so they can change their answer later Can edit

The attendee record
Registration → the person. Your team sees and edits it, whatever the switches say Stored

The CSV export
A column headed dietary_requirements — the field name, not the label Exports

The bulk import
A column you can now map onto, next time you upload a list Imports

Display label

Dietary

Changed, on the General tab. Safe to change, any time.

Field name

dietary_requirements

Unchanged — and that is deliberate.

This is the behaviour you want

Every answer already given is filed under dietary_requirements. If fixing a label moved the key, the 41 answers you already had would be orphaned by a typo correction.

The cost is that the export column keeps the old name. If a spreadsheet downstream reads the header, it still reads the header it always did.

#	Field	Registration form		Attendee app
#	Field	Ask	Required	Show	Can edit
6	Dietary requirements Dropdown · Custom					Settings Bin
7	Allergy details Only when “Dietary requirements” is “Vegan” “Dietary requirements” isn't asked at registration, so every registrant sees this.					Settings Bin

A condition on a question the form never asks counts as met

The registration form cannot know the answer to a question it did not ask, so it shows the follow-up to everyone rather than to nobody. Your carnivores get asked about vegan allergies.

Either turn Ask back on for Dietary requirements, or turn Ask off on Allergy details so it lives only in the app, next to the question it depends on.

Click a control above. One of them is the mistake people actually make — take it on purpose.

Step by step

1
Start with what is already thereRegistration → Attendee Fields
A new event lists seven standard fields — First name, Last name, Email, WhatsApp number, LinkedIn profile, Company, Job title — and the other six wait as chips under Standard fields in the Add to form panel. The four counters at the top — Asked at registration, Attendee can edit, Attendee can view only, Internal (team only) — say where you stand. Switching on a standard field is cheaper than adding your own — it maps to a real column, so it sorts, filters and imports without any further thought.
Tip. Look at the chips first — + Mobile, + Category, + Ticket type. Hosts routinely add a custom field for something that was already sitting there unused.
2
Add what is missingthe Add to form panel, on the right
Click a Standard fields chip to put that field at the end of the list, asked and editable. For anything else, use Custom question: type the Question, pick its Type, then Add. Enter adds it and leaves the box ready for the next one. A Dropdown, Multiple choice or Checkboxes field opens straight into its editor so you can write its choices; More options opens the full editor for anything else. New fields start asked at registration and editable in the app.
Careful. The Field name is generated from the question once, at creation, and is not recomputed when you edit the label. Check it on the General tab now; every export column and import mapping is this string.
3
For a dropdown or checkboxes, write the choices
Prefer a closed list to a text box whenever the answers are countable. A dropdown gives you a number at the end; free text gives you nine hundred spellings of "vegetarian".
Tip. Only a closed-list or yes/no field can drive a conditional question later — so choosing Dropdown over Text now keeps a door open.
4
Set who sees it
Each row has four switches under two headers. Registration form: Ask puts it on the form, Required makes it compulsory. Attendee app: Show puts it in their Edit Profile, Can edit lets them change it. Required stays greyed out until Ask is on, and Can edit until Show is on; turning the first of a pair off clears the second. Flip them right on the row, or open the field — Who sees it has the same four switches spelled out, and one sentence saying what they add up to.
Tip. Use View as above the list — Registration form or Attendee app — to see only the fields that audience gets. Switch back to All fields to reorder.
5
Take off what you don't need
Click the bin beside a row's settings icon. A custom field (*Delete field*) leaves the list; a standard field (*Remove from form*) has every switch turned off and goes straight back to the Standard fields chips under Add to form. A toast confirms it — *Removed “Mobile” — it's back under Add to form* — with an Undo that puts back just that field, where it was and as it was. Nothing is live until Save changes, and answers already collected are kept. Email has no bin.
Tip. The same two actions are also at the bottom of the field sheet's Advanced tab.
6
Add any validation
Validation is its own tab and changes shape per type: lengths and a regex for text, minimum and maximum for a number, minimum and maximum selections for checkboxes. Whether a field must be answered is not here — it is the Required switch.
Tip. Fill in Error message whenever you set a pattern. The default message says the value "is not in the expected format", which tells nobody what to type.
7
Put them in the order you want to be asked
The arrows on each row move a field up and down (in All fields view), and that order is the registration form, Edit Profile and the admin form all at once. Use Section on the Advanced tab to put a heading above a group.
8
Save, then look at the real form
Nothing is live until Save changes — the amber bar at the bottom says so: *Unsaved changes. Attendees still see the saved fields.* Discard throws your edits away. Then open your own registration link and fill it in once — it is the only way to see the thing an attendee sees, including the widths and the section headings.

Every option, and what it does

The switches the steps walked past. Defaults are what you get by leaving one alone.

The field listRegistration → Attendee Fields

A numbered list, Fields (N) — N counts only the fields on the list, not the standard fields waiting under Add to form. Each row has the field, then four switches under two headers: Registration form over Ask and Required, Attendee app over Show and Can edit.

Ask

Puts the field on the public registration form.

Default: On for First name, Last name, Email, Company and Job title. On for every new custom field, and for a standard field added from a chip (except Ticket ID and Ticket type, which are never asked).

Knock-on: Registration only. Turning it off also turns Required off and greys it out.

Required

The registration form will not submit while this field is empty. Greyed out until Ask is on.

Default: On for First name and Email; off for everything else.

Knock-on: Registration, and Edit Profile for this field. Applies to registrations made from now on — it cannot reach back into people who registered before you set it. Marks the field with a red asterisk on its row.

Show

Shows the field to the attendee in Edit Profile in the app. Turning it on starts as view-only — a locked row they cannot change.

Default: On for the seven fields listed by default, and for new custom fields. Off for the standard fields waiting under Add to form.

Knock-on: Edit Profile, and anything shown about them to other people — a business card never uses a field the attendee cannot see themselves. Turning it off also turns Can edit off and greys it out. Your team's view in the dashboard is never affected.

Can edit

Lets the attendee change their answer in Edit Profile. Off means they can look but not edit. Greyed out until Show is on.

Default: On for First name, Last name, WhatsApp number, LinkedIn profile, Company, Job title and new custom fields; off (and locked) for Email, Ticket ID and Ticket type.

Remove (the bin)

Beside each row's settings icon. Titled Delete field on a custom field and Remove from form on a standard one. Email has none.

Knock-on: A custom field leaves the list. A standard field is switched off everywhere and goes back to the Standard fields chips at once — unlike turning its four switches off by hand, which leaves it listed until the next save or reload. The toast says *Save changes to apply it. Answers already collected are kept.* and offers Undo, which restores just that field, in its old place with its old switches.

View as

All fields, Registration form or Attendee app. The last two show only the fields that audience gets, and say how many are hidden from them.

Default: All fields

Knock-on: Display only. The reorder arrows appear in All fields only.

Badges on a row

A field with all four switches off is badged Not used (a standard field) or Team only (a custom field). A conditional field shows *Only when “…” is “…”*. A field with a report column name shows *Report: “…”* under its name.

Knock-on: A standard field left with every switch off leaves the list on the next save or reload and becomes a chip under Add to form. A custom field stays on the list. Custom fields stay in the import sample CSV even when team-only, because an import is how internal values get there.

Counters

Asked at registration, Attendee can edit, Attendee can view only, Internal (team only). Internal counts custom fields with all four switches off.

Add to formthe panel to the right of the list

Two ways to add: a standard field in one click, or a question of your own.

Standard fields

One chip per standard field not on the form — + Mobile, + Bio, + Profile photo and so on. *Built-in fields every event understands. Click one to put it on the form.* When there are none left: *Every standard field is on the form.*

Default: Mobile, Category, Ticket type, Ticket ID, Bio and Profile photo, on a new event.

Knock-on: Clicking a chip appends the field to the end of the list, asked and editable. Ticket ID and Ticket type arrive shown and view-only instead, because they can never be asked or edited.

Question

Under Custom question: the display label of the new field. Its field name is generated from it.

Type

Any of the thirteen field types.

Default: Text

Add / More options

Add (or Enter) appends the field and clears the box for the next question. A choice field opens its editor instead, so you can add its options. More options opens the full editor on a blank field.

Default: *New fields are asked at registration and editable in the app. Change that with the switches on the field's row.*

Knock-on: Added fields are not live until Save changes.

The switches

A card under the panel with one line per switch: Ask — on the registration form; Required — they can't register without answering; Show — the attendee sees it in their profile in the app; Can edit — they can change it there, off = view only. It ends: *All four off keeps a field for your team only — a VIP flag, or a lucky draw number you haven't shown yet.*

Who sees itthe field editor → Who sees it (the first tab)

The row's four switches, spelled out, in two groups. Both edit the same values, so they can never disagree. Under them, a highlighted sentence says what the combination means — *Optional at registration. Attendees can see and change it in the app.* Your team always sees and edits this field in the dashboard.

Ask on the registration form: Under REGISTRATION FORM. *Registrants fill it in when they sign up.* The row's Ask.
Required: Indented under it. *They can't register without answering.* Locked off until Ask is on.
Show in their profile: Under ATTENDEE APP. *They see their answer in Edit Profile.* The row's Show.
Let them change it: Indented under it. *Off = they can look but not edit.* The row's Can edit; locked off until Show is on.
The summary: One sentence for registration — *Not asked at registration.*, *Optional at registration.* or *Required at registration.* — and one for the app: *Attendees can see and change it in the app.*, *Attendees can see it in the app but not change it.*, *Attendees don't see it again after registering.* (asked but not shown), or *Attendees never see it — only your team.* (all off).
Knock-on: Email and the ticket fields add a line saying why their switches are locked — see the reference on fixed fields.

Generalthe field editor → General

What the field is and how it looks: its question, a short name for reports, its storage key, and its width.

Field type

What kind of answer this collects — text, a date, a dropdown, an upload, and nine others. See the full reference below for all thirteen.

Default: Text

Knock-on: Which tabs the editor shows, what can be validated, and whether the field can control a conditional question. Fixed on standard fields.

Display label

*The question attendees see on the registration form and in the app.* Safe to change at any time.

Knock-on: Nothing but the wording. It is deliberately not the storage key.

Report column name

*A short header for the attendee list. Blank uses the display label.* Up to 40 characters; the placeholder shows the display label. Standard and custom fields both have it.

Default: Blank — the display label is used

Knock-on: The column headers and the column picker in Registration → Attendees only. The registration form, the app and the attendee detail panel keep the full display label, and the storage key does not move. When set, the field's row shows *Report: “…”*.

Field name

The storage key. Generated from your label as lower_snake_case, and editable only while you are creating the field.

Knock-on: The CSV export header, the import column mapping, and where the value is filed. Changing it on a field that already has answers orphans every one of them.

Description

Guidance shown under the input. Unlike a placeholder, it stays visible while someone types.

Placeholder

Grey example text inside an empty input. Disappears as soon as they type.

Width

Full width, or Half width so two fields sit side by side.

Default: Full width

Knock-on: Larger screens only. Everything is full width on a phone.

Optionsthe field editor → Options

Only appears for Dropdown, Multiple choice and Checkboxes.

The choice list: One line per choice, in the order they are offered. Add option appends; the bin removes.
Knock-on: Deleting a choice does not change answers already given — an attendee who picked it keeps it, and it simply stops being offered.

Validationthe field editor → Validation

The tab changes with the field type. Date, Checkbox (yes/no), Image and File have nothing here — use the Required switch.

Min length / Max length: Character counts, for the text-like types and the choice types.
Knock-on: Checked as the attendee types and again on the server, so it cannot be bypassed.
Pattern (regex): A regular expression the value must match — ^[A-Z0-9]+$ for a reference code, say.
Knock-on: A pattern that is not valid regex is ignored rather than blocking the form, so a typo here fails open, silently.
Error message: What to show when the value fails. Replaces the generic wording entirely.
Default: "<label>: is not in the expected format"
Minimum / Maximum: Numeric bounds. Number fields only.
Min selections / Max selections: How many boxes must be, and may be, ticked. Checkboxes only.

Advancedthe field editor → Advanced

The same four capabilities appear on the exhibitor, speaker and lead builders — learn them once.

Help text: Guidance under the input that survives typing.
Default value: What a blank form starts with.
Knock-on: Only pre-fills the input. It is not a value on anyone's record until they submit.
Section: A heading this field sits under. Type the same section name on several fields and they group together.
Knock-on: A section exists exactly as long as a field claims it — so there is no separate list to tidy up and no way to leave an empty heading behind.
Show only when…: Ask this field only when another field holds a particular value. One condition, one field above this one, compared for equality.
Knock-on: A field not being shown is exempt from its own Required rule, so a conditional question can safely be required. Only Dropdown, Multiple choice, Checkboxes and Checkbox (yes/no) fields can be the controller. If the controller is not asked at registration, the registration form shows this field to everyone — the row warns you.
Delete field: Removes a custom field — the same as the row's bin. Only shown on fields you added, once they have been added.
Knock-on: The field stops being asked. Answers already stored stay on the attendee records but are no longer shown anywhere.
Remove from form: On a standard field other than Email, in place of Delete field — the same as the row's bin. *Standard fields can't be deleted. This turns every switch off and puts it back under Add to form. Values already collected are kept.*
Knock-on: The field leaves the list straight away and reappears as a chip under Standard fields. Nothing is live until Save changes.

When it goes wrong

Every one of these has happened to someone. Symptom first, because that is what you will have.

Added a required field after the campaign went outwarning

What you see: A field is set to Required, and hundreds of attendees have no answer for it. The export column is mostly empty.

Why: Required is a rule about the form, not about the people. It stops the next registration going through empty; it has no way to reach back into a registration that already happened, and nothing prompts anyone to return.

Fix: Fill the gaps yourself from Attendees, or turn on the field's Show and Can edit switches and post an announcement asking people to answer it in Edit Profile. Next event, define the fields before opening registration.

Attendees ask where their registration answer wentgotcha

What you see: An attendee says they answered a question at registration but cannot find it in the app, or registers again to be sure it went through.

Why: The field has Ask on and Show off — the summary reads *Attendees don't see it again after registering.* The answer is saved and your team sees it, but it is never shown back to the attendee, so they cannot check or correct it.

Fix: Keep it that way for something sensitive you never want shown back. Otherwise turn Show on — they see it, locked — and Can edit too if they may change it.

A follow-up question shows on every registrationwarning

What you see: A field set to show only when another field has a certain answer appears for every registrant. Its row warns: *“…” isn't asked at registration, so every registrant sees this.*

Why: The field is asked at registration, but the field its condition depends on has Ask off. The form cannot know an answer to a question it did not ask, so it treats the condition as met and shows the follow-up to everyone.

Fix: Turn Ask on for the controlling field too, or turn Ask off on the follow-up so it only appears in the app alongside the question it depends on. In Edit Profile it behaves: if the attendee cannot edit the controller, the follow-up is judged against the answer already on their record.

Switched a field off and it is still in the dashboardgotcha

What you see: You turned all four switches off (or clicked the row's bin), but the field is still on the attendee record, in the export, and in the admin add/edit form.

Why: The switches are only about attendees. Your team always sees and edits every field in the dashboard, and data already collected is kept. All four off stops the field being asked or shown to attendees; a standard field also moves back under Add to form after the next save and drops out of the import sample CSV.

Fix: That is the intended way to retire a standard field. If it is a custom field you truly want gone, delete it from the Advanced tab — the stored answers stay on the records but are no longer shown anywhere.

Renamed a field and the export column did not changegotcha

What you see: You corrected "Dietary requirements" to "Dietary", but the CSV still has a dietary_requirements column.

Why: The Display label and the Field name are separate on purpose. The field name is the storage key, and it is generated once at creation and never recomputed — because if fixing a typo moved the key, every answer already given would be orphaned by a spelling correction.

Fix: Nothing to fix — the data is fine and the form reads correctly. If a downstream spreadsheet depends on the header, rename the column there, or create a fresh field with the name you want and copy the values across.

Cannot change Email's switches or delete itgotcha

What you see: Email's four switches are greyed out — Ask, Required and Show on, Can edit off — its row has no bin, and its Advanced tab has neither Delete field nor Remove from form.

Why: Email is how a person is identified and how they sign in. Registration matches on it, an import updates the row that already carries it, and the magic link that gets an attendee into the app is sent to it. Letting an attendee edit it in the app would change who can sign in, so they see it read-only.

Fix: Nothing to do. Every other standard field can be taken off the form with its row's bin (Remove from form), and every field you added yourself can be deleted. If an attendee's email is wrong, your team corrects it on their record.

A standard field you do not want has no Delete buttongotcha

What you see: Delete field is missing on Company, Bio, Ticket ID and the rest — the row's bin and the Advanced tab say Remove from form instead.

Why: Standard fields map to real columns on the attendee record, and those columns are read by the import, the export, the badge and the directory. Deleting one would be deleting part of the record, not part of a form.

Fix: Click the row's bin (Remove from form) — or the same button on the field's Advanced tab. It turns every switch off and puts the field straight back under Add to form as a chip; it leaves every attendee surface and keeps any data already collected. Undo on the toast, or clicking the chip later, brings it back.

A conditional question started showing for everybodywarning

What you see: A follow-up field that was meant to appear only sometimes is now on every registration form.

Why: Its controlling field was deleted or renamed. A condition pointing at a field that no longer exists resolves to visible — deliberately, because the alternative is a deleted field silently removing questions from a live form, and that is the failure nobody notices until the responses come back short.

Fix: Open the field's Advanced tab and point Show only when… at a field that still exists, or clear the condition. If the controller exists but has Ask off, see the pitfall about follow-ups showing on every registration.

Required or Can edit will not switch ongotcha

What you see: The Required or Can edit switch on a row is greyed out and does nothing when clicked — or it was on and turned itself off.

Why: Each is the second switch of a pair. Required only means something while Ask is on, and Can edit only while Show is on, so each is locked until its partner is on — and turning the partner off clears it. Turning Show on starts view-only, so Can edit has to be turned on again. On Email, Ticket ID and Ticket type some switches are locked for good.

Fix: Turn Ask (or Show) on first, then the second switch. If it is one of the fixed fields, the Who sees it tab says why it is locked.

A standard field disappeared from the listgotcha

What you see: Mobile (or Bio, Category…) is no longer in the list and Fields (N) went down by one — after a click on its bin, or after you turned off all four switches and saved.

Why: A standard field that is off everywhere is not on the form, so it is not listed: it waits as a chip under Standard fields in Add to form. The row's bin (Remove from form) sends it there at once. Turning the four switches off by hand leaves the row in place, badged Not used, until the next save or reload, so it does not vanish from under the pointer. A custom field with all four off stays on the list, badged Team only.

Fix: Straight after a bin click, Undo on the toast puts it back where it was, as it was. Otherwise click its chip — + Mobile — to put it back on the form, asked and editable, then adjust the switches. Its stored values were never touched.

The answers are unusable at the endgotcha

What you see: You need a headcount and the column has "veg", "Vegetarian", "veggie", "no meat pls" and forty blanks.

Why: The question was asked as a text field, so every attendee invented their own answer.

Fix: Use Dropdown or Checkboxes for anything you will need to count. It is worth changing even mid-campaign: the answers you have already are kept, and the ones from here are countable.

What people ask

Kept in the words people use, because that is what you are about to type.

Can I add a field after registration has already opened?

Yes, at any time. The catch is only that people who already registered will have no answer for it — and if you set it to Required, they still will not.

More detail

Nothing breaks and no data is lost. The new field appears on the registration form as soon as you save, and in the attendee's Edit Profile while Show and Can edit are on — the default for a new field — so attendees can fill it in themselves if you ask them to.

IssueWhy can't I delete this field?

It is a standard field. Its row's bin is Remove from form instead (also on the Advanced tab) — every switch goes off and it goes back under Add to form, with its data kept. Only fields you added yourself can be deleted; Email cannot be removed at all.

Where do the answers actually end up?

On the attendee record, visible under Attendees and included in the CSV export. Standard fields go to their own column; fields you added are stored on the record alongside them.

More detail

The export header is the Field name, not the Display label. That is also the column name the bulk import matches on, so a spreadsheet whose headers match your field names maps itself.

Read the upload attendees guide

What happened to Visible and Admin only?

They were replaced by the four switches on every field. The old Visible on is now Ask (plus Required if it was required), Show and Can edit; Visible off or Admin only is now all four off — team only.

More detail

Existing events were converted automatically and nothing changed for attendees: a previously visible field became asked (required if it was) and shown and editable; a hidden or admin-only field had every switch turned off. The split now lets you say what one switch could not — ask once and lock it, or let the attendee see a value your team assigned.

Can attendees see a field without being able to change it?

Yes — turn Show on and leave Can edit off. In Edit Profile it appears as a locked row above the form, with *Not set yet* when empty and a note: *You can't change these here. Ask the organizer if one is wrong.*

More detail

For a lucky draw number, a table or a seat, turn Ask off as well — your team fills it in. For something they gave you once and should not change, keep Ask on. If nothing in Edit Profile is editable, there is no Save button at all.

IssueWhy can't I ask for Ticket ID or Ticket type at registration, or let attendees edit them?

Your team or the system sets them. Ask, Required and Can edit are off and locked; only Show can be turned on, so attendees can see them.

More detail

QR sign-in matches on the ticket ID, so an attendee who could edit theirs could claim someone else's; a self-typed ticket type would let anyone call themselves VIP. You can still let attendees see them: click + Ticket ID or + Ticket type under Add to form, and it joins the list shown and view-only.

Can I ask a question only when someone answers another one a certain way?

Yes — Advanced → Show only when…. Pick the controlling field (one above it) and the value it must hold.

More detail

Only closed-list fields can be the controller: Dropdown, Multiple choice, Checkboxes and Checkbox (yes/no). A free-text controller was left out on purpose, because a rule that compares against typed text never fires the day someone adds a trailing space. A field not being shown is also exempt from its own Required rule, so conditional questions can safely be required. Ask the controller at registration too, or the follow-up shows to everyone there.

Is it safe to rename a field?

Renaming the Display label is completely safe and changes nothing but the wording. The Field name is a different matter — it is the storage key, and it is locked after creation for exactly that reason.

My question is too long for the attendee list column

Give it a Report column name on the field's General tab — up to 40 characters, e.g. *Dietary* for *Do you have any dietary requirements?*. The attendee list's column headers and column picker use it; the registration form and the app keep the full question.

More detail

Blank uses the display label. It works on standard and custom fields alike, and the row shows *Report: “…”* when it is set. It is not the Field name, so setting it never moves where answers are stored.

IssueI made a field required but people are still getting through without it

Check two things: whether they registered before you set it (Required is not retroactive), and whether the field is hidden by a condition — a field that is not being shown is exempt from its own Required rule.

IssueWhy can't I turn on Required?

Ask is off. A question that is not on the registration form cannot be required, so Required stays greyed out until Ask is on. Can edit works the same way with Show.

Is a Required field also required when attendees edit their profile?

Only if its Required switch is on. A field the attendee first meets in the app is never forced — otherwise saving a new job title would demand every empty field.

IssueAn attendee says the answer they gave at registration isn't in the app

The field has Ask on but Show off, so it is never shown back to them. Their answer is saved; they just cannot see it. Turn Show on.

IssueI turned a field off but I still see it on every attendee

That is expected. The switches only apply to attendees; your team always sees and edits every field in the dashboard, and existing answers are kept and exported.

IssueWhere is the Mobile field? I can't find it in the list

Standard fields that are not in use are not rows — they are chips under Standard fields in the Add to form panel. A click on a row's bin sends a standard field there; click + Mobile to put it back on the form, or Undo on the toast if you just removed it.

Which switches do I need for…?

Asked, and they can change it later: Ask, Show and Can edit on (Required if it must be answered). Asked once, then locked: Ask and Show on, Can edit off. Asked once, never shown back (a dietary need): Ask on, Show off. Filled in only in the app (a LinkedIn URL): Ask off, Show and Can edit on. A lucky draw number or table: Ask off, Show on, Can edit off. Team only: all four off.

More detail

The Who sees it tab's summary sentence says what any combination adds up to, so you never have to work it out. There are no presets to pick from; the switches are the whole setting.

How many fields can I add?

There is no fixed limit. The practical one is the form: every extra question measurably costs you registrations, so the useful discipline is asking what you will actually do with each answer.

More detail

Fields are stored as one configuration blob per event rather than as database columns, which is why adding one needs no migration and why there is no cap to quote.

Can I reuse these fields on my next event?

Field configuration belongs to one event, so it does not follow you automatically. Set it up again on the new event — the thirteen standard fields are already there (seven listed, six as chips under Add to form), so it is usually only your custom ones to re-add.

Can attendees change their own answers later?

Yes, for any field with Show and Can edit on — they change it in Edit Profile in the app. A field with Show on and Can edit off is shown locked; one with Show off is not shown at all.

Read the attendee profile guide

How do I set the size of profile photos?

Open the image field (Profile photo, or any Image upload question) and go to the Photo tab. Pick Square, Portrait 3:4, Passport or Landscape 4:3, or type a width and height in pixels. Attendees move and zoom their photo into that shape, and it is saved at exactly that size.

More detail

Any size from 100 to 2000 pixels a side. The cropping happens on the attendee's device, before anything is sent, so every photo arrives the same shape, and a large photo straight off a phone becomes a small one. A photo already on file is not changed until the attendee replaces it.

Can attendees take their photo with the camera?

Yes. In the image field's Photo tab, turn on Let them use the camera. The form then offers Take photo beside Choose photo: a live preview in the field's shape, a shutter, and the same move-and-zoom step afterwards. Turn on Show a face frame to draw an oval to put a face in, over both the camera and the cropper.

More detail

The face frame is on for the standard Profile photo and off for an image question you add, such as a company logo. The camera needs the browser's permission; an attendee who refuses, or whose device has none, can still choose a photo. Take photo only appears where the browser can open a camera.

IssueRegistering with a photo showed "This page couldn't load"

Large photos used to be sent as they were, and a request over 4.5 MB is refused before it reaches NookPass. Photos are now resized on the attendee's device to the field's size first, so this no longer happens. Ask the attendee to reload the form and try again.

More detail

Files in a File upload question are not resized, so they are checked as they are chosen instead: anything over 4 MB is refused there with a message, and the attendee can pick a smaller file.

Full reference

Everything, in detail. Folded away because you almost certainly do not need it to finish the task.

All thirteen field typeswhat each stores, and what it can validate

The type is chosen at creation and cannot be changed afterwards on a standard field. Controls a condition means this type can be the field a Show only when… rule points at — only closed sets qualify, because a condition compares for equality and free text never quite matches.

Type	Stores	Validation available	Controls a condition
Text	One line of text	Min/max length, pattern	No
Paragraph	Multi-line text	Min/max length, pattern	No
Email	One line, validated as an address	Min/max length, pattern	No
Phone	One line of text	Min/max length, pattern	No
URL	One line of text	Min/max length, pattern	No
Number	A number	Minimum, maximum	No
Date	A date	None — use Required	No
Dropdown	One choice from the list	Min/max length, pattern	Yes
Multiple choice	One choice, shown as radio buttons	Min/max length, pattern	Yes
Checkboxes	An array of choices	Min/max selections	Yes
Checkbox (yes/no)	True or false	None — use Required	Yes
Image upload	A photo, cropped to the field's size in the attendee's browser (Photo tab)	None — use Required	No
File upload	An uploaded file, up to 4 MB	None — use Required	No

The four switches, and the combinations they makewhat Ask, Required, Show and Can edit each control

Registration form is the pair Ask (on the public registration form) and Required (cannot submit without it). Attendee app is the pair Show (in Edit Profile — a locked row above the form, *Not set yet* when empty) and Can edit (in the form, theirs to change). Neither pair affects the dashboard — your team always sees and edits every field there.

The second switch of each pair is disabled while the first is off. Turning Ask off clears Required; turning Show off clears Can edit; turning Show on starts view-only, with Can edit off. Stored, the pairs are two values per field — registration (off / optional / required) and profile (hidden / view / edit) — so no combination is impossible to save. There are no presets; the table names the common combinations.

Case	Ask	Required	Show	Can edit	Example
Asked, they can change it later	On	Either	On	On	Name, company, job title
Asked once, then locked	On	Either	On	Off	They see it in the app but can't change it
Asked once, never shown back	On	Either	Off	Off	Dietary or accessibility needs
Filled in only in the app	Off	Off	On	On	A LinkedIn URL or bio
Your team fills it in, they can see it	Off	Off	On	Off	Lucky draw number, table or seat
Team only	Off	Off	Off	Off	Notes, tags, VIP flags

Fields whose settings are fixedEmail, Ticket ID and Ticket type

These are enforced on save as well as in the screen, so a hand-made configuration cannot get round them. A locked switch is greyed out on the row and in Who sees it, which adds a line saying why.

Field	Ask	Required	Show	Can edit	Why
Email	On, locked	On, locked	On, locked	Off, locked	It is the identity and the sign-in address; editing it in the app would change who can sign in
Ticket ID	Off, locked	Off, locked	Either	Off, locked	QR sign-in matches on it — an attendee editing theirs could claim someone else's
Ticket type	Off, locked	Off, locked	Either	Off, locked	Set by your team or the system; a self-typed ticket type would label anyone VIP

The thirteen standard fieldswhat ships with every event, and how each starts

Standard fields cannot be deleted or retyped; their label and the four switches are editable (within the limits above). A field with a column of its own is queryable and sortable; the rest are stored the same way custom fields are.

A standard field with every switch off is not listed: it is a chip under Standard fields in the Add to form panel. Clicking the chip appends it to the list asked and editable — Ticket ID and Ticket type shown and view-only. The row's bin — Remove from form, also on the Advanced tab; every standard field but Email — does the reverse, at once, with Undo on the toast. A row switched off by hand stays on the list, badged Not used, until the next save or reload.

Field	Type	On a new event	Switches by default	Own column
First name	Text	Listed	Ask, Required, Show, Can edit	Yes
Last name	Text	Listed	Ask, Show, Can edit	Yes
Email	Email	Listed — fixed	Ask, Required, Show (all locked)	Yes
Mobile	Phone	Chip under Add to form	All off	No
WhatsApp number	Phone	Listed	Show, Can edit	No
LinkedIn profile	URL	Listed	Show, Can edit	No
Company	Text	Listed	Ask, Show, Can edit	Yes
Job title	Text	Listed	Ask, Show, Can edit	Yes
Category	Text	Chip under Add to form	All off	No
Ticket type	Text	Chip under Add to form	All off (only Show can change)	Yes
Ticket ID	Text	Chip under Add to form	All off (only Show can change)	Yes
Bio	Paragraph	Chip under Add to form	All off	Yes
Profile photo	Image upload	Chip under Add to form	All off	Yes

Events set up before the switches existedhow Visible and Admin only were converted

Fields used to have one Visible switch (the eye icon — registration and profile together) and an Admin only switch on the Advanced tab. Both are gone. Existing events were converted when their fields are read, and nothing changes for attendees until someone edits the fields:

- a field that was visible (and not admin-only) became Ask on — with Required if it was required — and Show and Can edit on;
- a field that was hidden, or admin-only, had all four switches turned off (a standard one now waits under Add to form).

The old Display tab was folded into General (Width is there now), and Required moved from the General tab into the Required switch.

Which validation appears for which typewhy the Validation tab keeps changing

Types	Validation tab shows
Number	Minimum, Maximum
Checkboxes	Min selections, Max selections
Date, Checkbox (yes/no), Image upload, File upload	Nothing — the note says to use Required
Text, Paragraph, Email, Phone, URL, Dropdown, Multiple choice	Min length, Max length, Pattern (regex), Error message

The Photo tabimage fields only

Setting	What it does	Default
Size	The width and height the photo is cropped and saved at, 100–2000 px a side. Four presets, or type your own.	600 × 600
Let them use the camera	Adds Take photo, with a live preview, beside Choose photo.	Off
Show a face frame	An oval over the camera and the cropper, to put a face in.	On for Profile photo, off for other image questions

Where values are storedand what that means for exports and imports

Standard fields that own a column are written to that column on the attendee record. Everything else — the standard fields without one, and every field you add — is stored on the record under its Field name.

The practical consequences: values in a column can be sorted and filtered in the attendee list; the others are still exported, still imported and still editable, but are not sort keys. Adding a field never requires a database change, which is why there is no limit and no waiting.

The import sample CSV includes every field in use: every custom field (internal ones too — an import is how a table number gets there) and every standard field that is asked at registration or shown in the app. A standard field with every switch off is left out.

On a bulk import, a multi-value answer may be given as one cell separated by ; or ,; a yes/no field accepts true, yes, y, 1, on or checked; a number that will not parse is skipped rather than stored as text; and a blank cell is skipped rather than written as an empty value, so an import never blanks an answer somebody already gave.

Which surfaces read this configurationone list, several consumers

Surface	Shows	Can edit
Registration form	Fields with Ask on	The attendee, at registration
Edit Profile in the app	Fields with Show on and Can edit off as locked rows above the form; Can edit fields in the form	The attendee, any time — Can edit fields only
Business card	Only fields the attendee can see themselves (Show on)	—
Attendee list (Registration → Attendees)	Columns you pick, headed by each field's Report column name — or its display label when that is blank	—
Admin add/edit attendee	Every field, whatever its switches, by its full display label	Your team
CSV export	Every field, headed by its Field name	—
Bulk import	Every field, mapped by Field name; the sample CSV leaves out standard fields with every switch off	Your team

Rules that are easy to get wrongthe behaviour behind the pitfalls

Required is not retroactive. It is enforced when a form is submitted, so it applies to registrations made after you set it and to nobody else.

Required applies in Edit Profile only to fields with Required on. A field first met in the app is never forced.

The second switch follows the first. Required is locked off while Ask is off, and Can edit while Show is off; turning Ask or Show off clears its partner, and turning Show on starts view-only.

A hidden field is exempt from Required. If a Show only when… condition is not satisfied, the field is not shown and its Required rule is not enforced — otherwise a conditional question could block a form the attendee cannot even see.

A condition on a field the registration form does not ask counts as met there. The follow-up is shown to every registrant, and its row warns: *“…” isn't asked at registration, so every registrant sees this.* In Edit Profile, a condition on a field the attendee cannot edit is judged against the value already on their record.

A condition pointing at a missing field resolves to visible. Deleting a controlling field makes its dependants appear for everyone. The alternative — hiding them — would let one deletion silently drop questions from a live form.

An invalid regex is ignored. A pattern that will not compile does not block submission and does not warn; it simply stops validating.

Field names are unique and stable. Two fields cannot share a name, and a name is generated once from the label at creation. Editing the label afterwards never moves the key.

Email, Ticket ID and Ticket type are clamped to their fixed switches on every save and read, regardless of what is stored.

registration settings upload attendees attendees attendee profile