Submissions

A submission is one set of answers sent through a form, from its landing page, an embedded form, or the form's endpoint. Each accepted submission is attached to a profile, found by email address or created on the spot. The same person can submit a form more than once; each time is a new submission.

What Happens on Submit

A refused submission is not stored. The visitor sees the errors next to the fields concerned, or "Form submissions are closed" outside the submission window.

Matching the Profile

The Email address answer is looked up across every email address held on profiles.

Case Result
A profile has this email The answers of mapped fields are written to that profile, following each mapping's Overwrite existing value setting.
No profile has this email A new profile is created from the mapped answers and given the first state of the institution's lifecycle.

On a new profile, the source is recorded as a form submission, with the form's Default source category when one is set. An existing profile keeps its original source.

Mapping rules, explained in Form Builder:

  • Only mapped fields reach the profile. Every answer is kept on the submission.
  • An empty answer never clears a profile field.
  • The login email of a staff member, administrator, or lecturer is never changed by a form.

Files sent through a File upload field are also added to the profile's files.

The landing page shows the institution's privacy policy, with a consent checkbox unless the policy is set to show without one. It also shows the marketing consent, unless Show marketing consent on form is off on the Details tab. A policy that is sent must be accepted, or the submission is refused. Accepted policies are recorded on the profile with the submission as their source.

After a Submission

Once stored, a submission:

  • Adds "Name submitted to the Form form" to the profile's activity.
  • Creates an inbox card for staff. See Automation & Webhooks.
  • Starts the form's workflows and any webhook subscribed to form submissions.
  • Updates the form's submission count and rate.

A signed-in staff member can fill in a form for someone else: the submission goes to the profile of the email entered, not to the staff member, and the disposable email check does not apply.

Submissions Tab

The Submissions tab starts with the form's funnel: Views and Submissions, with the submission rate (submissions divided by total views) to one decimal.

Below it, the table lists one row per submission, newest first, 50 per page:

Column Shows
The form's fields One column per field. First name, Last name, and Email address are shown by default.
Profile fields The submitter's profile fields, hidden until picked. They cannot be sorted.
Submitted at When the submission was made.

Use Columns to show or hide columns. Your choice is remembered in your browser for that form. Each row has View profile and Delete submission.

Note: If your role has a data access scope, the table and the export only include submissions from profiles inside it, and the count says "available for your access scope".

Exporting

With forms.submissions_export_access, Export submissions exports the visible columns as CSV or Excel. The export runs in the background and offers a download link when it is ready.

Deleting a Submission

Delete submission removes the submission. The profile and anything already written to it stay, and this cannot be undone. When it was the person's last submission to the form, the form's inbox card for them is removed too.

When Profiles Are Deleted

When a profile is deleted, or scrubbed for data protection, all its submissions to every form are deleted with it.