# Need more clarity on user access in X-pack? **URL:** \ **Category:** Elasticsearch\ **Created:** [August 29, 2016, 7:52am UTC](https://discuss.elastic.co/t/need-more-clarity-on-user-access-in-x-pack/59158 "2016-08-29T07:52:12Z")\ **Posts on this page:** 7\ **Page:** 1
**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:** [August 29, 2016, 7:52am UTC](https://discuss.elastic.co/t/need-more-clarity-on-user-access-in-x-pack/59158/1 "2016-08-29T07:52:12Z")
Hi Experts, I installed X-pack and i loved it . I still have some concerns regarding user access and please let me know if the following can be achieved with X-pack access management . So my requirement is 1. User can only open abc dashboard not any other dashboard (or other dashboards should not visible to him ).This user will only have read permission not write or delete permission. 2. User can change password. 3. All other X-pack features like Console, Visualize, management (connect data,users,roles,Index pattern,advance settings ) shuld not be visible as i want to provide a very basic read permission to the user to a dashboard.I do not want user to make any changes to the dashboards etc. So in short when user logsin he can only see dashboard ,he can only share , print , export this dashboard, can change password.Rest other stuff should be disabled or not visible to this user Please suggest with which role or privilege i can achieve the above in X-pack. Thanks Vikas ---
**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:** [August 29, 2016, 3:23pm UTC](https://discuss.elastic.co/t/need-more-clarity-on-user-access-in-x-pack/59158/2 "2016-08-29T15:23:46Z")
@jaymode please help me on this , I got response from you on X-pack last time, so thought to bother you again. ---
**Author:** ![bohyun](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bohyun/32/10087_2.png) [@bohyun](https://discuss.elastic.co/u/bohyun)\ **Post date:** [August 29, 2016, 6:01pm UTC](https://discuss.elastic.co/t/need-more-clarity-on-user-access-in-x-pack/59158/3 "2016-08-29T18:01:07Z")
Hi Vikas, Thanks for installing X-Pack and providing feedback. > 1. User can only open abc dashboard not any other dashboard (or other dashboards should not visible to him ).This user will only have read permission not write or delete permission. Currently the dashboard level security is not possible but we are tracking the issue [here](https://github.com/elastic/kibana/issues/4453). The workaround would be to create multiple Kibana instances with different set of dashboards. > 1. User can change password. As of 5.0 Alpha-5, it is possible for users to change their own passwords. It is as simple as clicking on their user icon that appears on the bottom left pane. > 1. All other X-pack features like Console, Visualize, management (connect data,users,roles,Index pattern,advance settings ) shuld not be visible as i want to provide a very basic read permission to the user to a dashboard.I do not want user to make any changes to the dashboards etc. I'd like to clarify that Visualize and management are not X-Pack features as they are core Kibana features. It would be possible to hide X-Pack tabs such as Console, Monitoring, Graph by using the following in your 'kibana.yml' `xpack.plugin_name.enabled: false` More detailed documentation is [here](https://www.elastic.co/guide/en/x-pack/v5.0.0-alpha5-docs/monitoring-settings.html#general-monitoring-settings). And we are currently tracking the progress for having the ability to hide core Kibana tabs [here](https://github.com/elastic/kibana/issues/6545). Hope this helps, Bohyun ---
**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:** [August 30, 2016, 4:53am UTC](https://discuss.elastic.co/t/need-more-clarity-on-user-access-in-x-pack/59158/4 "2016-08-30T04:53:59Z")
Thank You Kim for this elaborative answer My further observations 1. xpack.plugin\_name.enabled: false did not work for me , so I checked the documents and implemented following . If I want to disable monitoring plugin I have to mention xpack.monitoring.enabled: false in both ES.yml and Kibana.yml. After doing this monitor tab is gone in kibana . Well I guess exactly the same I can do for other plugins like graph , console etc Now my concern is since I have disabled this feature entirely , now what if admin user wants to do some activity on monitoring plugin. So again this feature needs to be enabled on both ES and Kibana and this needs restart which is not recommended in prod. What I believe the best practice is to provide user based access to the plugins like admin can see all kibana , x-pack plugins but normal users can only see few of them like reporting, dashboard, discover. Are we considering this approach in future ? Regards Vikas ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [August 30, 2016, 11:00am UTC](https://discuss.elastic.co/t/need-more-clarity-on-user-access-in-x-pack/59158/5 "2016-08-30T11:00:31Z")
> [@vikas\_gopal](#): > > `plugin_name` You need to replace that part with the actual plugin name, eg `monitoring`. ---
**Author:** ![bohyun](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bohyun/32/10087_2.png) [@bohyun](https://discuss.elastic.co/u/bohyun)\ **Post date:** [August 30, 2016, 2:00pm UTC](https://discuss.elastic.co/t/need-more-clarity-on-user-access-in-x-pack/59158/6 "2016-08-30T14:00:33Z")
Hi Vikas In order to hide a tab (e.g. Monitoring tab) successfully, you need to make sure that both Elasticsearch and Kibana instances to be restarted. I observed the same behavior when I took the following steps only: 1. stop the Kibana instance 2. modify kibana.yml 3. restart kibana instance Instead, you need to take the following steps to achieve what you want, which is not disabling the feature entirely and just hiding the monitoring tab from the UI. 1. stop _both kibana and Elasticsearch_ instances 2. modify kibana.yml 3. restart Elasticsearch instance then Kibana instance. Let me know if this works for you. > What I believe the best practice is to provide user based access to the plugins like admin can see all kibana , x-pack plugins but normal users can only see few of them like reporting, dashboard, discover. > Are we considering this approach in future ? As described in my earlier comment, we are tracking the issue to hide the core Kibana tabs [here](https://github.com/elastic/kibana/issues/6545). Hope this helps, Bohyun ---
**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:40pm UTC](https://discuss.elastic.co/t/need-more-clarity-on-user-access-in-x-pack/59158/7 "2017-07-06T13:40:26Z")