# Make filters option read only in Kibana

**URL:** <https://discuss.elastic.co/t/make-filters-option-read-only-in-kibana/176169>\
**Category:** Kibana\
**Created:** [April 10, 2019, 8:29am UTC](https://discuss.elastic.co/t/make-filters-option-read-only-in-kibana/176169 "2019-04-10T08:29:19Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ashwin\_Bharadwaj](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ashwin_bharadwaj/32/42567_2.png) [@Ashwin\_Bharadwaj](https://discuss.elastic.co/u/Ashwin_Bharadwaj)\
**Post date:** [April 10, 2019, 8:29am UTC](https://discuss.elastic.co/t/make-filters-option-read-only-in-kibana/176169/1 "2019-04-10T08:29:19Z")

</div>

Hello Team,

We are using kibana for logs tracking purpose. Ours is a multi tenant application and i'm working on securing the kibana logs from different tenant users. The intent is to disable the filter option or make it read only as we are trying to redirect to kibana from our application by passing the filter at tenant level.

Is there any way where we can make this filter read only or hide from user so that they can not change the filter anytime.

Elasticsearch Version : 6.5.4

---

<div class="post-metadata">

**Author:** ![Marius\_Dragomir](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/marius_dragomir/32/42087_2.png) [@Marius\_Dragomir](https://discuss.elastic.co/u/Marius_Dragomir)\
**Post date:** [April 12, 2019, 9:44am UTC](https://discuss.elastic.co/t/make-filters-option-read-only-in-kibana/176169/2 "2019-04-12T09:44:38Z")

</div>

Hello,

The closest thing to what you want to do is Document Level Security and Field Level Security.  
[https://www.elastic.co/guide/en/elastic-stack-overview/current/document-level-security.html](https://www.elastic.co/guide/en/elastic-stack-overview/current/document-level-security.html)

Instead of passing the filter from the app, you can do a request to the api to add a specific role to the user that wants to check kibana so they'll only see data they have access to, like a filter, but not-editable by the user.

---

<div class="post-metadata">

**Author:** ![Ashwin\_Bharadwaj](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ashwin_bharadwaj/32/42567_2.png) [@Ashwin\_Bharadwaj](https://discuss.elastic.co/u/Ashwin_Bharadwaj)\
**Post date:** [April 22, 2019, 6:23am UTC](https://discuss.elastic.co/t/make-filters-option-read-only-in-kibana/176169/3 "2019-04-22T06:23:57Z")

</div>

Thanks Marius for the suggested solution.

However this requires to have Kibana in non basic mode. Is there anything which you can suggest for basic licences kibana.

---

<div class="post-metadata">

**Author:** ![Ashwin\_Bharadwaj](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ashwin_bharadwaj/32/42567_2.png) [@Ashwin\_Bharadwaj](https://discuss.elastic.co/u/Ashwin_Bharadwaj)\
**Post date:** [April 23, 2019, 8:30am UTC](https://discuss.elastic.co/t/make-filters-option-read-only-in-kibana/176169/4 "2019-04-23T08:30:50Z")

</div>

Hello Marius,

I was able to achieve the document level security through non basic license. Thank you very much for the help.

Is there anyway to achieve the same with Basic license.?

---

<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:** [May 21, 2019, 8:30am UTC](https://discuss.elastic.co/t/make-filters-option-read-only-in-kibana/176169/5 "2019-05-21T08:30:52Z")

</div>

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