# Exclude fields from add filter dropdown

**URL:** https://discuss.elastic.co/t/exclude-fields-from-add-filter-dropdown/315764
**Category:** Kibana
**Created:** [October 4, 2022, 10:57am UTC](https://discuss.elastic.co/t/exclude-fields-from-add-filter-dropdown/315764 "2022-10-04T10:57:23Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![Jonas\_S](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jonas_s/32/97631_2.png) [@Jonas\_S](https://discuss.elastic.co/u/Jonas_S)
#### Post date: [October 4, 2022, 10:57am UTC](https://discuss.elastic.co/t/exclude-fields-from-add-filter-dropdown/315764/1 "2022-10-04T10:57:23Z")

</div>

Hello,

i have an already existing Dashboard with personal information for a small user group. Now a new user group also needs some of that information, but should only see their part. The data comes from a logstash pipeline executed once a month, creating a new index. All indices are grouped with a data view for the Dashboard.

I was thinking: Do i need to seperate it all the way to make sure the new users only see their part? So create a new logstash pipeline fetching only the fields they should see and creating seperate indices. Or is it possible to reuse the already existing indices?  
I was trying to create a new data view based on the existing indices and add field filters for the fields they should not see:

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/a/2/a296a5e20cdccfa601ce40744ddb876b6fac63ad.png)  
But the field is still present in the add filters dropdown:  
 ![image](https://us1.discourse-cdn.com/elastic/original/3X/4/2/42d603d841dc40f9b852e4269dee592b43ae087c.png)  
And even though there is no visualisation containing the field, setting a filter would still give information about it.

So is there a way to completely exclude fields with a data view? Why is there even a filter fields functionallity if it is not consequent?

Best regards  
Jonas

---

<div class="post-metadata">

### Author: ![flash1293](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/flash1293/32/41227_2.png) [@flash1293](https://discuss.elastic.co/u/flash1293)
#### Post date: [October 5, 2022, 5:39pm UTC](https://discuss.elastic.co/t/exclude-fields-from-add-filter-dropdown/315764/2 "2022-10-05T17:39:17Z")

</div>

The data view level is not sufficient for security, it's a tool for improving performance - the user can work around this quite easily (as the query is built in the browser).

Check out [Field level security | Elasticsearch Guide [8.4] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/field-level-security.html) and [Document level security | Elasticsearch Guide [8.4] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/document-level-security.html) for fine grained access rules which can't be circumvented.

---

<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: [November 2, 2022, 5:39pm UTC](https://discuss.elastic.co/t/exclude-fields-from-add-filter-dropdown/315764/3 "2022-11-02T17:39:59Z")

</div>

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