# Disable search function in Kibana dashboard and visualisation

**URL:** <https://discuss.elastic.co/t/disable-search-function-in-kibana-dashboard-and-visualisation/298133>\
**Category:** Kibana\
**Created:** [February 24, 2022, 9:11am UTC](https://discuss.elastic.co/t/disable-search-function-in-kibana-dashboard-and-visualisation/298133 "2022-02-24T09:11:19Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![cf4455](https://avatars.discourse-cdn.com/v4/letter/c/e68b1a/32.png) [@cf4455](https://discuss.elastic.co/u/cf4455)\
**Post date:** [February 24, 2022, 9:11am UTC](https://discuss.elastic.co/t/disable-search-function-in-kibana-dashboard-and-visualisation/298133/1 "2022-02-24T09:11:19Z")

</div>

Hi there,

we activated X-Pack for our Elasticsearch and Kibana and created different users, roles and spaces. That works great.  
However, we would like to disable the search for specific users, roles or spaces. Is that possible? So far I've only found tricks via CSS, but unfortunately that's not enough for us.

Reason: There is an attribute in our logs that we don't want to show to some users. We can set up visualizations and dashboards so that this attribute is not visible. But they can still find and view this via the search function.

Many greetings  
Christian

---

<div class="post-metadata">

**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\
**Post date:** [February 25, 2022, 6:45am UTC](https://discuss.elastic.co/t/disable-search-function-in-kibana-dashboard-and-visualisation/298133/2 "2022-02-25T06:45:16Z")

</div>

Perhaps you should look at document level security and field level security.

These are commercial paid for features but you can trial them to see if they work for you.

You can set up roles that will not ever be able to even access the documents and / or fields that you don't want them to. These role can tied to users in spaces.

Document level security

> **[Document level security | Elasticsearch Guide \[8.0\] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/document-level-security.html)**

Field Level Security

> **[Field level security | Elasticsearch Guide \[8.0\] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/field-level-security.html)**

---

<div class="post-metadata">

**Author:** ![cf4455](https://avatars.discourse-cdn.com/v4/letter/c/e68b1a/32.png) [@cf4455](https://discuss.elastic.co/u/cf4455)\
**Post date:** [February 28, 2022, 8:43am UTC](https://discuss.elastic.co/t/disable-search-function-in-kibana-dashboard-and-visualisation/298133/3 "2022-02-28T08:43:24Z")

</div>

Hi @stephenb,

thanks for your quick reply. The field level security sounds very good. At the moment we are using the free standard version. Are there publicly visible prices or do I have to make an inquiry via [Offizielle Preisinformationen zu Elasticsearch: Elastic Cloud, verwaltetes Elasticsearch | Elastic](https://www.elastic.co/de/pricing) ? The problem is that I can't find any prices anywhere and I can't figure out which model we would then need.

---

<div class="post-metadata">

**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\
**Post date:** [February 28, 2022, 2:40pm UTC](https://discuss.elastic.co/t/disable-search-function-in-kibana-dashboard-and-visualisation/298133/4 "2022-02-28T14:40:50Z")

</div>

Here is Elastic Cloud Pricing

[https://cloud.elastic.co/pricing](https://cloud.elastic.co/pricing)

For self managed licenses you need to inquire.

---

<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:** [March 28, 2022, 2:40pm UTC](https://discuss.elastic.co/t/disable-search-function-in-kibana-dashboard-and-visualisation/298133/5 "2022-03-28T14:40:56Z")

</div>

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