# Why all fields and indices are visible to specific user while performing Document and Field Level security?

**URL:** <https://discuss.elastic.co/t/why-all-fields-and-indices-are-visible-to-specific-user-while-performing-document-and-field-level-security/99083>\
**Category:** Elasticsearch\
**Created:** [September 1, 2017, 5:09am UTC](https://discuss.elastic.co/t/why-all-fields-and-indices-are-visible-to-specific-user-while-performing-document-and-field-level-security/99083 "2017-09-01T05:09:50Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![PinkiMondal](https://avatars.discourse-cdn.com/v4/letter/p/a698b9/32.png) [@PinkiMondal](https://discuss.elastic.co/u/PinkiMondal)\
**Post date:** [September 1, 2017, 5:09am UTC](https://discuss.elastic.co/t/why-all-fields-and-indices-are-visible-to-specific-user-while-performing-document-and-field-level-security/99083/1 "2017-09-01T05:09:50Z")

</div>

Hi

I have applied document level security for a particular user but when I login through that user, Firstly **all the Indices names** are visible in the **Discover Screen**. Secondly, **all the field names** are visible to that user while choosing split charts in **visualization**.

**Is there any way to hide the fields and indices names for a particular user, Is there any configuration available?**

---

<div class="post-metadata">

**Author:** ![vikas\_gopal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vikas_gopal/32/47661_2.png) [@vikas\_gopal](https://discuss.elastic.co/u/vikas_gopal)\
**Post date:** [September 1, 2017, 9:35am UTC](https://discuss.elastic.co/t/why-all-fields-and-indices-are-visible-to-specific-user-while-performing-document-and-field-level-security/99083/2 "2017-09-01T09:35:20Z")

</div>

Hi,

Even I am trying to achieve the same , but at the field level . So I want to restrict user to certain fields , but when I select field name under the granted field list my Discover tab stops displaying the results . However if i choose \* there the it works but user can see all the fields . I believe your problem and mine are related so thought to add comment here . Will share my findings also .

Regards  
VG

---

<div class="post-metadata">

**Author:** ![PinkiMondal](https://avatars.discourse-cdn.com/v4/letter/p/a698b9/32.png) [@PinkiMondal](https://discuss.elastic.co/u/PinkiMondal)\
**Post date:** [September 7, 2017, 10:36am UTC](https://discuss.elastic.co/t/why-all-fields-and-indices-are-visible-to-specific-user-while-performing-document-and-field-level-security/99083/3 "2017-09-07T10:36:46Z")

</div>

Please reply if anyone has any suggestions

---

<div class="post-metadata">

**Author:** ![vikas\_gopal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vikas_gopal/32/47661_2.png) [@vikas\_gopal](https://discuss.elastic.co/u/vikas_gopal)\
**Post date:** [September 8, 2017, 1:34pm UTC](https://discuss.elastic.co/t/why-all-fields-and-indices-are-visible-to-specific-user-while-performing-document-and-field-level-security/99083/4 "2017-09-08T13:34:25Z")

</div>

Yeah No answer or suggestion , this is strange . So for now I am dropping plan with Shield or X-Pack.  
@PinkiMondal :- Are you facing the same issue ?

---

<div class="post-metadata">

**Author:** ![PinkiMondal](https://avatars.discourse-cdn.com/v4/letter/p/a698b9/32.png) [@PinkiMondal](https://discuss.elastic.co/u/PinkiMondal)\
**Post date:** [September 11, 2017, 6:43am UTC](https://discuss.elastic.co/t/why-all-fields-and-indices-are-visible-to-specific-user-while-performing-document-and-field-level-security/99083/5 "2017-09-11T06:43:29Z")

</div>

Yes @vikas_gopal

---

<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:** [October 9, 2017, 6:43am UTC](https://discuss.elastic.co/t/why-all-fields-and-indices-are-visible-to-specific-user-while-performing-document-and-field-level-security/99083/6 "2017-10-09T06:43:31Z")

</div>

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