> ## Documentation Index
> Fetch the complete documentation index at: https://help.dreamcast.in/llms.txt
> Use this file to discover all available pages before exploring further.

# How to build your registration form

> Add questions of any field type, set validations like required and unique, OTP verification and visibility, and show questions conditionally.

**In short:** Your registration form decides what you collect from each guest. Build it under **Registrations → Form** — add questions, control which are required or unique, and show questions only when they apply.

## The form at a glance

![The Form Questions tab listing fields with their field type and category count](https://mintcdn.com/dreamcast-4085c99b/Ucuw7Zzcf8NybmpK/images/regplus-form-questions.jpg?fit=max\&auto=format\&n=Ucuw7Zzcf8NybmpK\&q=85\&s=ca9d910cbd62ce7547af4c25905e21a1)

* **Collect data from all guests** — turn on to capture form details for **every** attendee in an order, not just the booker.
* Each question shows its **field type** (Text, Email, Phone, Single Select…) and how many **ticket types** it applies to.
* Use **Preview** to see the form as guests will, and the **⋮** menu on a question to **Edit** or **Delete** it.

## Step 1 — Add questions

Open a question's **⋮ → Edit** (or add one from the library) to open the field editor. The **Question Library** on the left lists every field type you can add:

![The Add form fields editor with the question library of field types and the per-ticket validations table](https://mintcdn.com/dreamcast-4085c99b/Ucuw7Zzcf8NybmpK/images/regplus-form-fields.jpg?fit=max\&auto=format\&n=Ucuw7Zzcf8NybmpK\&q=85\&s=48d4a47a459aa661ddb9fc02f7e2b543)

Common field types include **First/Last Name**, **Email**, **Phone**, **Title**, **Single Select**, **Company**, **Designation**, **Country**, **Address** and **Profile Picture** — toggle one on to add it to your form.

## Step 2 — Set validations per ticket type

In the field editor's **Validations** tab you control the question for each ticket type at once. The **Master · Apply to all** row sets every ticket type together, or set each row individually:

| Column | What it does |
| - | - |
| **Required** | Guest must answer before they can register |
| **Unique** | The same answer (e.g. an email) can't be used twice — stops duplicate sign-ups |
| **Enable OTP Verification** | Verify the answer (e.g. phone/email) with a one-time code |
| **Visibility** | Whether and how the question shows for that ticket type |

## Step 3 — Show questions conditionally

Switch to the **Conditions** tab to show a question only when an earlier answer matches a rule — for example, ask *"Please specify your diet"* only when **Dietary preference** is *Other*.

![The Conditions tab where you add rules that must match for a question to show](https://mintcdn.com/dreamcast-4085c99b/Ucuw7Zzcf8NybmpK/images/regplus-form-conditions.jpg?fit=max\&auto=format\&n=Ucuw7Zzcf8NybmpK\&q=85\&s=322f640d8e560c8e55df09dc27c2c089)

**1. Open Conditions**

In the field editor, open the **Conditions** tab and click **Add Condition**.

**2. Define the rule**

Choose the earlier question, the match (e.g. *is*), and the value that should reveal this question.

**3. Save**

Click **Save Changes**. Questions with a rule show a **condition** badge in the list.

## FAQ

> **Can different ticket types ask different questions?**
>
> Yes. Each question's **Validations** row is set per ticket type, and **Visibility** lets you hide a question for ticket types it doesn't apply to.

> **How do I stop one person registering twice?**
>
> Turn on **Unique** for a one-per-person field like email or a staff ID. See [Prevent duplicate sign-ups](/regplus/how-to-prevent-duplicate-signups).

> **Can I edit the form after publishing?**
>
> Yes — changes go live immediately. Take care removing or renaming a field guests have already filled, as it affects the data you've collected.

## What's next?

> **[Build your ticket types](/regplus/how-to-ticket-types)**
>
> What guests choose before the form.

> **[Design and print badges](/regplus/how-to-badges)**
>
> Put form answers on badges.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.