FormBastion

Inbox & attachments

A considered home for your data.

Review submissions, handle files, export records, and understand retention.

Your inbox is a complete workflow

Open Inbox to review accepted submissions or switch to quarantine. The detail page shows escaped field values, the source and published version, attachments, retention information, and action outcomes. Arbitrary submitted text is displayed as data.

Accepting attachments

Enable attachments in the form’s draft and publish the change. For HTML forms, use enctype="multipart/form-data" and a file input with a field name. Your form’s configured limits and your workspace’s storage allowance both apply.

File input
<label for="attachment">Attach a file</label>
<input id="attachment" type="file" name="attachment">

The default configuration permits up to three files, each no larger than 5 MiB, with a 15 MiB aggregate limit. Supported types are PDF, PNG, JPEG, GIF, WebP, plain text, CSV, and JSON. Both the extension and detected content type are checked; changing the browser’s file picker does not bypass server validation.

Storage and downloads

Files use private application storage with random internal names. Authorized customers obtain a short-lived download link from the submission detail page. The download host does not share your customer session cookie. Download tickets expire after 60 seconds, can be used only once, and are reauthorized when used. Treat them as private.

Attachments are marked unscanned. Type and size validation do not establish that a file is free from malware. Only open files you trust; never execute uploaded content.

Quarantine and release

Submissions held by local protection remain visible in quarantine and do not trigger actions while held. Releasing one checks the workspace allowance, counts the accepted submission, and schedules its configured work. Review its contents before release.

Exports

Export submission data as JSON for structured use or CSV for a spreadsheet. CSV export neutralizes leading spreadsheet formula characters to help keep submitted text from becoming an executable formula. JSON preserves the recorded data structure.

Retention and deletion

Each submission records an expiry based on the applicable plan. Maintenance removes expired submission data and associated files and processing records. Removal occurs when that maintenance job runs, not at a guaranteed exact second.

Deleting a submission removes its stored data and associated attachments. A completed external action cannot be undone by deleting the source record. Export information you need to retain before deleting it or reaching its retention expiry.