> For the complete documentation index, see [llms.txt](https://eventx-hq.gitbook.io/knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://eventx-hq.gitbook.io/knowledge-base/registration-and-ticketing/registration-form/registration-form-fields.md).

# Registration Form Fields

Registration form fields determine what information you collect from attendees during sign-up. EventX provides default fields, custom field types, reusable field templates, conditional logic, and multi-language support.

***

## What Are the Default Registration Form Fields?

Every event comes with a set of default fields that appear on the registration form:

* **First Name** (configurable: can be made optional)
* **Last Name** (configurable: can be made optional)
* **Email Address** (configurable: can be made optional)
* **Secondary Email** (optional)
* **Job Title** (optional)
* **Organization** (optional)
* **Contact Number** (optional)
* **City** (optional)
* **Country** (optional)

All fields, including **First Name**, **Last Name**, and **Email Address**, can be made optional by toggling off the **Required** toggle on the registration form.

![](/files/tOyC4vLL3vj4lJA0EcW0)

***

## How to Rename Registration Form Fields

Organizers can rename both default and custom fields to match their event's terminology. Renaming helps you use language your attendees are familiar with.

1. On the **Registration Form** page, click the **edit icon** on the form. ![](/files/AR3KXZGwEL4x8pxZVep6)
2. Click the **edit icon** next to the field you want to rename. ![](/files/GCDlFEu0a7DO4pbFc74x)

   ![](/files/BaChUdkWpCOPY6yq2XFr)
3. Make changes to the field name and click **Save**. ![](/files/JoePC5nwtGjFpitT5cun)
4. If a default field is renamed, the original default name is shown below the field for reference. ![](/files/qjtxhx8eXlNydSMMvE3K)

### How to Customize the Country Code Field

Organizers can customize the country code label that appears on the registration form. This is useful for international events where you want to display a specific country code format or label convention.

Click into the field edit page, modify the country code display name, then save. The country code label in the registration form will reflect your customized content.

![](/files/6Ur02M7GjyAidCRaJGTA)

***

## What Custom Field Types Are Available?

In addition to default fields, organizers can add custom fields to collect specific information. EventX supports three categories of custom fields:

### When to Use Each Field Type

| If you need to collect...                         | Use this field type  | Why                                                                        |
| ------------------------------------------------- | -------------------- | -------------------------------------------------------------------------- |
| A short answer (e.g., "dietary preference")       | **Short Text**       | Single-line, 255 character limit                                           |
| An open-ended response (e.g., "feedback")         | **Long Text**        | Multi-line, 1000 character limit                                           |
| One selection from options (e.g., "T-shirt size") | **Single Choice**    | Radio buttons — attendee picks one                                         |
| Multiple selections (e.g., "topics of interest")  | **Multiple Choice**  | Checkboxes — attendee picks several                                        |
| A long list of options (e.g., "department")       | **Dropdown**         | Compact menu for many choices                                              |
| A date (e.g., "arrival date")                     | **Date Picker**      | Calendar widget with min/max range                                         |
| A time (e.g., "preferred session time")           | **Time Picker**      | Time selector with min/max range                                           |
| A file (e.g., "upload resume or portfolio")       | **File Upload**      | Accepts .jpg, .png, .pdf, .doc, .docx, .xls, .xlsx, .csv, .txt up to 20 MB |
| Legal agreement (e.g., "agree to terms")          | **Consent Checkbox** | Single checkbox with a text statement                                      |

### Text Fields

| Field Type     | Description              | Max Length      |
| -------------- | ------------------------ | --------------- |
| **Short Text** | A single-line text input | 255 characters  |
| **Long Text**  | A multi-line text area   | 1000 characters |

### Choice Fields

| Field Type          | Description                                       |
| ------------------- | ------------------------------------------------- |
| **Single Choice**   | Attendee selects one option (radio buttons)       |
| **Multiple Choice** | Attendee can select multiple options (checkboxes) |
| **Dropdown**        | Attendee selects one option from a dropdown menu  |

For choice fields, organizers can add options in bulk instead of one-by-one:

1. Click **Bulk Add** on the field configuration. ![](/files/1DtUP8Ol7lpgKKYfZF1F)
2. Enter the first 2 options in the provided fields, then enter the remaining options in the text area — one option per line. ![](/files/HO5zB6g8B0GztoipAGrf)
3. Click **Confirm** > **Save**.

### Date Picker & Time Picker

Use these when you need structured date or time data rather than free-form text.

* **Date Picker** — Attendees select a date from a calendar widget.
* **Time Picker** — Attendees select a time.

Both fields support optional/minimum/maximum date and time range configuration.

### File Upload

Allows attendees to upload files as part of registration. Common use cases: resumes, portfolios, presentation slides, signed documents. See [Registration Form Setup](/knowledge-base/registration-and-ticketing/registration-form/registration-form-setup.md#3-file-upload-fields) for detailed configuration.

* **Maximum file size:** 20 MB per file
* **Accepted file types:** .jpg, .png, .pdf, .doc, .docx, .xls, .xlsx, .csv, .txt
* **Maximum files per upload:** 10

### Consent Checkbox

A single checkbox field for collecting consent — useful for terms and conditions, privacy policies, marketing opt-in, or photo release agreements. Not configurable as multi-select: one consent statement per field.

> **Note:** Consent text fields cannot be used as the `if` statement in conditional logic (see [Conditional Logic](#how-does-conditional-logic-work-in-registration-forms)).

***

## What is the Form Fields Library and How Do I Use It?

The Form Fields Library allows organizers to save standardised field templates and reuse them across multiple registration forms — eliminating the need to recreate commonly used fields for each new form.

**Prerequisites:** At least one registration form must exist.

### What is the Form Fields Library?

A central repository of predefined field configurations. When you add a field to the library, you can insert it into any registration form with its configuration (validation, dropdown options, conditional logic) preserved.

### Benefits

* **Time savings** — No need to recreate commonly used fields for each new form.
* **Standardized data** — Using the same fields across multiple forms produces consistent data that is easier to analyse and compare.
* **Central management** — Update a field in the library and the changes apply to all forms using that field.
* **Validated responses** — Configure validation, dropdown options, and conditional logic once; those rules apply wherever the field is used.

![](/files/5S17lSHbbdCta0t9dYE8)

### How to Use the Form Fields Library

1. Go to the registration form edit / configuration page.
2. You will see the default fields: Full Name, Job Title, Organization, Contact Number, City, Country. These fields cannot be modified at the library level; when used, their labels automatically change to match the attendee's selected event language.
3. To add new fields to the library, click **Manage Fields** > **Add New Field**. EventX provides the following field types:
   * **Selection type:** Single Choice, Multiple Choice, Dropdown
   * **Text type:** Short Text, Long Text
   * **Consent type:** Consent Text
4. If multi-language is enabled for the event, you can configure field labels in each language by switching language tabs.

![](/files/UIqEtF1X0kbA8yKedt9C)

> **Note:** Fields added to the library are available across all registration forms for the event. If a field is not already in the form you want to add it to, you need to open "Available Fields" to add it.

***

## How Does Conditional Logic Work in Registration Forms?

Conditional logic allows you to show or hide form fields based on an attendee's previous answers. This creates a dynamic, personalised registration experience — attendees only see questions relevant to them.

**Prerequisites:** At least one choice-type custom field (Single Choice, Multiple Choice, or Dropdown) must exist to act as the trigger.

### Benefits

* **Personalized registration experience** — Tailor the form to each attendee's responses.
* **Streamlined process** — Eliminate unnecessary fields, reducing friction and increasing completion rates.
* **Improved data accuracy** — Follow-up questions only appear when the relevant condition is met, ensuring precise data collection.

### How to Set Up Conditional Logic

**Step 1: Add all needed fields to the form**

Enable all the fields you need — both the conditional trigger fields and the fields that will be shown or hidden.

![Step 1: Add fields](/files/J6gAmWot1uh0iM4dqoI1)

**Step 2: Configure conditions**

Open the **Condition Setting** panel and define the logic rules.

![Step 2: Configure conditions](/files/jGbgyzx2fHBStdyVj9bf)

![Condition setting interface](/files/xduY0Y9LjnCXfitClS70)

A condition rule consists of:

| Component                     | Description                                            |
| ----------------------------- | ------------------------------------------------------ |
| **If** (Trigger Field)        | The field whose answer determines the condition        |
| **Equals To** (Trigger Value) | The specific option value that activates the condition |
| **Then Show** (Target Field)  | The field to show or hide based on the condition       |

### Condition Rules & Constraints

* **Condition Setting** is greyed out if no custom fields exist or no eligible fields are enabled.
* Only **choice-type fields** (Single Choice, Multiple Choice, Dropdown) can be used as the `if` statement.
* **Open-ended fields** (Short Text, Long Text, Consent Text) cannot be used as the `if` statement.
* All field types can be used in the `then show` setting.
* A field added to `then show` is **hidden by default** and only appears when the matching option is selected.
* **Hidden mandatory fields do not block registration.** If a required field is hidden by a condition, the attendee can still submit the form without filling it in.

**Example:**

* Q: "What do you want to eat for lunch?" → Options: "Meat", "Vegetable"
* **If:** "What do you want to eat for lunch?" **equals:** "Meat", **then show:** "What meat do you want?" (mandatory)
* If the attendee selects "Vegetable", the "What meat do you want?" field remains hidden and does not block registration.
* The same trigger field can be used in multiple condition rules.
* The same target field can be controlled by multiple condition rules.

***

## What's the Difference Between Display Name and Default Name?

For custom fields, there is a distinction between the **Display Name** and the **Default Name**. Understanding this difference is important when you need a field to appear differently in one form versus all forms.

| Attribute        | Scope                                                  | How to Edit                               | When to Use                                                                                      |
| ---------------- | ------------------------------------------------------ | ----------------------------------------- | ------------------------------------------------------------------------------------------------ |
| **Display Name** | Applies only to the current registration form          | Edit directly on the form                 | Give a field a form-specific label (e.g., "Your Department" in Form A vs "Department" in Form B) |
| **Default Name** | Applies across all registration forms using that field | **Manage Fields** > 3-dot icon > **Edit** | Change the field's name everywhere at once                                                       |

When changing the **Display Name**, the changes only affect the specific registration form.

When changing the **Default Name**, the changes are applied to all registration forms using that field.

![](/files/cjto5BaP0ZXXURpmtwoZ)

![](/files/iFgqurunE1OO62eBALXz)

***

## How to Configure Multi-Language Field Labels

When multi-language is enabled for your event, you can configure field labels in each supported language. Attendees see field labels in their selected event language automatically.

**Prerequisites:** Multi-language must be enabled in your event settings.

**Supported languages:** English, Traditional Chinese (zh-HK), Simplified Chinese (zh-CN), Korean, Japanese, Vietnamese, Spanish, Thai, Portuguese.

### How to Configure

1. Ensure multi-language is enabled in your event settings.
2. Go to **Registration Form** > **Manage Fields**.
3. Language tabs appear at the top of the field configuration panel. Switch between tabs to configure labels for each language.
4. Enter the translated field label for each language and save.

> **Note:** Default fields (Full Name, Job Title, Organization, Contact Number, City, Country) auto-translate based on the attendee's language. Custom field labels must be translated manually.

***

## What Form Settings Are Available for Registration Forms?

Several form-level settings affect field behaviour and the registration experience. These are toggled from the registration form configuration page.

| Setting                                                | Description                                                           | Where to Find It    |
| ------------------------------------------------------ | --------------------------------------------------------------------- | ------------------- |
| **Required Toggle**                                    | Makes a field mandatory. A red asterisk appears on required fields.   | Per-field setting   |
| **Enable Attendee Registration Editing**               | Allows attendees to edit their registration details after submission. | Form settings panel |
| **Unique Attendee Email**                              | Prevents multiple registrations using the same email address.         | Form settings panel |
| **Show Check-in QR Code Upon Registration Completion** | Displays a QR code to the attendee after successful registration.     | Form settings panel |
| **Promo Code Field**                                   | Adds a promo code field to the registration form for discounts.       | Form settings panel |
| **Display "Free" Price**                               | Shows the word "Free" next to free tickets on the registration form.  | Form settings panel |
| **Show Total Price Only**                              | Hides the per-ticket price breakdown; shows only the total price.     | Form settings panel |
| **Ticket Description Collapse**                        | Collapses ticket descriptions by default; attendees expand to read.   | Form settings panel |

***

## What Are the Limitations of Registration Form Fields?

### Field Naming

* Organizers can name two fields with the same name. This may cause confusion on the attendee-facing registration form, as there is no visual differentiator for registrants.

  ![](/files/6UkfFvWXH7EhcQYlgFq5)

### Renamed Default Fields

If a default field is renamed, the original field name is still used in the **People List** and **Attendee List Report**. For example:

* On the registration form, "First Name" is renamed to "Edited First Name".
* The People List and Attendee List Report will still display "First Name" and "Last Name".

  ![](/files/qjtxhx8eXlNydSMMvE3K)

  ![](/files/wYRG3sXQyVX0xqhq1Ii4)

  ![](/files/8JslmLJD5swKRNexgWxH)

### Field Name Independence

Field names are independent across different registration forms. If a field is renamed on **Form A**, the changes only apply to **Form A**.

### File Upload Constraints

* Maximum file size: 20 MB per file
* Accepted formats: .jpg, .png, .pdf, .doc, .docx, .xls, .xlsx, .csv, .txt
* Maximum 10 files per upload field

### Conditional Logic Constraints

* Only choice-type fields can be conditional triggers
* Open-ended fields cannot be conditional triggers
* Hidden mandatory fields do not block registration

***

## Common Questions

### Can I make First Name, Last Name, and Email optional?

Yes. All default fields, including First Name, Last Name, and Email Address, can be made optional by toggling off the **Required** toggle on the registration form. See [Default Fields](#what-are-the-default-registration-form-fields).

### Can I use conditional logic with text fields?

No. Only **choice-type fields** (Single Choice, Multiple Choice, Dropdown) can be used as the trigger field (`if` statement) in conditional logic. Short Text, Long Text, and Consent Text fields cannot trigger conditions. However, text fields **can** be shown or hidden as a result of a condition (the `then show` side). See [Conditional Logic Constraints](#condition-rules--constraints).

### Can I rename a field in one form without affecting others?

Yes — use the **Display Name**. Changing the Display Name only affects the current form. If you use the **Default Name**, the change applies to all forms using that field. See [Display Name vs Default Name](#whats-the-difference-between-display-name-and-default-name).

### What happens if a mandatory field is hidden by conditional logic?

Hidden mandatory fields do **not** block registration. If a required field is hidden because the triggering condition was not met, the attendee can submit the form without filling it in. See [Conditional Logic Constraints](#condition-rules--constraints).

### How do I reuse the same field across multiple forms?

Use the **Form Fields Library**. Add a field to the library from one form, then insert it into any other form from the "Available Fields" list. See [Form Fields Library](#what-is-the-form-fields-library-and-how-do-i-use-it).

### Can I upload files larger than 20 MB?

No. The maximum file size for file upload fields is 20 MB per file. If attendees need to submit larger files, consider asking them to provide a link (e.g., Google Drive, Dropbox) using a Short Text or Long Text field instead.

### How many custom fields can I add to a registration form?

There is no hard limit on the number of custom fields per form. However, be mindful of form length — longer forms typically have lower completion rates. Use conditional logic to hide irrelevant fields and keep the visible form concise.

### Can attendees see field labels in their preferred language?

Yes, if multi-language is enabled in your event settings. Default fields auto-translate. Custom field labels must be translated manually using the language tabs in the field configuration. See [Multi-Language Field Labels](#how-to-configure-multi-language-field-labels).