# Indices/dashboards etc names visibility for every user? **URL:** \ **Category:** Elasticsearch\ **Tags:** elastic-stack-security\ **Created:** [January 18, 2016, 1:18pm UTC](https://discuss.elastic.co/t/indices-dashboards-etc-names-visibility-for-every-user/39451 "2016-01-18T13:18:23Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![logstaszek](https://avatars.discourse-cdn.com/v4/letter/l/b9e5f3/32.png) [@logstaszek](https://discuss.elastic.co/u/logstaszek)\ **Post date:** [January 18, 2016, 1:18pm UTC](https://discuss.elastic.co/t/indices-dashboards-etc-names-visibility-for-every-user/39451/1 "2016-01-18T13:18:23Z")
Hello, I have a question. I have configured some roles, for example, user1 can see only dashboard1 and user2 can see only dashboard2. In kibana user2 of course can't access to dashboard1, error show up, but he can see the name of dashboard, and user1 can see the name of dashboard2 to which he doesn't has access. Is there possibility to turn off the visibility of particular indices in roles that can't access them? Is this clearly defined, or should I upload some pic, cause of my poor english language? 😛 ---
**Author:** ![jaymode](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jaymode/32/50103_2.png) [@jaymode](https://discuss.elastic.co/u/jaymode)\ **Post date:** [January 18, 2016, 2:25pm UTC](https://discuss.elastic.co/t/indices-dashboards-etc-names-visibility-for-every-user/39451/2 "2016-01-18T14:25:58Z")
Kibana does not currently support the ability to restrict dashboards based on a user as Kibana does not have knowledge of the ACLs provided by shield. We're thinking about how we can solve this issue so that Kibana and Shield have better integration in the future. ---
**Author:** ![logstaszek](https://avatars.discourse-cdn.com/v4/letter/l/b9e5f3/32.png) [@logstaszek](https://discuss.elastic.co/u/logstaszek)\ **Post date:** [January 19, 2016, 7:15am UTC](https://discuss.elastic.co/t/indices-dashboards-etc-names-visibility-for-every-user/39451/3 "2016-01-19T07:15:30Z")
Hmmm, ok. And what about admin roles. Admin1 and Admin2 can create dashboards/visualizations from own indices, but Admin1 can overwrite any visualize/dashboard name created before for example by Admin2. Also, we can't resolve this problem for now? ---
**Author:** ![jaymode](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jaymode/32/50103_2.png) [@jaymode](https://discuss.elastic.co/u/jaymode)\ **Post date:** [January 19, 2016, 11:50am UTC](https://discuss.elastic.co/t/indices-dashboards-etc-names-visibility-for-every-user/39451/4 "2016-01-19T11:50:12Z")
> [@logstaszek](#): > > Also, we can't resolve this problem for now? That's correct, we are still working on a solution. Shield does not differentiate between a user and a admin, they simply have different permissions. ---
**Author:** ![tbragin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tbragin/32/45166_2.png) [@tbragin](https://discuss.elastic.co/u/tbragin)\ **Post date:** [February 2, 2016, 12:30am UTC](https://discuss.elastic.co/t/indices-dashboards-etc-names-visibility-for-every-user/39451/5 "2016-02-02T00:30:45Z")
One potential workaround if you don't have too many groups is to set up separate Kibana instances for each group pointing to different configuration indices (instead of the defailt .kibana index). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 1:47pm UTC](https://discuss.elastic.co/t/indices-dashboards-etc-names-visibility-for-every-user/39451/6 "2017-07-06T13:47:01Z")