Why it matters
Shivay Lamba explains how fine-grained, relationship-based authorization can enforce per-user and per-document access in RAG and agent pipelines. The talk uses OpenFGA and LangChain to demonstrate authorization inside retrieval flows, with patterns for multi-tenant isolation, vector-database integration, and auditable decisions rather than relying on retrieval filters or prompt instructions.
My takeaway: Authorize every retrieval and tool action against the current principal, resource, relationship, and context. Model tenant, document, and tool boundaries; deny by default; preserve decision logs; and test cross-tenant access, stale membership, confused-deputy paths, and index synchronization. Never delegate access-control enforcement to the model or its system prompt.