Short walkthroughs that turn the platform into your operations team: automated pipelines, instant follow-ups, AI-handled admin. One video, one less thing to do manually.
When to void vs delete a form submission, how to do each from the UI, what gets removed, and the optional PDF cleanup step.
Two separate actions control the lifecycle of a form submission: Void and Delete. They do different things, and picking the right one avoids accidentally wiping data you still need.
There are two places you can delete from:
If the submission had an auto-archived PDF rendered into your Documents library, the confirmation prompt includes a checkbox: Also delete the archived PDF.
The checkbox only appears if an archived PDF exists for that submission. If no PDF was ever rendered, you won't see it.
The form template is not affected. You can still send the same form to other recipients.
Only users with the forms:delete permission see the Delete button and trash icon. By default this is granted to Owners and Admins. To grant it to a custom role, go to https://app.trustpager.com/settings/permissions and enable Delete form submissions for that role.
The TrustPager MCP exposes a delete_form_submission tool that accepts the submission id and an optional delete_archived_pdf boolean (defaults to false). Agents with the appropriate API key and forms:delete scope can call this directly to clean up submissions programmatically — for example, as part of an automated data-retention workflow.
Talk to Evie right now, or book a real human for a deeper walkthrough. Whichever feels right.
Hear her in 10 seconds.

60 minutes with a real human · Google Meet · Free.