Kibana multi-tenancy

[Stacey_Gammon]

I'm going to link to an old discuss ticket which I think answers your question:

Does ElasticSearch/Kibana Support Multi Tenancy?

I am trying to understand how to restrict the elasticsearch data that different user groups can view using Kibana. In other words, I am trying to understand how an elasticsearch/kibana solution can be a multi tenant solution. I recognize the answer might have to do with how you architect your solution. Assume that I have two different sets of users. Each set of users can only access their own set of data via Kibana. What is the best way to architect this solution? Should I have 2 different…

Specifically this answer from @tbragin :

Does ElasticSearch/Kibana Support Multi Tenancy?

Multi-tenancy at the data level exists if you pair Kibana/Elasticsearch with Shield - you can restrict which users can view which data in Elasticsearch at a pretty granular level. However, fine-grained access control at the UI level, such as restricting which dashboards and views are accessible to given groups of users, is not part of that integration yet. You can work around this currently by setting up multiple instances of Kibana - one per user - configured to point to different configuratio…

Even though this is a pretty old discuss ticket, it's still a good representation of where we are today.