File uploads: images and documents

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

Add an image or document field

Create an image or file field in a source. Decide whether the value is required and explain what the file represents. Keep unrelated assets in separate fields so operators can tell a profile image from an invoice or membership form.

Upload and verify

Use the generated record form to upload an image/document, then verify the resulting record value and open the file through the application. Dashier’s file route checks membership before serving objects; the configured public base URL and storage bucket settings still matter, so do not assume that every deployment has identical bucket exposure. Test access from an account without project membership as well as from an authorized account.

Treat uploads as untrusted input

Only accept file types your workflow actually needs. Do not upload secrets or sensitive documents unless the data-handling, retention, access, and deployment policies have been reviewed. Avoid putting user-controlled file links into trusted HTML. Keep the original in the appropriate source-of-record system if it must be retained independently of Dashier.

The documented per-upload cap in the repository is 500 KB. No malware-scanning, retention schedule, encryption configuration, geographic location, or document-processing service is claimed on this page. For questions about a deployment, contact support@dashier.app.