20Design RAG over 10M documents with per-user permissions: a user must never see data they can't access▼hardGleanMicrosoftOpenAI1 replies○ sign inGlean's signature design question. The two traps: post-filtering that drains your top-k, and the leak through generated answers. The winning architecture filters at retrieval, and here is how, at scale.Open full answer →
25Design per-user permissions for a RAG system over a company's documents. The CEO and an intern ask the same question.▼hardGleanMicrosoftSnowflake1 replies◆ premiumThe defining security design problem of enterprise RAG, and the reason Glean exists. Query-time ACL filtering, permission sync lag, and the leakage channels that survive naive designs: caches, citations, and the model itself.Open full answer →