Join the LadVen OS testing programRequest a demo
Skip to main content

Disk projections

The projection view gathers accessible files and documents from tasks, chats, CRM, and other work contexts. It is a virtual view of relationships, not a separate physical folder. Open Projections from Disk and Files.

Physical placement and context

Conceptual process guidance; not a UI screenshot or state evidence.

Each row has one of two placement types:

  • Placed in Disk (physical) — the file or document has a Disk space, folder, and path;
  • Available through context (virtual) — it is visible through a linked task, chat, CRM record, or document but has not yet been put in a Disk folder.

Rows also show the primary context, other links, update time, and shared, placed, context-only, or archived badges. Use Open context for the source task, chat, document, company, contact, project, or legal entity, and Reveal placement for the physical folder.

Do not treat a virtual projection as a file copy: placing a document creates a placement record, not another document revision.

Presets and filters

Conceptual process guidance; not a UI screenshot or state evidence.

Presets cover task files, chat files, CRM files, deal documents, shared with me, and physically placed items. Manual filters support file/document target, source (task, chat, CRM, document, deal, appeal, company, client, contact, client project, legal entity, conversation, or message), a specific work object or context scope, any/physical/virtual placement, title search (q), owned by me, shared with me, and archived items.

Filters stay in the link, so a colleague can open the same bounded view. Context-folder summaries are available for tasks, CRM, appeals, companies, clients, projects, and legal entities; chats, documents, conversations, and messages show item rows.

Sharing a projection creates a fixed copy of the current selection. Recheck the contents and recipient permissions before sending the link; later changes in the work context must not unexpectedly expand access.

Context folders and states

Conceptual process guidance; not a UI screenshot or state evidence.

For supported task, CRM, appeal, company, client, contact, client-project, and legal-entity sources, the page can show an aggregate context folder with total, file, and document counts plus ownership, sharing, placement, archive, and governance flags. Open it for the filtered items; the source context opens separately. For chats, documents, conversations, and messages the page remains an item list. Sharing from this view creates a fixed copy, not a live folder, and it does not reveal future items automatically. Recheck the archive and governance flags before sharing a copy.

Modes, pages, and states

Conceptual process guidance; not a UI screenshot or state evidence.

The list supports Compact, Details, and Grid modes. Long lists load in portions with a continuation control, while context folders open separately. Loading, refresh, an unfiltered empty result, filtered-empty, a load error with retry, and a temporarily unavailable context or placement link are normal states. An empty result can reflect filters, archive visibility, or permissions rather than deletion; after a refresh, do not repeat a bulk action against a stale selection.

Downloads and privacy

Conceptual process guidance; not a UI screenshot or state evidence.

Use the download control for files. Keep SVG/HTML as downloads instead of inline content in an authenticated session; documents open in their document card. Before sharing a projection copy, check every source context, recipient permission, and client or personal data: one fixed copy can contain items from several work areas. Never publish tokens, private links, filenames, source identifiers, or live data.

Conceptual process guidance; not a UI screenshot or state evidence.