Routes
/dashboard/api/board/envelopes/[id]/audit-pdf/api/board/envelopes/[id]/finalized-urlFlow 7
Proof Vault
After signing, BrieflyGo keeps the final PDF and the audit evidence together so the user can prove what happened.
3
Routes
5
Buttons
2
Screenshots
3
Watch-outs
ELI10
After signing, BrieflyGo keeps the final PDF and the audit evidence together so the user can prove what happened.
W5
Who: the sender or account owner.
What: signed PDF, audit PDF, tags, archive, proof sharing link, download all.
When: after a package is completed.
Where: dashboard proof vault and status room.
Why: proof is a paid SaaS value, not just a one-time download.
Flow graph
Screens and paths in this flow
Each step connects to its screen manual. Follow the nodes left-to-right to trace the document journey.
4nodes
Step 1DashboardActive documents, proof vault, templates, and archive.
Step 2Audit PDFGenerates tamper-evident audit trail PDF via API.
Proof Vault3 routes · 5 actions
Dashboard→Audit PDF→Final PDF
Important buttons
Watch-outs
Proof sharing links should be protected by default.
Archive should hide items from active work without deleting proof.
Search and tags make the vault useful over months, not just one session.