My Forms

The SG-Admin My Forms module — form definitions, submission records, workflow producer.

The My Forms module in the admin is the per-site surface for form definitions and submission records. Operators design forms here, configure capture and notification rules, and review every submission as records. Submissions feed the Form Submission Workflow. This page is the Reference definition.

What is this for?

Read this page when you want the structural definition of the My Forms module — the form-definition model, the submission record, and how the module fits into the broader form workflow.

Good use cases

• You are scoping form-driven capture for a site.
• You are explaining to a stakeholder how SGEN handles form submissions.
• You hit a "where do form submissions land?" question.

What NOT to use this for

• Step-by-step procedures — open the relevant Guide.
• At-capture filtering — open Blacklist.
• Cross-product flow — open Form Submission Workflow Reference.

How this connects to other features

• SG-Admin Overview — parent surface.
• Blacklist — at-capture filter that intercepts unwanted submissions.
• Form Submission Workflow — cross-product workflow.

Where to find it

Open SG-Admin for the active site. My Forms is in the sidebar under the content group. The form builder and submissions view are both sub-surfaces. Editors and Admins can build forms and review submissions; Authors may have read-only access depending on site configuration.

Definition

The My Forms module administers form definitions and submission records. A form definition carries the form identity, the field list (per-field type, label, validation), capture configuration (notifications, integrations, confirmation rules), and the styled rendering hooks SG-Builder uses on the public site. A submission record is the persisted output when a visitor completes the form.

Purpose

Define the My Forms module as a Reference layer.

Scope

Covers form definition, submission record, and producer relationship to the Form Submission Workflow. Does not cover at-capture filtering (Blacklist) or per-step procedures (Guides).

Form definition

Identity

Name, slug, internal ID.

Field list

Per-field: type (text, email, select, checkbox, file upload, etc.), label, required flag, validation rules, default value.

Capture configuration

Notification recipients, confirmation email setup, integration push targets, success message.

Rendering hooks

How the form renders on the public site (typically inserted via a SG-Builder form block referencing this definition).

Submission record

Each submission carries form identity, field values, visitor metadata (timestamp, IP, source page), and notification + integration push outcomes. Per the Form Submission Workflow, the record landing is Handoff 1 of the workflow.

Constraints and boundaries

My Forms is a Reference area for form definitions and submissions.

Do not use for: at-capture filtering (Blacklist), cross-product flow (Form Submission Workflow Reference), per-step procedures (Guides).

Public boundary

This page is intentionally public-safe.

Examples

Example 1 — Operator builds a contact form

Operator clicks Add Form, configures fields (name, email, message), sets notification recipients, sets confirmation email. Drops the form on a contact page via SG-Builder form block referencing the new form.

Example 2 — Operator scans submissions for a campaign

Operator switches to the Submissions tab, filters by date range matching the campaign, exports for follow-up.

Example 3 — Operator tunes notification routing

Operator updates the contact form's notification config to add a second recipient. Future submissions notify both recipients.

Documentation guidance

Use this page as the structural definition for the My Forms module.

Reading order

Open this page when scoping form-driven capture. Pair with Form Submission Workflow Reference for the cross-product flow.

Related reading

• SG-Admin Overview — parent surface.
• Blacklist — at-capture filter.
• Form Submission Workflow — cross-product workflow.

Vocabulary cross-reference

• Form definition is the per-form configuration record.
• Submission record is the persisted output of a visitor's completed form.
• Capture configuration is the per-form notification + integration setup.
• Rendering hook is how the form surfaces on the public site (via SG-Builder block).

Maintenance discipline

When the My Forms module changes across releases (new field type, new capture option, new submission field), update this Reference.

Related reading