Storage and Uploads
How remoteEaze uploads, validates, protects, and serves stored files.
Last updated
remoteEaze treats uploaded files as controlled records with lifecycle state, not just attachments. This supports traceability, safe access, and controlled deletion.
Upload lifecycle
The normal flow is:
- Start upload.
- Receive a secure upload URL.
- Upload file directly to storage.
- Complete upload.
- Run validation checks.
- Make the file available for download when ready.
File policy enforcement
Upload policy is enforced by object class, including:
- allowed content types
- allowed file extensions
- size limits
Unsupported files are rejected before they can be treated as trusted records.
Completion and integrity checks
On completion, the system verifies that the file exists in storage and checks integrity metadata when available.
If checksum verification fails, the upload is rejected and the invalid file is removed.
Download behavior
Downloads use generated, time-limited links with access checks. Only files that reached the ready state are downloadable.
Retention, legal hold, and deletion
Stored files carry retention metadata. Deletion is conservative:
- legal hold blocks deletion
- the record is soft-deleted for traceability
- storage cleanup handles leftover cases where direct removal fails
Replacement and history
The platform supports replacement/supersession relationships so teams can replace documents without losing historical reference.