# How to use Document Level Security to make Kibana Multitenant?

**URL:** <https://discuss.elastic.co/t/how-to-use-document-level-security-to-make-kibana-multitenant/138567>\
**Category:** Kibana\
**Created:** [July 4, 2018, 1:28pm UTC](https://discuss.elastic.co/t/how-to-use-document-level-security-to-make-kibana-multitenant/138567 "2018-07-04T13:28:31Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![BicaLuv](https://avatars.discourse-cdn.com/v4/letter/b/c5a1d2/32.png) [@BicaLuv](https://discuss.elastic.co/u/BicaLuv)\
**Post date:** [July 4, 2018, 1:28pm UTC](https://discuss.elastic.co/t/how-to-use-document-level-security-to-make-kibana-multitenant/138567/1 "2018-07-04T13:28:32Z")

</div>

Hello!  
We use ES 6.2.1 and would like to add some multi-tenant support to kibana.  
To us it would be good enough to have the Kibana Dashboard View filter dashboards based on their titles.  
To achieve this I tried adding a document based security entry on the ".kibana" index that shows only dashboards starting with "public\_":  
post /_xpack/security/role/test\_group  
{  
"indices": [  
{  
"names":[".kibana"],  
"priviledges": ["read"],  
"query": { "term": {"dashboard.title": "public_\*"}}  
}  
]  
}  
But when logged in with user test\_group, I still see all dashboards.

---

<div class="post-metadata">

**Author:** ![Larry\_Gregory](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/larry_gregory/32/34969_2.png) [@Larry\_Gregory](https://discuss.elastic.co/u/Larry_Gregory)\
**Post date:** [July 6, 2018, 7:40pm UTC](https://discuss.elastic.co/t/how-to-use-document-level-security-to-make-kibana-multitenant/138567/2 "2018-07-06T19:40:33Z")

</div>

Hey @BicaLuv,

Creating a multi-tenant Kibana installation using Document Level Security isn't supported, as it relies heavily on internal implementation details that aren't guaranteed to be compatible in the future.

I have some good news for you though: we are actively working on a "Spaces" feature that will allow you to organize and secure access to your Kibana dashboards, visualizations, and other saved objects. You can track our progress here: [https://github.com/elastic/kibana/issues/18948](https://github.com/elastic/kibana/issues/18948)

---

<div class="post-metadata">

**Author:** ![BicaLuv](https://avatars.discourse-cdn.com/v4/letter/b/c5a1d2/32.png) [@BicaLuv](https://discuss.elastic.co/u/BicaLuv)\
**Post date:** [July 7, 2018, 8:00am UTC](https://discuss.elastic.co/t/how-to-use-document-level-security-to-make-kibana-multitenant/138567/3 "2018-07-07T08:00:42Z")

</div>

@Larry_Gregory, thanks for the reply.  
I know that tweaking .kibana index that way is not an official solution. But based on the fact, that there is currently no solution at all, I would give it a try for 6.2 and 6.3 installations in our project.

BTW: I will keep an eye on what the new spaces feature will bring.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [August 4, 2018, 8:00am UTC](https://discuss.elastic.co/t/how-to-use-document-level-security-to-make-kibana-multitenant/138567/4 "2018-08-04T08:00:45Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.