Registration Fields
Which optional details new users are asked for when they sign up, and whether each is required.
| Section | Settings → Accounts |
| Panel route | /admin/registration-fields |
| Access needed | Platform → Settings → View list |
Whatever you enable also becomes a column in Users and a search option there. It quietly decides how findable your customers are later.
The two switches
Each field has two:
| Switch | Meaning |
|---|---|
| Show | The field appears at signup |
| Required | The visitor cannot finish signing up without it |
A field must be shown before it can be required: Required stays greyed out until Show is on, and switching Show off also switches Required off.
The predefined fields
Phone number · WhatsApp · Telegram · Birth date · National code · Gender · Passport number · Citizenship · Residence
All nine start hidden and optional until you switch them on.
Custom fields
Add custom field adds your own beyond the predefined list. Each has the same two switches.
| Field | Accepts |
|---|---|
| Label | Required — what the visitor sees, up to 255 characters |
| Key | Lowercase letters, numbers and underscores, starting with a letter, up to 64 characters — must be unique |
| Type | Text, Date or Number |
Up to 50 fields in total, the nine predefined ones included.
The key is the field's identifier and is best left alone once customers have answered it.
| Action | Does |
|---|---|
| Save | Applies the configuration |
| Reset | Discards unsaved changes |
The trade-off
Every field you add is friction at exactly the moment a visitor decides whether to bother.
A field nobody looks at costs you sign-ups for nothing. Two good questions beat eight speculative ones.
Worth asking for:
| Field | When |
|---|---|
| Passport number | You sell international flights or visas and would otherwise chase it later |
| National code | Local regulation or supplier rules require it |
| WhatsApp or Telegram | That is genuinely how your support team reaches customers |
What happens to existing customers
Enabling a field does not go back and ask people who already registered. Their column in Users is simply empty.
What customers see
The sign-up form, with your enabled fields. Required ones must be filled before the account is created.
Scenarios
Cut sign-up drop-off
Disable everything not strictly needed. Collect passport details at booking instead, where the customer is already committed.
You need a detail your predefined list does not cover
Add a custom field with a clear label and a sensible key.
You need to find customers by a detail
Enable that field. It becomes a search option in Users.
Questions
Can I make a field required without showing it? No.
Are existing customers asked for a newly enabled field? No.
Can I delete a custom field? Yes — Remove field. Values already collected for it are no longer a column or a search option in Users, but they still appear under Show Full Information.
How many fields can I have? Up to 50.
Does this apply to social sign-in too? Yes. A new customer who signs in through a social provider still completes the sign-up form, with every field you show and every field you require.