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

# Form Settings

> Configure notifications, styling, confirmation messages, and field mapping.

**Form settings cover notifications, the confirmation message, styling, availability, and the conversion mapping that pre-fills events from a submission.** Set them up once on the form's edit screen and they apply to every submission that comes in.

<Info>
  **This page covers features gated by Manager-tier permissions.** Managers and Admins have these by default; your administrator can adjust who has them in [Settings > Team](/settings/team).
</Info>

## Notifications

You choose whether you're notified when a new submission arrives, and who else should be copied in.

* **Send email when form is submitted** — toggle this off if you prefer to check submissions manually.
* **Additional recipients** — add extra email addresses (one per line) for anyone who should know about new enquiries, like your events manager or assistant.
* **Location email always included** — your location's email address receives every notification when notifications are on, on top of any extra recipients you add.

Notification emails are queued, so they're dispatched in the background and don't slow down the form for the customer.

## Confirmation message

After a customer submits the form, they see a thank-you screen with the title and message you write. Edit both under **After submit** on the form's **Basics** tab. The default reads "Thank you for your enquiry!" with a short follow-up line, and you can change either to suit your tone.

## Appearance and styling

Match your brand on the **Look & Feel** tab. You can set an accent colour, choose a body font and a heading font, pick the submit button text, and choose a button style (solid or outline) and corner radius.

<Info>
  If you've already styled one form, you can reuse those styles on another. On the **Look & Feel** tab, find **Copy style from another form**, pick the source form, and click **Apply Style** to copy its appearance settings across.
</Info>

## Conversion field mapping

When you convert an enquiry into an event, Digital Florists can pre-fill the event details from the submission. The mapping lives on the **Conversion** tab, which appears once **Show advanced** is on.

If your form uses the standard field names (`event_date`, `event_type`, `budget_range`, `guest_count`, `venue`, `notes`, `referral_source`), they're auto-detected and shown as "Auto-detected from …" with no further setup. Only use the mapping if you've renamed those fields or built your form from scratch.

You can map any of:

* **Event Date** — the form field that holds the date of the event.
* **Event Type** — wedding, corporate, workshop, and so on.
* **Budget** — the customer's budget.
* **Guest Count** — the estimated number of guests.
* **Venue** — venue name or location.
* **Notes** — the customer's description, brief, or vision.
* **Referral Source** — how the customer heard about you.

<Tip>
  Set the mapping up when you first build the form. It takes a moment and saves repeated re-entry when you convert submissions to events later.
</Tip>

## Availability

Control when your form accepts submissions from the **Form status** card on the **Basics** tab.

* **Active / Inactive toggle** — flip this off to pause submissions without deleting the form. Inactive forms can't receive new submissions.
* **Opens On** — turn on **Show advanced** to set a date when the form becomes available. Useful for seasonal forms, like a Valentine's Day enquiry form you want to go live in January.
* **Closes On** — set a date when the form stops accepting new submissions.
* Leave both dates blank to keep the form open at all times.

## Spam protection

Spam protection runs in the background. There's nothing to configure on the form itself.

Every form includes an invisible honeypot field and per-IP rate limiting. Bots that fill the hidden field are silently dropped, and repeated submissions from the same address are throttled.

## Common questions

<AccordionGroup>
  <Accordion title="Do I have to set up conversion field mapping?">
    No. If your form uses the standard names (`event_date`, `event_type`, `budget_range`, `guest_count`, `venue`, `notes`, `referral_source`), they're auto-detected and the mapping fields show "Auto-detected from …". If you don't set anything up and your fields use different names, you can still convert enquiries — you'll just fill in the event details manually instead of having them pre-filled.
  </Accordion>

  <Accordion title="Can I change the confirmation message after the form is live?">
    Yes. Update the title or body under **After submit** at any time. The change takes effect immediately for new submissions.
  </Accordion>

  <Accordion title="Will the honeypot field affect real customers?">
    No. The honeypot is hidden from real visitors and only triggers on automated bots.
  </Accordion>

  <Accordion title="What happens when a form reaches its closing date?">
    It stops accepting new submissions. Customers who visit the form after the closing date see an unavailable message and can't submit. Submissions received before the closing date are kept as normal.
  </Accordion>
</AccordionGroup>

## What's next?

<Columns cols={2}>
  <Card title="Building Your Form" icon="hammer" href="/events/form-builder">
    Add fields, set requirements, and design the form your customers will fill out.
  </Card>

  <Card title="Embedding Forms" icon="code" href="/events/embedding-forms">
    Get your form onto your website with a simple embed code.
  </Card>

  <Card title="Managing Submissions" icon="inbox" href="/events/managing-submissions">
    Review, organise, and follow up on enquiry submissions.
  </Card>

  <Card title="Converting Enquiries" icon="arrow-right-to-arc" href="/events/converting-enquiries">
    Turn a submission into a full event with pre-filled details.
  </Card>
</Columns>