# Elasticsearch security - possible to block \_search but allow get/mget?

**URL:** <https://discuss.elastic.co/t/elasticsearch-security-possible-to-block-search-but-allow-get-mget/253847>\
**Category:** Elasticsearch\
**Tags:** elastic-stack-security\
**Created:** [October 30, 2020, 5:08pm UTC](https://discuss.elastic.co/t/elasticsearch-security-possible-to-block-search-but-allow-get-mget/253847 "2020-10-30T17:08:34Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Andy\_Wick](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andy_wick/32/44017_2.png) [@Andy\_Wick](https://discuss.elastic.co/u/Andy_Wick)\
**Post date:** [October 30, 2020, 5:08pm UTC](https://discuss.elastic.co/t/elasticsearch-security-possible-to-block-search-but-allow-get-mget/253847/1 "2020-10-30T17:08:34Z")

</div>

Is it possible to create an elasticsearch user that can do get/mget but not search? It looks like there is only elasticsearch privilege around reading, called "read", and not fine grain control. I could maybe use field filtering, but that requires platinum.

The use case I'm trying to solve for is I want to allow a user to get a document if they know the id, but not search for documents.

Maybe I just need to build a simple proxy.

---

<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 27, 2020, 5:08pm UTC](https://discuss.elastic.co/t/elasticsearch-security-possible-to-block-search-but-allow-get-mget/253847/2 "2020-11-27T17:08:35Z")

</div>

Closed on November 27, 2020, 5:08pm UTC

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