Multi-Client Context Isolation (Zero Context Leakage)
How Dori strictly separates project, client, and vault contexts so confidential data never bleeds across client accounts.
If you manage multiple clients, projects, or separate business entities, context leakage is a major risk. Standard AI chat tools merge all your past conversations into a global memory pool, risking a situation where Client A’s financial numbers or strategy end up in a draft for Client B.
Dori solves this with Multi-Client Context Isolation.
1. How Context Isolation Works
Dori enforces strict security and context boundaries at the database and prompt retrieval layers:
- Project & Client Vault Silos: Each client or project lives in its own designated directory and tag scope within your Markdown vault.
- Siloed Retrieval-Augmented Generation (RAG): When you execute a query or draft a document inside Client A’s workspace, Dori’s search index explicitly restricts vector search and FTS5 keyword lookups to Client A’s context window.
- Zero Cross-Contamination: Financial figures, strategic plans, and meeting notes from other clients are filtered out before the prompt is assembled.
2. Setting Up Client Isolation
- Go to Projects → New Project and create dedicated project spaces for each client.
- When capturing notes, voice memos, or files, assign them to their respective project tags (or let Dori auto-file them based on client domain rules).
- When drafting proposals or running meeting prep, select the target project scope. Dori guarantees that only that project’s memory is referenced.
Related Guides
- Run a Pipeline Without a CRM — relationship and deal tracking.
- See What Dori Did & Why — inspecting execution logs and audit entries.