Attachments are the quiet workhorses of enterprise software. A signed contract lives on a sales order; a compliance certificate hangs off a supplier record. It is enormously useful, and, left unmanaged, it is exactly where sensitive documents pile up with no oversight at all.
The hidden cost of unstructured attachments
When any user can attach any file to any record, you inherit three problems at once: storage that balloons unpredictably, documents that duplicate and drift, and sensitive files sitting wherever someone happened to drop them. None of these show up until an audit, or an incident.
Design for structure from the start
The fix is not to ban attachments; it is to give them rules. Define which document types belong on which records, enforce naming and metadata, and route files to managed storage rather than the database itself. The user still clicks one button, the structure happens underneath.
A pattern that scales
- Store files in managed object storage; keep only references in the ERP.
- Attach a required document type and metadata to every upload.
- Scan on upload and enforce size and format limits.
- Apply access rules that follow the record, not the folder.
Security follows the record
The elegant part of doing this well is that permissions can inherit from the business object. If a user can see the invoice, they can see its attachments, and if they cannot, the files are invisible too. Access control stops being a separate, forgotten system.
“The goal is an attachment experience so simple that nobody is tempted to route around it. Security that adds friction is security that gets bypassed.”
