# Restricting fields dynamically in the search request

**URL:** <https://discuss.elastic.co/t/restricting-fields-dynamically-in-the-search-request/59946>\
**Category:** Elasticsearch\
**Created:** [September 7, 2016, 8:09am UTC](https://discuss.elastic.co/t/restricting-fields-dynamically-in-the-search-request/59946 "2016-09-07T08:09:17Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\
**Post date:** [September 9, 2016, 11:14am UTC](https://discuss.elastic.co/t/restricting-fields-dynamically-in-the-search-request/59946/2 "2016-09-09T11:14:20Z")

</div>

Hey,

this would require a static configuration. Either you do [source filtering](https://www.elastic.co/guide/en/elasticsearch/reference/2.4/search-request-source-filtering.html) (which can be circumvented) or use [field level security](https://discuss.elastic.co/t/elasticsearch-issues-on-maven-3-3-3-docker-image/59971) (which is part of the commercial offering though). Still, both need configuration.

--Alex

---

_[View the full topic](https://discuss.elastic.co/t/restricting-fields-dynamically-in-the-search-request/59946)._