Private files and generated document storage
Overview
Section titled “Overview”CRM attachment metadata is stored in the database while attachment bytes live in a private durable file store. Objects use generated opaque keys rather than user-supplied paths. Background import sources occupy a separate namespace in the same private storage root. Commercial document finalization captures document snapshots and generated artifacts so later catalog or template edits do not silently alter retained documents.
Purpose
Section titled “Purpose”Use this article when planning storage, investigating missing files or defining the scope of a recovery point.
Prerequisites
Section titled “Prerequisites”-
Administrator access to System Health and the package storage configuration.
-
A known attachment or document reference; do not distribute the underlying private filesystem path.
Procedure
Section titled “Procedure”-
Check System Health for private storage availability, writability and remaining capacity. Confirm the API and worker use the intended durable store.
-
Open the parent record and its Attachments tab. Verify that the current user can access both the record and the attachment action.
-
Review the scan state before requesting a download. A listed filename is not proof that the bytes are released for download.
-
For an import, inspect Import Jobs and its source/progress history rather than treating the source file as an ordinary customer attachment.
-
For a finalized sales document, use the document PDF action and selected revision. Compare the document identity and revision when investigating a historical rendering difference.
Expected result
Section titled “Expected result”The investigation separates metadata, private bytes, scan evidence and stored commercial output.
Important notes
Section titled “Important notes”-
Supported attachment types are PDF, DOCX, XLSX, PNG, JPG/JPEG, TXT and CSV, subject to content validation. Upload limits default to 10 MiB with a hard cap of 50 MiB; the installed proxy may impose a lower effective limit.
-
Removing an attachment from a record does not necessarily purge its bytes immediately. Retention cleanup is a worker operation.
-
Import sources and completed import histories have no general automatic retention cleanup in the reviewed implementation.
-
Protect the entire private store as part of coordinated recovery. Do not expose its directory through the web gateway.
Troubleshooting
Section titled “Troubleshooting”-
File metadata appears but download fails: inspect scan status and parent permissions, then storage integrity.
-
Disk usage grows after imports: review retained import sources and establish an approved retention process rather than deleting files ad hoc.
Related articles
Section titled “Related articles”Search the guides or talk to the ZBIX team.
Software products, application engineering and IT services from Zbix Technologies.
Visit our company website ↗