Overview

Each form in Forms has a submissions list and an analytics view. Before publishing, you also choose where submissions go, so every response can create a record automatically.

Who can do this

  • Required access: an access level that includes Forms - Standard Access or Forms - Full Access.
  • Default access levels that include it: Team Member, Accountant, and System Administrator.
  • Owners and admins: always allowed. Workspace owners and admins are not limited by access levels.
  • Personal accounts: Not available. This is a work feature, so it is hidden in personal (family) spaces.

Owners and admins review and change access levels in Settings → Administration → Members → Access levels.

Choose where submissions go

In the form's target settings, pick a destination module: Contacts, Tasks, Tickets, Deals, Events, or Entities (shown with your workspace's configured name, often Clients). Each submission then creates a new record there. You can also target a custom collection instead. Map form fields to target fields in the field-mapping panel - a form cannot be published until its required target fields are mapped.

File Upload and Website fields can additionally save their submitted file or link into a document folder. Choose a specific folder, or have Scrambl file it under the record the submission creates.

Review submissions

  1. Open the form's Submissions view. Each row shows the submitter, a preview of the first answers, a status (Pending, Processed, or Failed), and when it arrived.
  2. Click a row to open the detail panel: responses grouped by section, downloadable file attachments, the created record, and submission info such as browser and referrer.
  3. Use search, bulk select, and delete to keep the list clean.
  4. Export responses as Excel, CSV, or JSON, optionally including metadata and empty fields.

Analytics

MetricWhat it shows
Total submissionsAll-time response count.
This weekResponses this week with a week-over-week trend.
Avg. Per DayDaily average over the last 30 days.
Processing rateShare of submissions successfully processed into records.

Below the cards you get a submissions-over-time chart for the last 30 days, a status breakdown, completion rates for your most-answered fields, and the latest responses.

Best practice: Watch the Failed status. A failed submission usually means a mapping problem on the target record - fix the mapping and the pattern stops.


Troubleshooting

IssueWhat to check
Submissions are not creating records.Confirm the form has a target module or collection and required target fields are mapped.
Uploaded files are hard to find.Set a document destination on the file field so uploads land in a predictable folder.

Next steps

  • Build a new form or refine fields in the builder article.