Submission notifications, review, and exports

Documentation / Media, forms, and integrations

Native form submissions are stored independently of notification emails. A successful response means the submission was saved; it does not prove that an email reached every recipient.

Set notification recipients

Open the form's settings and enter Notification Emails, one recipient per line. Save the settings, then submit a test response from the public page. Notification sending depends on the configured mail service and runs without blocking the successful submission response.

If no message arrives, inspect stored submissions first. Check recipient spelling and mail filtering before asking an administrator to investigate delivery configuration. Avoid treating the mailbox as the only record of incoming responses.

Review responses

Open the form's submissions tab. It shows total and unread counts and lets you expand individual records. Expanding a record marks it read. You can also select records and mark them read or unread.

The admin provides deletion actions for individual, selected, or all submissions. Deletion changes stored response data, not the public form definition. Review retention requirements before removing records, and keep only exports that have a justified purpose.

Export and verify

Use the CSV or JSON export action for the selected form. Open the downloaded file and check representative fields, dates, and non-English text before using it elsewhere. These exports contain submitted data and may include personal information; store and share them accordingly.

The verified review screen does not establish a general CRM, email-delivery audit, or automatic retention policy. External provider forms have separate submission and export tools unless specifically integrated.

For end-to-end testing, compare one test response in the page confirmation, admin record, notification, and export. See Legal and privacy with LEX8 for privacy responsibilities.