I used AI tools to help draft and edit this post. I checked the facts and the wording, and the original lives at geekindata.com . The diagrams are on that page.

One entitlement module for chat, browse, and citation

Key takeaways

Put chat, browse, download, upload, reindex, and citation on one authorization module.

Use the same role family for the agent catalog and knowledge categories.

Filter the library and clamp retrieval on the server before the SPA renders.

Citation and content routes must call the same path checks as library browse.

Write implication rules (manage implies use, or not) and unit-test them.

Test general-only, specialized-only, admin, and named break-glass matrices.

An agent that answers from documents is only as trustworthy as the document permissions behind it.

Teams often lock the chat endpoint carefully, then leave library browse and citation file downloads open to anyone who can sign in. That is not a knowledge boundary.…