Site forms — contact, request, signup — are built here, and their submissions land here.
Submissions are always stored
Every accepted submission is recorded, whatever else you configured. If a notification email did not arrive, the submission is not lost; it is in the form's submissions list. Nothing in the form can switch storage off.
What happens afterwards is additional
A form can also email you, create a CRM lead, or POST the answers to an address. These run in that order, each on its own: if one fails the visitor still sees success and the submission is kept. The outcome of each is stored with the submission but no screen shows it, so a failed email or lead is invisible to staff. A CRM lead rejected as a duplicate is only written to the server log.
Forms are built in the Form Studio
A form is laid out with the same visual editor as pages, full screen, opened from the Forms list. Saving changes what visitors see at once, even while the form is published. Validation runs again on the server, but only for required, minimum and maximum length, pattern and show-when rules; email, number, date and option values are not format-checked there.
Publishing and the address
A new form is a draft: its public address shows nothing and it takes no submissions or uploads. Publish it to open /forms/<address>. The address is made when you create the form and can never change, because embeds and links use it. A Persian-only name gets an address like form, form-2.
Spam and limits
A hidden honeypot field is always on: a bot that fills it sees a success page and nothing is stored. Each connection may submit 10 times an hour. There is no captcha for staff to turn on, and the "spam protection" setting does nothing. A submission may carry up to 200 answers.
Changing a form does not change past submissions
Past submissions stay exactly as sent. Answers are stored under each field's key; if you change a key, old answers stop showing in the table and the CSV. A field hidden by a show-when rule at submit time is not stored.
Who can do what
Seeing the list needs View forms; creating, editing and publishing need Create & edit forms (publishing may also need a plan that includes it); deleting forms and submissions needs Delete forms; the submissions screen and file downloads need View submissions. The list shows every button to anyone who can open it, and the server refuses the ones you lack.