We do it through a central ai tool server, openAI compatible interface + MCP, where any knowledge ingested is still linked to the source (always good) and the authorisation layer of the source that was ingested. If we consume a wiki where permissions are managed with a Windows AD, this info needs to be collected when you ingest the information. Such connectors are source specific and must be aware how the system manages permissions. With the correct architecture, you

That way any agent tool only has the information the employee was able to access anyway. A larger problem is to ensure quality control for any answers with different context depths, but that isn't easily testable with or without access management.

It isn't product-y, but often the standard RAG-AI pipeline that is also used to delegate queries to either local or remote agents (and the latter might also not be allowed to consumer PII for example - access management on the other side)