Form settings

To open a form's settings, click the form in All Forms, or choose Edit settings in its row menu. The settings open on the form's Overview, with the list of sections alongside.

Changes in form settings aren't saved until you choose Save changes. While you have unsaved changes, the form shows an Unsaved changes badge, and Discard puts the saved settings back. If you leave with unsaved changes, Forms asks "Discard unsaved changes?": choose Keep editing, or Discard & leave. Once everything is saved, the button reads Saved.

Before saving, Forms checks that the form has a name and that a few settings are complete, such as a password for password access or a code for every coupon. If one isn't, it says what's missing and opens that section.

Saving needs a role that can edit forms: Owner, Admin, Manager or Member. For a Viewer, the button explains "Your role can't edit forms." At the top, Preview opens the form's public link in a new tab and Open builder opens the builder.

Form settings are grouped into sections. This guide covers Overview and Details, the Design and Flow groups, and Notifications, Access & Sharing and Security & Compliance in the Settings group. The other groups have their own guides:

• Build sums up the form's fields, layout and logic. You change them in the builder: see Form builder and Logic and scoring.
• Payments: see Payments.
• Sharing: see Publishing and sharing.
• Workflow: see Approvals and automations.
• Integrations: see Integrations and API.

The builder's Design, Schedule & limits and Submission sections change some of the same settings, and there they save on their own.

A form's Overview shows its Responses (all time), and its Views, Starts and Completion rate for the last 30 days. Under Public link are the form's address with a copy button, a QR code and shortcuts to Open builder, Preview, Responses, Share, Embed and Publish. At a glance lists its status, folder, fields, tags, description and when it was last edited and published.

Details holds:

• Form name: required.
• Description: shown under the form's title, and in the template gallery when the form is saved as a template.
• Folder / category: the folder the form is in, or No folder.
• Tags: type a tag and press Enter or choose Add. Tags are saved in lowercase, with dashes for spaces. Remove one with the × beside it.

A theme is a ready-made look for a form. Under Design → Themes & Colors, Themes shows 10 Presets (Geiger, Daylight, Midnight, Ocean, Forest, Editorial, Studio, Blossom, Poster and Terminal) and the project's Workspace themes. Click one to apply it. Applying copies the theme's look into the form, so later changes to the theme don't affect it. Choose Save changes to keep it.

A workspace theme saves a form's colors, fonts, images and logo so any form in the project can use them. To save one, choose Save current, type a Theme name, then Save theme. It's saved straight away. Each workspace theme's ⋯ menu has Rename and Delete. Deleting a theme doesn't change the forms that used it. Only the Owner and Admin roles can save, rename or delete workspace themes.

The rest of Design → Themes & Colors fine-tunes the look, with a Live preview beside it:

• Colour mode: Dark (the default), Light or Device, which follows each respondent's device.
• Accent colour: used for buttons, selections and the progress bar. Pick a swatch, Default or your own color as a 6-digit hex value like #6366f1.
• Corner radius: Square, Small, Medium (the default), Large or Round.
• Body font for questions, answers and buttons, and Heading font for titles (Same as body to start with). Search 100 fonts in four groups: Sans serif, Serif, Display and Monospace. Fonts load from Bunny Fonts, so respondents' IP addresses never reach Google.
• Background: Plain (the default), Gradient (a glow tinted by the accent color) or Image, which shows the Cover image behind the form.

In the builder's Design section, the Header settings also add a cover at the top of the form, from a gradient or an image.

Design → Welcome & Ending sets what respondents see before and after the form.

• Show a welcome screen adds an intro before the first question, with a Title, a Body and a Button label (Start to start with). The body can recall values from the form's link, like Hi {Name}.
• After submission shows a Thank-you message with a Title and Message (Response submitted, to start with), or Redirect to URL, which sends respondents to another page. Merge tags work in both, including in the redirect's query string.
• Show score shows the response's score, or the quiz result, on the thank-you screen.
• Allow another submission adds a Submit another response button.

When the form uses named outcomes, Outcome endings lists each one and whether it has its own ending, redirects or uses the default. Outcome endings are set on their branch in the builder. See Logic and scoring.

