Finding the right document in RAG is not enough

Retrieval-Augmented Generation strengthens the model’s answer with context from in-house documents. But the search layer is not a permission layer; if a user can find a document they should not see, the system is not secure.

Permissions must be checked before search

Access boundaries such as department, role, customer or project scope should be kept in document metadata and applied to query results. Hiding results on screen after fetching them is not a secure approach.

Show the source to the user

Showing which document and section produced the answer increases both trust and human oversight. When no source is found, the model saying so is more valuable than answering every question with certainty.

Data lifecycle

• Removing old or cancelled documents from the index.
• Carrying deletion requests into the embedding layer too.
• Limiting sensitive information in query and output logs.
• Making sure the model does not mistake external instructions for system rules.