Configure upload controls
Set maximum file size, accepted extensions and allowed file count. Tell visitors those limits before they choose a file. Test oversized, disallowed and multiple files on the public page.
An uploaded answer may be a structured attachment with an ID, filename, size and content type. Preserve that structure when consuming the API; converting it to a generic string can produce an unusable [object Object] value.
Retrieve completed attachments
Open the entry in the authenticated Submissions workspace and use its file link. The Umbraco adapter checks the current user's access to the submission before returning private content. Sharing a file ID or its private endpoint URL does not make the attachment publicly accessible.
PDF output can be opened through the approved PDF response path; other file types retain their download handling. Check filenames and content types when adding a custom integration.
Storage connections
Configure any external/cloud storage through the installation's connection settings and map it in the form's Data & storage settings. Keep account keys and connection strings on the server. Test that the file reaches the selected provider and remains downloadable with the intended permissions.
Retention must cover both submission records and their files. Decide how archival, removal and backups apply to the configured provider.
Use the PDF example for a complete document-to-submission flow. For a missing link or 401/403 response, follow Troubleshooting.