The submissions viewer lives at /view/:uuid. It shows the form record, the current submission count, and the controls used to verify access before a download can be generated.
Access checks
The route checks ownership or viewer grants before showing protected actions. The UI can accept QR-based credentials or pasted Access Key JSON, depending on the workflow you prefer.
Exporting data
When the form is verified, the viewer starts an export job through the queue-driven download pipeline. The status updates asynchronously until the package is ready.
What the viewer shows
The page is also used to inspect encrypted submission history and to open the download controls once the job has completed.
/api/download/auth-startvalidates credentials and queues an export./api/download/status/:jobIdis used to poll progress./api/download/:tokenserves the final archive once, then consumes the token.