7. Every Setting Explained

Now, Or At The Next Publish
Above everything on this screen is one sentence: Each one says whether it takes effect now or at the next publish.
Every group of settings on the screen carries one of exactly two lines under its heading, and they mean what they say.
Applies to the form that is already live, as soon as you save.
Takes effect the next time you publish, because it changes what a respondent reads. A form that is already live keeps what it had when you published it.
The dividing line is simple once you see it. Anything a respondent reads is part of the published snapshot, so changing it waits for a publish. Anything about whether they may answer, or where the answers go, is live and takes effect on save.
Nothing Is Saved Until You Save It
The Settings screen does not save as you go — the builder does that, this screen does not. Change anything and a bar appears along the bottom saying You have changes that are not saved yet. with two buttons: Discard and Save changes.
Nothing you have touched has reached the form until you press Save changes. That includes the Design tab: the preview updates as you click, but the theme is not stored until you save. (The Design dialog inside the builder is the opposite — it applies as you pick. Same controls, two places, and each says which it is.)
Try to leave with the bar still showing and FlyForms asks first — You have unsaved changes, with Discard changes, Stay on this page and Save changes.
Text boxes on this screen commit when you click away from them rather than as you type, so a half-typed address is not staged.
There are five tabs. Here is every setting on each.
General
Everything on this tab takes effect at the next publish.
How People Move Through It
Show a progress bar — Tells a respondent how much is left. On to begin with.
Start the progress bar part-filled — Opening a form that is already a little complete makes people more likely to finish it. Off to begin with. It is a small and well-documented piece of human behaviour: a task that has already started feels more finishable than one that has not.
Refusing A Submission
This is for the thing one question cannot say on its own — two answers that contradict each other. A delivery date before the order date. A total that does not match the parts.
Press Add a rule and you get: Refuse it when — all of these are true or any of these are true — followed by one or more conditions, each reading question · comparison · value. The comparisons are the same eight you meet in the builder's rules: is, is not, contains, does not contain, is greater than, is less than, is empty, is not empty.
And tell them is what the respondent reads when the submission is refused. Write it as a sentence they can act on — the placeholder shows the shape: The delivery date has to be after the order date.
A form takes up to five such rules, and each rule up to five conditions.
When They Are Finished
Send them somewhere afterwards — a web address. Leave empty to show your thank-you screen instead.
Access
Everything on this tab takes effect immediately.
Who Can Reach It
Search engines may list this form — An unlisted form stays out of search results. Anyone with the link can still open it. Off to begin with. Note the second sentence carefully: this is about listing, not about locking. The link is still a public link.
Ask respondents to prove they are human — four cards to choose between: No challenge, Cloudflare Turnstile, Google reCAPTCHA and FlyForms challenge. No challenge to begin with. Underneath: A challenge before a submission is accepted. The always-on checks stay on either way — the protections described on page 11 do not switch off when you choose No challenge.
Choose reCAPTCHA and a red line appears: reCAPTCHA is known to misbehave on a custom domain. Turnstile does not.
Turnstile and reCAPTCHA can run on your own keys. An owner sees Use your own keys (or Replace your keys when there are some), which asks for a Site key and a Secret key, and notes: These are your organisation's and apply to every form in it. The Save keys button here is the one control on the screen that saves at once rather than waiting for the bar — they are the organization's credentials, not this form's setting.
The FlyForms Badge
Remove the "Powered by FlyForms" badge — The badge sits under the last question on the form itself. Off to begin with.
When It Takes Answers
Opens and Closes are two date-and-time pickers. Underneath: Times are in [your workspace timezone]. Stored as exact moments, so they mean the same thing wherever a respondent opens the form. Leave either empty for no limit at that end. Somebody opening the form from another country gets the moment you meant, not the clock reading you typed.
Stop after this many answers — a number, or empty for no limit. The form closes itself once it reaches this, and says it is full rather than that it is closed. Somebody arriving late is told the form is full, which is a different and more useful thing to be told.
Refuse a submission with nothing in it — Only useful when every question is optional — otherwise the required ones already stop it. Off to begin with.
Where It May Be Embedded
Fit the frame to the questions — The embed grows and shrinks with the form, so the page scrolls instead of a box inside it. Turn it off if you have given the frame a height of your own. On to begin with, and it is the one live setting that starts on.
Sites allowed to embed this form — a box, one address per line. One per line,
as a scheme and a host — no path. Empty means any site may embed it. So
https://example.com, not https://example.com/contact. Up to fifty of them.
Responses
Telling You About New Answers — Takes Effect Immediately
You start with one notification email, and you can have up to five, so different people can be told different things about the same answer.
Each one is a card with a switch (on or off), a name of your choosing — What this email is for — and a one-line summary of who gets it and when. Open a card and you get:
Who gets it — Separate addresses with a comma. Leave it empty to tell everyone on the form who can read responses. Up to twenty addresses.
Except these people — appears only while the recipients box is empty, because it only makes sense there. Somebody added to read one report should not be signed up to every answer.
Send this one — every time, only when all of these are true, or only when any of these are true, followed by conditions built the same way as everything else. A question or a calculated value, compared the same way the builder's logic compares it. Five conditions is the most a rule takes.
Replying goes to — appears once the form asks for an email address. The first choice is Us — replies come back to FlyForms; the others are your email questions. Pick the question that asks for their address, and hitting reply reaches them instead of us.
Subject line — what you see in your own inbox.
What it says — the words above the answers, with bold, italic and a link. A line above the answers. Leave it empty to send just the answers. Under the box is a row of buttons, one per question, headed Add an answer: — press one and that answer is dropped into the text, so a subject or a body can name the person who sent it.
One thing that is not there yet, and the screen says so rather than leaving you looking: A daily digest is not available yet: it needs a timezone for the workspace, so that "daily" can mean one thing.
Telling The Person Who Answered — Takes Effect At The Next Publish
Email them a copy — Sent when they submit, to an address they gave you. If the form has no email question the switch is not available and says why: Add an email question first — there is nowhere to send it.
Once it is on:
Send it to the answer from — which email question the address comes from.
Subject — What they see in their inbox before they open it.
Include what they answered — A copy of their own answers, which is what most people want a receipt for. Off to begin with.
Privacy
What Is Recorded — Takes Effect Immediately
Collect nothing that identifies a respondent — No IP address, location, device or browser is stored, and respondents are told so. Off to begin with.
If the form itself asks something identifying — a name, an email address — the switch is unavailable and tells you why, naming the questions: Remove these first — each one can identify a respondent. Promising anonymity on a form that asks for an email address is a promise the form breaks.
How Long Answers Are Kept — Takes Effect Immediately
Delete answers after so many days — Answers and any files uploaded with them are erased for good. Leave it empty to use the period set for the whole account. Up to ten years. Where the account has its own period, a second line says so and adds the rule: A form can be stricter than that, never looser.
What They Agree To — Takes Effect At The Next Publish
Ask for consent before submitting — Adds a box a respondent ticks, recorded with their response. Off to begin with. Turning it on reveals:
What the box says — Write it in your own words. It is recorded with the response exactly as it was worded at the time. That last clause matters: if you reword the consent later, the responses you already have keep the wording those people actually agreed to.
They cannot submit without it — on to begin with. Turn this off to record agreement without requiring it.
Link to your privacy policy — The policy they are agreeing to. The consent box links to it.
Design
The same theme, colour and branding controls the builder's Design dialog offers, described in full on the previous page. The one difference is the one already mentioned: here they are staged behind Save changes like everything else on this screen, rather than applying as you pick.
When Something Is Not On Your Plan
Nothing on this screen is ever hidden from you. A setting your plan does not include is shown in place, greyed, with a small padlock beside its name, and its description replaced by Not on your plan. On the Design tab the colour controls say Changing a theme's colours is not part of this plan. Every theme above is still yours to use, and the logo says Putting your own logo on a form is not part of this plan.
Showing a locked control explains what the product does; hiding it explains nothing and sells nothing.
Next: Sharing and embedding →