Best Practices and Support for Multi-Tenancy / Data Isolation #1880
Unanswered
harshitraj2409
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm exploring the possibility of using graphRAG to power a multi-tenant application (e.g., a SaaS platform) where different users or organizations would index their own private documents. A critical requirement for this use case is strict data isolation—ensuring that one tenant's data (indexed documents, extracted knowledge graph entities/relationships, and vector embeddings) is never accessible or returned in queries made by another tenant.
Any guidance, insights, code pointers, or discussion on the best way to architect this within the graphRAG ecosystem would be greatly appreciated!
Beta Was this translation helpful? Give feedback.
All reactions