Skip to main content
The Forms Settings screen allows administrators to configure module-level settings for the Forms & Workflow core and is available at /fw/settings.

​
Overview

This admin screen loads the organization’s FW module settings from fw_module_settings via useFWModuleSettings and renders them in FWSettingsForm. A guided tour is available via useTour with steps defined in fwSettingsTour. If the current user holds fw.dependencies.view, links to the Dependency Graph (/fw/settings/dependency-graph) and business calendars are shown. A dirty-state tracker (isDirty) controls the save button state. Settings include default form status, custom categories, submission retention, anonymous submission policy, automation retry limits, timeout configuration, worker batch sizes, checkpoint settings, and rate limiting for external forms.

​
Who it’s for

Requires permission: fw.settings.manage (FW_PERMISSIONS.SETTINGS_MANAGE).

​
Before you start

  • Hold fw.settings.manage to access and modify these settings.
  • Changes affect all forms and automations for the current organization.

​
Steps

1

Open Settings

Navigate to /fw/settings.
2

Review current configuration

The form loads the current fw_module_settings row for the organization.
3

Edit settings

Modify the desired fields in FWSettingsForm.
4

Save

Click Save; the settings are persisted to fw_module_settings.
5

Explore dependency graph

If you hold fw.dependencies.view, click the link to open /fw/settings/dependency-graph.

​
Key concepts

  • fw_execution_worker_enabled — master toggle for the automation execution worker.
  • submission_retention_days — how long form submission records are retained.
  • fw_event_schema_validation_mode — controls strictness of event schema validation (off, strict, warn).

Forms & Workflow

Forms & Workflow core overview.

Governance & parity

Documentation coverage and governance.
This page documents shipped product behavior. It is not medical, legal, or billing advice. Verify against your organization’s policies and applicable regulations before using it for clinical, compliance, or billing decisions. Protected health information (PHI) shown in the product is governed by your tenant’s access controls and is never exposed in this documentation.
  • src/routes/fw.tsx
  • src/cores/fw/pages/FWSettingsPage.tsx
  • src/platform/permissions/constants.ts