Submissions

Submissions are the saved records created when someone interacts with a Formie form.

They can represent a completed submission, a partially saved draft, or a submission that has been marked as spam. Once a submission exists, you can review it in the control panel, organize it with statuses, export its data, relate it to other elements, or render it back into the front end for editing.

Submission States

Formie tracks a few built-in submission states:

• complete submissions have finished the normal submission flow
• incomplete submissions are partially saved, such as save-and-continue drafts or multi-page progress
• spam submissions have been screened and marked as spam

These are system states. They describe what happened during submission processing.

Custom Statuses are different. A status is your team's workflow label on top of the saved submission, such as new, approved, or closed.

Common Ways to Work With Submissions

Organize Them With Statuses

Use Statuses when your team needs labels for review, follow-up, or internal processing after a submission has been saved.

Export Submission Data

Use Reports when you need saved filters, summary counts, charts, on-demand export, or scheduled email delivery.

For a one-off file without saving a report definition, run a report and choose an export format from the report run screen.

Relate Submissions to Other Elements

Use Relations when a submission belongs to another Craft element such as an entry or product, or when you want to look up related submissions later.

Select Submissions From Other Elements

Use Element Field when you want another Craft element to choose and store a reference to a Formie submission.

Edit Submissions in the Control Panel

When you view or edit a submission in the control panel, Formie can honour the same field and page conditions used on the front end.

Set the default under Formie → Settings → Submissions → Control Panel Field Conditions. Override per form under Form → Settings → Submissions — choose Use Formie default to inherit the plugin setting.

Use Show all fields when your team prefers the full layout at all times.

Let Users Edit Saved Submissions

If you need to render an existing submission back into the front end so a user can update it, see Editing Submissions.

Developer Access

If you are working with submissions in templates or custom code:

• use Submission Queries to fetch submissions in Twig or PHP
• use Submission Workflow when you need to hook into submission processing stages or tasks
• use Submission Content when you need the right value format for output, exports, summaries, emails, or integrations
• use Submission for the public properties and methods available on the element itself