Attachments in exports

Links in the data

A photo, recording, signature, file or audit answer is exported as a link to the file on your server. The link opens the file for a signed-in member of your organisation who may see that workspace, and for nobody else; a script can open it with an API token. A photo shows and a recording plays in the browser; anything a browser could run is downloaded instead, never opened as a page.

A file answer the workspace's Privacy page withholds is not served to someone without identity access.

All of an export's attachments

The Data Exporter lists an export's attachments by submission and offers them as one attachments zip: a folder per submission, and a manifest.csv with each file's SHA-256, so you can check every file. The zip holds exactly the export's subset of submissions. One submission's attachments can also be downloaded from its page.

Each file's SHA-256 is also recorded on the server when the submission arrives, so a file can always be checked against what the phone sent.

On your computer

Joripo Desktop downloads attachments with the data, checks each against its SHA-256, puts them in a media folder, and writes media\<file> into the CSV cells instead of a link.