# Limiting access to visualizations

**URL:** <https://discuss.elastic.co/t/limiting-access-to-visualizations/128098>\
**Category:** Kibana\
**Created:** [April 16, 2018, 4:06am UTC](https://discuss.elastic.co/t/limiting-access-to-visualizations/128098 "2018-04-16T04:06:24Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![kenneth](https://avatars.discourse-cdn.com/v4/letter/k/94ad74/32.png) [@kenneth](https://discuss.elastic.co/u/kenneth)\
**Post date:** [April 16, 2018, 4:06am UTC](https://discuss.elastic.co/t/limiting-access-to-visualizations/128098/1 "2018-04-16T04:06:24Z")

</div>

Hi @elastic

Is there anyway I can use the "Granted Documents Query" to restrict access to visualizations without creating different ".kibana" indices per use case as suggested in this topic [Any way to show different kibana view to different users?](https://discuss.elastic.co/t/any-way-to-show-different-kibana-view-to-different-users/80342)?

For example if I have the following visualizations/dashboards, I would like to control which role has access to it.

role\_end\_users =\> Common visualizations/dashboards  
role\_managers =\> Common visualizations/dashboards, management-related visualizations/dashboards

Appreciate your inputs and suggestions.

Kenneth

---

<div class="post-metadata">

**Author:** ![emil.mirzayev](https://avatars.discourse-cdn.com/v4/letter/e/ba9def/32.png) [@emil.mirzayev](https://discuss.elastic.co/u/emil.mirzayev)\
**Post date:** [April 16, 2018, 6:31am UTC](https://discuss.elastic.co/t/limiting-access-to-visualizations/128098/2 "2018-04-16T06:31:09Z")

</div>

Hi @kenneth, yes, you can do that. With X-pack Security module you can restrict/grant different access rights to different user groups starting from dashboards, ending with specific fields on specific indices. More info you can find [on X-pack docu page](https://www.elastic.co/guide/en/x-pack/current/xpack-security.html)

---

<div class="post-metadata">

**Author:** ![kenneth](https://avatars.discourse-cdn.com/v4/letter/k/94ad74/32.png) [@kenneth](https://discuss.elastic.co/u/kenneth)\
**Post date:** [April 16, 2018, 8:22pm UTC](https://discuss.elastic.co/t/limiting-access-to-visualizations/128098/3 "2018-04-16T20:22:46Z")

</div>

@emil.mirzayev when you said ending with specific fields on specific indices, may i know what you mean by that?

---

<div class="post-metadata">

**Author:** ![emil.mirzayev](https://avatars.discourse-cdn.com/v4/letter/e/ba9def/32.png) [@emil.mirzayev](https://discuss.elastic.co/u/emil.mirzayev)\
**Post date:** [April 17, 2018, 7:25am UTC](https://discuss.elastic.co/t/limiting-access-to-visualizations/128098/4 "2018-04-17T07:25:12Z")

</div>

I mean that, you can even block some fields on some indices for a user. The user will see all fields that has access to. This is very specific use case

---

<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:** [May 15, 2018, 7:25am UTC](https://discuss.elastic.co/t/limiting-access-to-visualizations/128098/5 "2018-05-15T07:25:19Z")

</div>

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