Receive the right attachment with the right enquiry.
Sometimes a recipient needs a document or image to assess an enquiry. ImbaHub can develop a focused attachment workflow with controlled transfer, storage and access. A file picker alone is not delivery. This capability is scoped separately; it does not mean all existing Imba Forms workflows already support uploads.
- Selected
The file is in the visitor's form.
- Received
The server has checked and associated it.
- Accessible
The intended recipient can download the right test evidence.
A displayed filename is not proof of attachment receipt.
The text enquiry arrives but its file is missing. Is the whole route verified?
No. Trace transfer, relationship and downloading separately, and use a truthful confirmation.
Request only files the recipient actually needs
Start with the next assessment decision and whether a file is needed before initial contact. Define permitted formats, counts and size limits around the need and delivery environment. Explain what customers should not submit through this route.
Fictional example: a sign supplier needs a simple sketch for initial assessment. The enquiry may accept a limited format and offer contact when the evidence does not fit. This does not assume confidential drawings or sensitive personal information belong in an ordinary open contact route.
Check the file after browser selection
File-picker format hints help visitors but do not replace receiving validation. Scope server checks, permitted types, size, names and treatment of suspicious or unassessed content. A filename alone does not establish format.
Storage and downloading need an access model. A private attachment must not become a public resource merely because it is easier to link. Assess scanning and quarantine explicitly around the solution and risk, without universal security guarantees.
| Element | Decision before development | Acceptance exercise |
|---|---|---|
| Need | What evidence helps initial assessment? | Visitor understands why it is requested |
| Limits | Formats, count and size | Allowed file succeeds; exception gets useful help |
| Relationship | Which enquiry owns the file? | Attachment follows the right test case |
| Access | Who may read it and how? | Intended recipient can fetch; another is denied |
| Lifecycle | Who removes files and follows up? | Agreed cleanup and failure ownership documented |
Handle interruptions without false delivery confirmation
Distinguish selected file, upload in progress and received attachment. If transfer breaks, visitors need to understand whether to retry. A recorded text enquiry with a missing attachment must not be confirmed as complete evidence.
Agree how retries remain connected to the right case and how abandoned uploads are handled. If recipients receive a link instead of an email attachment, test its permission and lifetime against the actual recipient workflow.
Hand over a tested route from selection to recipient
An initial delivery can cover one form, limited formats, storage and one receiving channel. External case systems, multiple attachments and especially sensitive material require separate assessment. We propose scope and price after reviewing evidence and operations.
Handover describes file rules, access, storage, cleanup and failures. Use harmless synthetic files to test mobile, keyboard, boundaries and final downloading. Content production does not require sending actual customer files.
Sources and further reading
Questions, answered
Is the accept attribute enough to protect uploads?
No. It guides file selection, but does not replace receiving validation and access control.
Must the file become an email attachment?
No. A controlled download route may fit better. Test it with the intended recipient and agreed lifetime.