Skip to main content
Flex Forms settings live in three places. Pick the one that matches who changes it and how often it changes.

Decision tree

1

Use Global Settings when admins should change it in Studio

Open Global Settings from the Flex Forms left rail (gear icon). Best for:
  • License — Public API key (pk_forms_…)
  • Appearance — Site name, Studio theme, admin language
  • Mail — Logo for submission alert emails
  • Security — Require encryption on all forms
  • Public URLs — Custom fill path prefix
  • Insights — Redis mode, key prefix, cache TTL
Third-party API keys (Mailchimp, Mapbox, reCAPTCHA, etc.) live under Integrations in the left rail — not Global Settings.Full tab reference: Global Settings.
2

Use config / .env for deploy-time and infrastructure

Publish optional config or set env vars when values should not be edited in Studio — disks, quotas, strict permissions, Insights Redis connection, upload authorization callbacks.Every key is documented in Config & env.
3

Use FilamentFlexFormsPlugin for panel-specific PHP

Register fluent options in your panel provider when each Filament panel needs different navigation, branding, or permission overrides:
Plugin methods win over config/env for navigation and Studio rail branding. See Admin customization and Studio permissions.

Quick reference

Env vars are ideal for per-environment differences (staging vs production disks). Global Settings are ideal for tenant admins who should not touch .env.

Publish tags

Run only what you need: Examples:
Localization workflow: Localization & RTL.
Publishing config is optional — every key has defaults and env overrides. Publish when you need PHP callbacks (e.g. uploads.authorize) or non-env overrides.
Last modified on September 7, 2026