https://community.databricks.com/t5/machine-learning/rbac-and-vectorsearch/m-p/67079#M3218 <P>Thanks AI for summarizing my question. However, you did not actually answer it.</P> Tue, 23 Apr 2024 14:10:17 GMT re 2024-04-23T14:10:17Z https://community.databricks.com/t5/machine-learning/rbac-and-vectorsearch/m-p/66947#M3216 <P>When implementing the managed VectorSearch, what is the preferred way to implement row based access control? I see that you can use the filter API during a query, so simple filters using a certain column may work, but what if all the security information is in another table?</P><P>The use case in question is for a RAG workflow, but where some information should be limited based on the querying user. The filter API probably work fine for a simple "information_deprecated" flag, but probably not for checking group membership.</P> Mon, 22 Apr 2024 14:51:25 GMT https://community.databricks.com/t5/machine-learning/rbac-and-vectorsearch/m-p/66947#M3216 re 2024-04-22T14:51:25Z https://community.databricks.com/t5/machine-learning/rbac-and-vectorsearch/m-p/67079#M3218 <P>Thanks AI for summarizing my question. However, you did not actually answer it.</P> Tue, 23 Apr 2024 14:10:17 GMT https://community.databricks.com/t5/machine-learning/rbac-and-vectorsearch/m-p/67079#M3218 re 2024-04-23T14:10:17Z