# Grant permission to space is not effect

**URL:** <https://discuss.elastic.co/t/grant-permission-to-space-is-not-effect/184494>\
**Category:** Kibana\
**Created:** [June 6, 2019, 5:07am UTC](https://discuss.elastic.co/t/grant-permission-to-space-is-not-effect/184494 "2019-06-06T05:07:24Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![lukeelmers](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lukeelmers/32/35230_2.png) [@lukeelmers](https://discuss.elastic.co/u/lukeelmers)\
**Post date:** [June 6, 2019, 10:40pm UTC](https://discuss.elastic.co/t/grant-permission-to-space-is-not-effect/184494/3 "2019-06-06T22:40:42Z")

</div>

You may find this related thread to be helpful as well:

> [@Kibana User Roles, kibana\_dashboard\_only and Limit Spaces?](https://discuss.elastic.co/t/kibana-user-roles-kibana-dashboard-only-and-limit-spaces/161905/4):
>
> The kibana\_dashboard\_only\_user from the permissions perspective gives the user read-only access to all of Kibana. To have Kibana hide all of the other applications besides the Dashboards app, the Kibana advanced setting: xpackDashboardMode:roles should be configured to list this role so that all other applications are hidden. To create a new custom role which grants read-only access to a single space, you can use a cURL request similar to the following against the [Kibana Role API](https://www.elastic.co/guide/en/kibana/current/role-management-api.html) curl -H "kbn-…

---

_[View the full topic](https://discuss.elastic.co/t/grant-permission-to-space-is-not-effect/184494)._
