Documents · local product-use draft
Understand document versions, quarantine and retained storage.
Keep a current document pointer without losing earlier evidence, integrity facts or current permission checks.
Prepared 13 November 2026 from the implemented local workflow. Local product-use draft; independent operational and legal review remains open.
Metadata and bytes have different states
A document record can exist before any verified upload. A reserved version declares a file; only completed validation records actual bytes and integrity. A filename or metadata row alone does not prove safe content.
Quarantine is a real access boundary
Uploaded bytes stay blocked until an approved provider returns a clean result. Unknown, failed or unapproved scanner decisions never become safe. The local main registry has no approved scanner.
Current authority applies again
A previously visible document or attachment link does not preserve download rights after revocation or reassignment. Delivery rechecks current scope and byte integrity. Notifications and support never bypass that boundary.
Archiving is not deletion
Retained versions and reservations still count towards storage. Holds protect evidence. A disposal request records a reason for review; it is not destructive permission or a verified legal retention period.
Product context and sources
This guide describes the current local Fleet feature and its visible record/permission boundaries. It does not define a legal retention period, statutory check schedule or competent release policy.
Open the related feature explanation