/fw/submissions provides a paginated, searchable list of all form submissions for the active organization, with filters by form, status, and date range, and support for CSV/JSON export and bulk PDF export.
Overview
The Submissions list displays form submissions in a paginated data table (50 per page). Each row shows: form name (link to detail), submitted by, submitted at, status badge, and action buttons (export as PDF, View). Users can select non-draft submissions for bulk PDF export. Submission data may contain PHI — access is controlled byfw.submissions.view.
Who it’s for
Requiresfw.submissions.view permission (FW_PERMISSIONS.SUBMISSIONS_VIEW), enforced by RequirePermission in src/routes/fw.tsx.
Before you start
- You must have the
fw.submissions.viewpermission. - Ensure the organization context is set; submissions are scoped to the active organization.
Finding and exporting submissions
Viewing submissions:- Navigate to
/fw/submissions. - The table loads the first page of submissions (up to 50).
- Use pagination controls at the bottom to navigate pages.
- Form filter — Select a specific form from the dropdown to show only its submissions.
- Status filter — Select a status (
draft,submitted,reviewed,completed,rejected) to filter by lifecycle state. - Date range — Use the date-range popover to filter submissions by submission date.
- Search — Type in the search box to filter by form name or submitter name/email (client-side filter on the current page).
- Select Clear Filters to reset form and date filters.
- Export CSV — Downloads a CSV of submissions matching the current status filter.
- Export JSON — Downloads a JSON file of submissions matching the current status filter.
- Bulk PDF export — Select non-draft submissions using row checkboxes, then select “Export N as PDF” in the bulk action bar.
/fw/submissions/:id.
Single PDF export:
Select the PDF icon on any non-draft submission row. The browser navigates to /fw/submissions/:id?action=pdf, which auto-opens the export dialog.
- Submission status —
draft,submitted,reviewed,completed,rejected. Only non-draft submissions are selectable for export. - Page size — Fixed at 50 submissions per page.
- Search scope — Filters by
form_name,submitter_name, andsubmitter_emailon the current page’s loaded data. - Bulk PDF export — Uses
useBulkSubmissionPdfExport; selection is cleared on successful export. - PHI — Submission data frequently contains PHI. Do not export or share without authorization.
Viewing a submission
The Submission Details page (/fw/submissions/:id) displays the full contents of a single form submission, along with tools for managing its lifecycle, annotations, and supporting documents.
The page includes:
- Submission field values — All form fields with their submitted responses, including file attachments and signature captures.
- AI Summary Card — Shown for non-draft submissions (SME: confirm AI summary scope and PHI handling).
- Status workflow — A dropdown to update the submission status.
- Notes — A textarea to add internal notes visible to staff.
- Signatures — A card listing captured signatures when the form includes signature-type fields.
- Attachments — A drag-and-drop zone for uploading supporting files and a list of existing attachments with download and delete actions.
- PDF export — Download PDF and Export with Letterhead buttons for non-draft submissions; Signed PDF button when signature fields are present.
fw.submissions.view permission. The submission must exist. PDF export requires the submission to have a status other than draft.
Changing status:
- In the Status sidebar card, select a new status from the dropdown.
- The status updates immediately. Timestamps for reviewed and completed events are shown below the dropdown.
- In the Notes card, enter the note text in the textarea.
- Select Add Note. The note is appended to the list with creator and timestamp.
- In the Attachments card, drag a file onto the drop zone or click to select.
- The file uploads and appears in the attachments list.
- Download PDF — Generates a standard PDF export.
-
Export with Letterhead — Opens the
FormSubmissionExportDialogfor branding and formatting options. - Signed PDF — Available when the form has signature fields; generates a PDF with embedded signatures.
-
Submission status lifecycle —
draft→submitted→reviewed→completed(orrejected). Status changes are persisted viauseSubmissionMutation. -
PHI — Form submission data frequently contains PHI. Access is gated by
fw.submissions.view. Notes and attachments should not contain PHI beyond what is necessary. -
Signature capture — Signature-type fields that lack a value and have a capturable status show a “Capture Signature” button powered by
SignatureDialog. -
Attachment storage — Files are stored in the
submission-attachmentsSupabase storage bucket. Download links use signed URLs expiring after 1 hour.
Related
Forms & Workflow
Forms & Workflow core overview.
Governance & parity
This page documents shipped product behavior. It is not medical, legal, or
billing advice. Verify against your organization’s policies and applicable
regulations before using it for clinical, compliance, or billing decisions.
Protected health information (PHI) shown in the product is governed by your
tenant’s access controls and is never exposed in this documentation.
Documentation sources
Documentation sources
- src/routes/fw.tsx
- src/cores/fw/pages/SubmissionsList.tsx
- src/cores/fw/pages/SubmissionDetailPage.tsx
- src/cores/fw/hooks/useSubmissionList.ts
- src/cores/fw/hooks/useSubmissionDetail.ts
- src/cores/fw/hooks/useSubmissionMutation.ts
- src/cores/fw/hooks/useSubmissionExport.ts
- src/cores/fw/hooks/useBulkSubmissionPdfExport.ts
- src/platform/forms/hooks/useFormSubmissionPdf.ts
- src/platform/signatures/SignatureDialog.tsx