# Hide space for user **URL:** \ **Category:** Elasticsearch\ **Created:** [June 30, 2020, 2:47pm UTC](https://discuss.elastic.co/t/hide-space-for-user/239327 "2020-06-30T14:47:33Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![igarci](https://avatars.discourse-cdn.com/v4/letter/i/dc4da7/32.png) [@igarci](https://discuss.elastic.co/u/igarci)\ **Post date:** [June 30, 2020, 2:47pm UTC](https://discuss.elastic.co/t/hide-space-for-user/239327/1 "2020-06-30T14:47:33Z")
Hello I have kibana 7.2 and basic license I am trying to hide or not allow any user to access some space, but there is no documentation to do it. I just want to create a user who can access to different workspaces with different privileges. For example: user administrator can access and view all workspaces with all privileges the user employee just can access and view a workspace called employee that only allows reading data from dashboard, visualize and discover Does it possible ?? Could someone help me?? Thanks in avance ---
**Author:** ![Wolfram\_Haussig](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/wolfram_haussig/32/70528_2.png) [@Wolfram\_Haussig](https://discuss.elastic.co/u/Wolfram_Haussig)\ **Post date:** [July 1, 2020, 4:53am UTC](https://discuss.elastic.co/t/hide-space-for-user/239327/2 "2020-07-01T04:53:41Z")
Hello Isaac, Have a look here: [https://www.elastic.co/guide/en/kibana/7.2/kibana-role-management.html](https://www.elastic.co/guide/en/kibana/7.2/kibana-role-management.html) You can configure on each role which Space users with this role are allowed to see and even if they have readonly or write access (which is even configurable on a per feature basis). Best regards Wolfram ---
**Author:** ![igarci](https://avatars.discourse-cdn.com/v4/letter/i/dc4da7/32.png) [@igarci](https://discuss.elastic.co/u/igarci)\ **Post date:** [July 1, 2020, 6:03am UTC](https://discuss.elastic.co/t/hide-space-for-user/239327/3 "2020-07-01T06:03:28Z")
Hello wolfram I tried this before, but after creating the role and assigning a user to this role, all workspaces are available to all users. True, I can configure it, a user has real privileges (all, read or none) for a tab, but I would like the user to only see the associated workspaces and can't see other workspaces Thanks for your answer ---
**Author:** ![igarci](https://avatars.discourse-cdn.com/v4/letter/i/dc4da7/32.png) [@igarci](https://discuss.elastic.co/u/igarci)\ **Post date:** [July 1, 2020, 8:27am UTC](https://discuss.elastic.co/t/hide-space-for-user/239327/4 "2020-07-01T08:27:39Z")
I solved my problem. It was because I created an anonymous access in elastichsearch.yml This could not allow me to be privileged for roles. Now if I keep this out when I create an elastichsearch request it asks me for username and password. Is there a way to have both? I mean, you can create different roles with different privileges and elastichssearch doesn't ask for username and password or can create a anonymous access without this issues Thank you ---
**Author:** ![Wolfram\_Haussig](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/wolfram_haussig/32/70528_2.png) [@Wolfram\_Haussig](https://discuss.elastic.co/u/Wolfram_Haussig)\ **Post date:** [July 2, 2020, 4:54am UTC](https://discuss.elastic.co/t/hide-space-for-user/239327/5 "2020-07-02T04:54:30Z")
Hello Isaac, You could install an apache server which is called by users who want to login anonymously. In the apache configuration you can create a forwarding rule to Kibana including the user authentication of a single user which should be used as an anonymous login. Everyone with their own users can login using the normal Kibana UI. Best regards Wolfram ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 30, 2020, 4:54am UTC](https://discuss.elastic.co/t/hide-space-for-user/239327/6 "2020-07-30T04:54:32Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.