Workspace settings

To change Forms' settings for a project, choose Templates & Admin → Workspace Settings in the Forms sidebar. The settings belong to the open project, and only the Owner and Admin roles can change them. For everyone else the controls are disabled, and the save button explains "Only workspace admins can change settings."

Nothing saves until you choose Save settings. While you have changes, Forms shows "You have unsaved changes." and a Discard button that puts the saved settings back. Once everything is saved, the button reads Saved.

Most settings on this screen are defaults for new forms. To change one form, use its own settings instead. See Form settings.

Workspace defaults are copied into a form when it's created, and only then. They apply to forms you create with New form from a blank form or a built-in template, and to forms made with Use in the template gallery.

They don't apply to duplicates, to forms made from Your templates or to forms that already exist. Changing a default later never changes an existing form.

A default only fills in what the new form doesn't set itself. A built-in template that has its own accent color, logo or retention period keeps it.

• Default form language: the language of the built-in text on new forms, such as buttons and error messages. Choose English (the default), Español, Français, Deutsch, Português, हिन्दी (Hindi) or العربية (Arabic).
• Starting status: Draft (the default) or Published. Published only applies to forms created with New form in All Forms, and only when your role can publish forms. Other new forms start as drafts.
• Require CAPTCHA: turns on the captcha challenge for new forms.
• Anonymous by default: new forms don't store the respondent's IP hash, browser details or signed-in account.
• Delete responses after (days): how long new forms keep responses before they're deleted. Leave it empty to keep responses until someone deletes them.

Each form can change these afterward in its own settings. The Security and compliance guide covers captcha and retention.

The Branding card sets the look new forms start with.

• Accent colour: pick a color, or type a 6-digit hex value like #6366f1. Forms won't save any other format. Clear removes it.
• Logo URL: the address of an image to show as new forms' logo.
• Hide Geiger branding: removes the "Powered by Geiger Forms" footer from new forms.

To change the look of a form that already exists, open its settings and go to Themes & Colors or Branding.

Three more cards on Workspace Settings link to tools covered in other guides.

• Folders counts the project's folders. Manage folders opens the Folders screen, covered in All forms.
• API keys creates and revokes the keys that other tools use to reach the project's forms through the REST API. Only the Owner and Admin roles can manage them. See Integrations and API.
• Right to erasure (GDPR) permanently deletes everything a respondent submitted with one email address, after you confirm. See Security and compliance.

The Configuration card shows which server services are set up for your deployment of Forms. It shows only whether each one is set up, never its value, and its badge reads All configured or the number not configured. When a service isn't set up, the features that need it don't work, and their settings in a form show a warning that starts "Not configured on this deployment."

• Server database access: without it, public forms, submissions, uploads and webhooks are unavailable.
• Email (Resend): without it, no email is sent, from confirmations and alerts to approvals, resume links, invitations, follow-ups and reports.
• Stripe Checkout: without it, respondents aren't sent to checkout, so payments aren't collected.
• Stripe webhooks: without it, payments are never confirmed, so paid responses stay Awaiting payment.
• Captcha (Cloudflare Turnstile): without it, captcha challenges aren't shown or checked.
• Field encryption: without it, sensitive answers are stored unencrypted, and answers encrypted earlier can't be revealed.
• Link signing: without it, signed, expiring respondent links can't be created or checked.
• Scheduled jobs: without it, retention clean-up, reminders, follow-up emails and weekly reports don't run.

Whoever runs your deployment sets these up.