Forms, workspaces & routing

Allowed origins and timezone

Each form can restrict which origins are allowed to submit to it (allowed_origins) and set a timezone for how dates display (time_zone) - both from the dashboard's Settings tab. Leave either unset and the form inherits its workspace's default instead; set your own value on the form to override it. The dashboard always shows the effective value actually in force (its own override if set, otherwise the inherited workspace default) - the section's icon ("+" versus a pencil) tells you at a glance whether the form has its own override or is inheriting.

Vanity slugs

On Pro plan and higher, a form can have a custom slug (f.bootform.com/contact-acme) instead of its raw UUID - set from the Settings tab. Useful for making a public-facing endpoint look first-party rather than a random ID.

Workspaces

Workspaces group forms together and let you set shared defaults once instead of per form - allowed_origins, time_zone, CAPTCHA, and email-branding removal can all be set at the workspace level and inherited by every form in it. Every account starts with one default workspace; creating additional ones requires Pro plan or higher. A form belongs to exactly one workspace at a time, and can be moved between workspaces you own.

Form Rules

On Business plan, forms can have conditional rules that route or act on a submission based on its field values - configured from the dashboard's Workflow tab, evaluated in order. A rule pairs one condition with one action:

Conditions: always match, a field is empty, a field is not empty, a field contains a keyword, or a field does not contain a keyword.

Actions: send an email to a specific recipient, tag the submission as spam, or redirect the submitter to a specific URL.

For example: "if department contains housewares, send email to housewares@example.com" routes that one category of submission to a different inbox than the rest.