# Disable filter option (Dashboard Kibana)

**URL:** https://discuss.elastic.co/t/disable-filter-option-dashboard-kibana/85549
**Category:** Kibana
**Created:** [May 12, 2017, 11:15am UTC](https://discuss.elastic.co/t/disable-filter-option-dashboard-kibana/85549 "2017-05-12T11:15:24Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![Helder\_Marques](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/helder_marques/32/18160_2.png) [@Helder\_Marques](https://discuss.elastic.co/u/Helder_Marques)
#### Post date: [May 12, 2017, 11:15am UTC](https://discuss.elastic.co/t/disable-filter-option-dashboard-kibana/85549/1 "2017-05-12T11:15:24Z")

</div>

Can I disable these buttons? I don't want users to see them.

![](https://us1.discourse-cdn.com/elastic/original/3X/5/5/55a26379b2cb0119de5aa7457bc3cdfa32ca64dd.png)

---

<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: [May 12, 2017, 12:34pm UTC](https://discuss.elastic.co/t/disable-filter-option-dashboard-kibana/85549/2 "2017-05-12T12:34:29Z")

</div>

Those buttons are not removable. You could modify Kibana from source and rebuild it after you hide them from CSS, but it would be hard to maintain a fork. Best thing I can do is add an enhancement request in our X-Pack repo which deals with users and access.  
But out of curiosity, why would you want to remove them from there? Maybe we can achieve the same result using an available feature.

---

<div class="post-metadata">

### Author: ![Helder\_Marques](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/helder_marques/32/18160_2.png) [@Helder\_Marques](https://discuss.elastic.co/u/Helder_Marques)
#### Post date: [May 12, 2017, 2:16pm UTC](https://discuss.elastic.co/t/disable-filter-option-dashboard-kibana/85549/3 "2017-05-12T14:16:10Z")

</div>

Thanks for your reply.  
I'm building different URLs for user levels by changing the search parameters. By being able to change the query, the user can access data that should not have access.  
Is there another way?

---

<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: [May 12, 2017, 2:40pm UTC](https://discuss.elastic.co/t/disable-filter-option-dashboard-kibana/85549/4 "2017-05-12T14:40:00Z")

</div>

The simple solution for what you want to achieve is document/field level security, which is part of X-Pack. Other than that maybe filter the button out of your nginx or remove it from disk, this way they can't see it. It's not perfect, but it's not a supported behavior.

---

<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: [June 9, 2017, 2:51pm UTC](https://discuss.elastic.co/t/disable-filter-option-dashboard-kibana/85549/5 "2017-06-09T14:51:46Z")

</div>

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