Engineering
RAG that survives permissions, freshness, and citations
How to design retrieval-augmented generation for enterprise production: access control, source quality, freshness, citations, latency, and evaluation.
9 min read · Updated 2026-07-26
Key takeaways
- Enterprise RAG fails more often on permissions and freshness than on embedding choice.
- Citations without source quality controls create confident wrong answers.
- Evaluation must cover groundedness, access leakage, and regression — not only “helpfulness.”
Stop treating RAG as “chat over PDFs”
Production RAG is a knowledge platform: ingestion, chunking strategy, metadata, access control, retrieval quality, answer synthesis, citations, evaluation, and operations. If any layer is weak, the product looks smart in demos and brittle in real use.
Permissions are product requirements
If a user cannot open a document in the source system, the assistant should not surface its contents. That requires identity, document ACLs or equivalent policy, and retrieval filters that enforce them under load — including for cached or embedded content.
Access leakage is a security incident, not a prompt-tuning issue.
Freshness and source quality
Stale indexes create legally and operationally dangerous answers. Production systems need update pipelines, tombstoning, version awareness, and explicit handling when sources conflict or are outdated.
Source quality scoring — trusted systems of record versus informal docs — should influence retrieval and answer confidence.
Citations that mean something
Citations are only useful when they point to the passages that actually supported the claim and when the system can abstain when evidence is weak. Force-citing irrelevant chunks trains users to distrust the product.
Evaluate before you scale
Golden questions, groundedness checks, permission tests, latency budgets, and regression suites should gate releases. Measure failure modes your enterprise cares about: leakage, hallucination under sparse evidence, and broken retrieval after corpus changes.
Map this to your environment
Book a Production Readiness Assessment to translate these principles into a concrete architecture, risk map, and first production path.