Skip to content
← All documentation

Dashier documentation

File uploads: images and documents

Understand the current image/file field flow and constraints before attaching files to records.

Dashier includes image and file fields so a record can refer to an uploaded asset, such as a profile image or document. The current repository configures an S3-compatible Cloudflare R2 client, organizes object keys under organization and project identifiers, and applies a 500 KB upload cap. Confirm the deployed environment has the required R2 settings before relying on uploads.

Add an image or document field

Create an image or file field and decide whether it is required. Give each field a clear purpose so an operator can distinguish a profile image from an invoice or membership form.

Upload and verify

Use the generated record form to upload an asset, then check the saved value and open it through the application. Dashier’s file route checks membership before serving objects, but the public base URL and bucket settings still affect a deployment. Test both an authorized account and an account without project membership.

Treat uploads as untrusted input

Accept only the file types your workflow needs. Do not upload secrets or sensitive documents until data handling, retention, access, and deployment policies are reviewed. Avoid placing user-controlled file links in trusted HTML, and keep an independent source-of-record copy when retention requires it.

The repository documents a 500 KB per-upload cap. It does not claim malware scanning, a retention schedule, encryption configuration, geographic location, or document processing. For deployment questions, contact support@dashier.app.