Design → Branding holds the form's Logo: upload an image, or link a PNG or SVG. It shows above the form's title only while Show form icon is on (in the builder's Design section, the same switch is called Show logo). Add Logo alt text for screen readers, unless the title already names your brand. Turn off "Powered by Geiger Forms" footer to remove Geiger branding from the public form.

Design → Localization sets the Language of the form's built-in text, such as buttons, validation messages and dates: English (the default), Español, Français, Deutsch, Português, हिन्दी (Hindi) or العربية (Arabic). An Arabic form reads right to left. Your own questions and texts aren't translated, so write them in the same language.

Flow → Multi-step Pages sets how respondents move through the form.

• Conversational mode: shows one question per screen. Respondents press Enter to move on (Shift Enter adds a new line in long text), and can press a letter key to pick a choice. When it's off, each page shows all of its questions.
• Progress bar: shows respondents how far along they are. It's on to start with.

The Pages list shows each page with its number of fields, and marks pages that are skipped by conditions as Conditional. You add page breaks in the builder: Open builder takes you there. See Form builder.

While respondents fill in a form, Forms saves their progress as they go, so their unfinished answers show under Responses → Partial / Abandoned. Flow → Save & Resume controls how that works:

• Save & resume (off to start with): adds a Save & continue later button. It gives respondents a link to pick up where they left off on any device, and can email it to them.
• Offline drafts (on to start with): keeps answers on the respondent's device, so a refresh or a lost connection doesn't lose work. A respondent who comes back is asked "Restore your draft?", and a response submitted offline is sent once the connection returns.
• Ask before saving progress (off to start with): respondents see Save my progress as I go, and nothing is stored on the server until they tick it. Unticking it deletes what was saved. Respondents who don't opt in never appear in Partial / Abandoned or the drop-off reports.

Emailing a resume link needs email to be set up for your deployment.

Flow → Submission Rules starts with when the form accepts responses.

• Opens on and Closes after: the form accepts responses between these dates, including both days, which start and end at midnight UTC. Before the start, respondents see Not open yet with the opening date. After the end, they see This form is closed.
• Closed message: what respondents read once the form has closed or is full.
• Maximum responses: the most responses the form takes. Leave it empty for no limit. Once it's reached, respondents see Response limit reached.
• Show remaining spots: shows respondents how many places are left, like "12 of 50 spots left".

The same settings are under Schedule & limits in the builder. A published form that closes within the week or nears its limit is counted on the project overview.

The rest of Flow → Submission Rules sets how respondents confirm and change what they send.

• Minimum review time (seconds): blocks a response submitted faster than this. Respondents see a countdown before they can submit.
• Respondent edit link: after submitting, respondents get a private link to change their answers, on the thank-you screen and in their confirmation email. Choose how long it works: Off (the default), 1 hour, 24 hours, 7 days, 30 days or Always.
• Allow submitting on behalf of someone: signed-in respondents can tick "I'm submitting on behalf of someone else" and give that person's name and email.
• Require attestation: a required checkbox with your Statement right before the submit button.
• Require policy acknowledgement: respondents read a policy, from its Policy title and Policy text or a link to it, and confirm before the form opens. Must scroll to the end and Type full name to acknowledge are on to start with. The form's report lists who acknowledged it.

Duplicate detection spots a respondent submitting the same form twice. Under Flow → Submission Rules, turn on Detect duplicates, then:

• Under Match on, select the fields to compare: short text, email, phone, full name, number, website and hidden fields. A response is a duplicate when every selected field matches an earlier response.
• Look back (days): how far back to compare, 30 days to start with.
• When a duplicate arrives: Accept and flag it (the default) saves it with the status Needs review, and Block the submission turns it away with "It looks like you've already submitted this form."

Fields marked as sensitive are never compared.

Settings → Notifications sets the emails a form sends. These need email to be set up for your deployment, and the section warns you when it isn't.

• Email respondents a confirmation: sends the respondent a Subject and Body of your choosing, with a copy of their answers, right after they submit. It goes to the first email answer, so the form needs an Email field. Merge tags work in both.
• Email these people on every new response: type addresses and press Enter. Each new response sends them its answers and a link to open it, with sensitive answers hidden. Replying goes to the respondent.
• Notify in Geiger Flow: puts a notification in the bell at the top of Forms for the form's creator and everyone with a role in the project.
• Weekly report: the people who get the form's weekly digest. See Analytics.

Add follow-up schedules a later email to each respondent, with Send after (hours) (24 to start with), a Subject and a Body. Forms sends follow-ups once a day, so each goes out on the first daily run after its delay. It's sent once per response, only while the form is published and never for responses marked Spam.

Settings → Access & Sharing starts with Who can respond:

• Anyone with the link (the default): no sign-in.
• Password: respondents enter a shared password. Type at least 4 characters and choose Set password (or Change), then Save changes. Remove clears it.
• Signed-in users: respondents sign in with their Geiger account.
• Organisation domain: only people signed in with an email on the Allowed email domain, like company.com.
• Signed links only: only personal signed links made under Share & Send work. See Publishing and sharing.

One response per person asks respondents to sign in, then accepts one response from each account. Someone who has already responded sees "You've already responded to this form."

The rest of Settings → Access & Sharing covers spam and privacy for one form:

• Honeypot field (on to start with): a field people can't see but bots fill in. Forms quietly discards those responses.
• CAPTCHA challenge (off to start with): respondents pass a check before submitting. It needs captcha to be set up for your deployment.
• Rate limit: the most submissions per hour from one network, 20 to start with.
• Anonymous responses: doesn't store the respondent's IP hash, browser details or signed-in account.
• Delete responses after: responses older than this many days are erased automatically. Leave it empty to keep them.

Team access records who you've shared the form with, as Can view, Can edit or Admin. It's a record only: what each person can do comes from their role. The Security and compliance guide covers spam, retention and roles across the project.

Settings → Security & Compliance counts the form's sensitive fields and recent access events, and shows its HIPAA readiness score.

• Sensitive fields lists the fields marked as sensitive in the builder. Their answers are encrypted before they're stored, masked in the Response Inbox and shown only when a teammate reveals them. If encryption isn't set up for your deployment, a warning says so, and sensitive answers are stored unencrypted.
• HIPAA readiness is a checklist of seven safeguards: sensitive fields marked, encryption set up, restricted access, a retention period, no answers in plain-text alerts, the access log and a Business Associate Agreement with your providers. Forms provides the controls, and compliance also depends on your own agreements and processes.
• Access log lists the latest 25 times someone viewed, revealed, exported, printed or edited a response to this form, with who it was and which field.