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

# Build and publish a registration form

> Choose the questions, set capacity and the registration window, publish the form, and share it as a hosted link or on your website.

Each event has one registration form. You build it on the event's **Registration** tab, publish it, and share it as a hosted link or embed it on your website. Both show the same form and add participants to the same list.

## Choose the questions

Every form asks for name and email, an optional phone number and company, and shows a privacy notice. You don't need to add these.

In **Questions**, add anything else you need:

1. Choose **Add a question** and pick one of your workspace's registration fields. Workspace admins can create a field with **New question**.
2. Use the arrows to change the order, or remove a question.
3. Choose **Save questions**.

Workspace admins can also change a question's wording and help text on this form, choose whether participants must answer it (**Required**), and make it a **Restricted answer**. Use a restricted answer for sensitive information such as dietary or accessibility needs. It's stored separately and only the organiser and workspace admins can see it.

Saved questions reach the public form the next time you publish.

## Registration settings

**Registration settings** take effect as soon as you save them, without publishing.

* **Accepting registrations**: participants can register while this is on and the form is published.
* **Opens** and **Closes**: the registration window, in the event's time zone. Leave them blank for no limit. Registration closes exactly at the closing time.
* **Capacity**: the number of seats. Leave it blank for no limit. Only registered participants take a seat. Lowering the capacity doesn't remove anyone.
* **Waitlist**: when the event is full, new registrations join the waitlist. With the waitlist off, the form tells visitors the event is full.
* **Form language**: **Danish** or **English**. The whole public form, the confirmation page and participant emails use this language. A change reaches the public form when you publish.

## Preview

**Preview** shows the form as participants will see it, with the saved questions in the form language. Switch between **Mobile** and **Desktop**. Submitting is turned off in the preview.

## Publish

Nothing is public until you publish. In **Publication**, choose **Publish**. The form gets a public address that stays the same for the life of the event.

After you change the questions or the form language, **Publication** says the form has changed. Choose **Republish** to update the hosted page and every embed. Participants who already registered keep the answers they gave.

Changing the planning status never publishes or unpublishes the form. You can't publish a cancelled event, an archived event or a form with archived questions.

## Share the hosted link

Once published, **Hosted link** shows the form's own page. Choose **Copy link** to share it in emails, newsletters or social posts, or **Open hosted page** to check it.

The hosted page shows the event title, time, location and public description above the form. It works on phones and doesn't need an account.

## Embed the form on your website

1. In **Embed on your website**, choose **Copy code**.
2. Paste the code into an HTML or embed block on your website. Always copy it from Floral. It contains a link to the hosted page and a short script that replaces the link with the form.
3. Publish the web page and submit a test registration.

The embedded form resizes to its content and works on mobile. Republishing in Floral updates it without new code. No plugin is needed.

If your website removes scripts or blocks embedded content, visitors see the link to the hosted page instead of the form. The hosted link is always a working fallback, so you can also add it as a button.

## What participants see

After registering, participants see whether they're registered or on the waitlist, and receive a confirmation email. The email has a link where they can view, change or cancel their registration. See [Manage participants](/product/event-participants#help-participants-manage-their-registration).

The form never tells a visitor whether an email address was already registered. A visitor who registers twice gets the same answer and a confirmation to that address.

The form may show a short security check to stop automated sign-ups.

## Stop registration

* To pause registration, turn off **Accepting registrations**. The form stays online and says registration isn't open.
* To take the form offline, choose **Unpublish**. The hosted page and embeds show **Registration unavailable**. Participants and their answers are kept, and publishing again uses the same address.

The public form also closes when the registration window ends, when you cancel the event and when you finalise attendance.

## If the form says registration is unavailable

Check these in order:

1. **Publication** says **Published**.
2. The event isn't archived.
3. The embed code on your website matches the code in **Embed on your website**.

If all three are right and the form still says **Registration unavailable**, contact support.