Skip to content

Files, documents and communication

Toolora associates files and communication with defined records and audiences. Application attachments use Storage and authorized retrieval. The company-mail workspace reads an Estate-owned archive projection. Archive ownership and customer access are separate from a decision to publish a document or message.

The Storage reference traces bucket/path identity, application metadata, browser policies and privileged retrieval. It separates customer, worker and UE file audiences, operation-specific URL lifetimes and upload/link failure boundaries. Publication withdrawal can stop future issuance without recalling an existing URL or downloaded copy. Information handling retains its own lifecycle rules.

The conversation-audience concept compares office, customer, worker and UE histories, resource admission, participant seats and effective assignment. It explains separate SQL/message/attachment predicates, retry keys, read receipts and inbound reopening. Sharing an attachment there does not automatically publish it as a customer-visible project image. Staff publication remains a separate action. Publication and record ownership explains the distinction between internal collaboration, portal access and customer-facing material.

Estate preserves RFC822 originals and attachment bytes. Toolora keeps a bounded, searchable projection and shows missing coverage or unavailable originals. Reading requires mailbox policy and current reader access. The mail integration owns the source contract; Toolora’s own application-email delivery records remain in their quote, invoice or project workflow.

Mail originals and attachment evidence traces source occurrences, verified copies, current readers and incomplete byte coverage.

A document-inbox candidate represents one attachment occurrence in a preserved source version. Interpretation supplies proposed classification, fields and source evidence. Human confirmation establishes business routing. A delivery note is a supplier claim; a material receipt records human-confirmed received quantities. AI proposals do not by themselves approve these business facts.

Document intake follows optional interpretation, manual classification, version/hash checks and explicit domain routing.