Archiving vs deleting Submissions
Archive is the standard customer-facing path for Submissions you no longer want in the active list. Hard delete is essentially staff-only — and often blocked entirely once a Submission has used any Data Credits. Archive preserves data; delete is permanent and rare.
In short: Archive when you want a Submission out of the active list but kept on file. Delete is staff-only and frequently blocked — when in doubt, archive.
Archive: the standard path
Archiving a Submission:
- Hides it from the default list views.
- Preserves all data — answers, attached records, documents, integration responses, Notes, Comments, Tags.
- Keeps it filterable — toggle the archived filter to see archived Submissions.
- Is reversible — unarchive any time (with one caveat below).
Use archive when:
- A lead didn’t convert and isn’t worth working further
- A test Submission was created and you want it out of the way
- A duplicate came in and you’ve consolidated to the canonical one
- Auto-archive on a Status (e.g. Lost) fires automatically
Why “delete” usually isn’t available
Submissions don’t expose a customer-facing delete action through the normal UI. The reason: once a Submission has been enriched with Data Credits (property data pulled, dec page retrieved, MVR fetched), its data is tied to billing records that can’t be silently removed. SALT blocks the delete to keep that trail consistent.
If you genuinely need a Submission gone — a privacy request, a test record, a wholly mistaken submission — that path runs through SALT staff (contact support).
Auto-archive (the trap to know)
Some Statuses can be configured to auto-archive Submissions that move into them — typically Lost, abandoned, or stale-lead Statuses. See Customizing Statuses for the configuration.
A Submission auto-archived by Status can’t be unarchived directly. Move it to a different Status first, then unarchive. The auto-archive Status will re-archive it if you move it back.
Archive or unarchive a Submission
-
1
Open the Submission.
-
2
Use the archive action (if active) or the unarchive action (if archived).
-
3
The change saves immediately.
If unarchive seems to fail, check whether the Submission’s current Status has auto-archive turned on — that’s the most common cause.
What’s preserved when archived
Everything:
- All answers across all questions
- All attached Insureds, drivers, vehicles, properties
- Documents (still downloadable)
- Notes and Comments
- Tags
- Integration responses
- Status history
Archive is non-destructive. The only thing that changes is visibility in the default list.
Bulk archive
From the list view, select multiple Submissions and bulk-archive (where supported). Useful for cleaning up a batch of stale leads at once.
Common questions
I clicked delete and got an error. What happened? Likely the Submission has had Data Credits used against it, which prevents hard delete. Archive instead.
How do I find archived Submissions later? Toggle the archived filter on the Submissions list. Or save a Saved View that includes archived state.
Will archiving cancel a pending integration sync? Synchronous integrations have already fired by the time you can archive. Pending async work (e.g. dec page retrieval) may continue and complete on the archived record.
Can I archive and still get notifications about the Submission? Notifications follow the Submission, not its archive state. If the Submission becomes active again (via consumer activity or unarchive), notifications continue to fire.