# Limit access to dashboard **URL:** \ **Category:** Elasticsearch\ **Created:** [January 20, 2017, 3:24pm UTC](https://discuss.elastic.co/t/limit-access-to-dashboard/72308 "2017-01-20T15:24:04Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![Mormaii](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mormaii/32/10790_2.png) [@Mormaii](https://discuss.elastic.co/u/Mormaii)\ **Post date:** [January 20, 2017, 3:24pm UTC](https://discuss.elastic.co/t/limit-access-to-dashboard/72308/1 "2017-01-20T15:24:04Z")
How can I limit a roles ability to access certain dashboards? Is it possible to let a role only see certain dashboards? ---
**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:** [January 21, 2017, 8:25am UTC](https://discuss.elastic.co/t/limit-access-to-dashboard/72308/2 "2017-01-21T08:25:36Z")
Not at this point, it's something we're working on! ---
**Author:** ![jetnet](https://avatars.discourse-cdn.com/v4/letter/j/a87d85/32.png) [@jetnet](https://discuss.elastic.co/u/jetnet)\ **Post date:** [January 22, 2017, 12:12am UTC](https://discuss.elastic.co/t/limit-access-to-dashboard/72308/3 "2017-01-22T00:12:31Z")
Isn't it an use case, where the document level security could shine? [set-security-user-processor](https://www.elastic.co/guide/en/x-pack/current/field-and-document-access-control.html#set-security-user-processor) ---
**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:** [January 22, 2017, 1:18am UTC](https://discuss.elastic.co/t/limit-access-to-dashboard/72308/4 "2017-01-22T01:18:07Z")
You'd then have to have a naming standard for all your dashboards etc to filter on accordingly. It'd be pretty rough, and not what we're ideally aiming for. ---
**Author:** ![jetnet](https://avatars.discourse-cdn.com/v4/letter/j/a87d85/32.png) [@jetnet](https://discuss.elastic.co/u/jetnet)\ **Post date:** [January 22, 2017, 3:28pm UTC](https://discuss.elastic.co/t/limit-access-to-dashboard/72308/5 "2017-01-22T15:28:39Z")
I would rather say, it'd be not a workaround, but a solution for that limitation in the current implementation (since having a good naming schema is better, than seeing an overcrowded dashboard list). But, it seems, that method is not gonna work either: Kibana framework has to use the `pipeline` parameter when ingesting data into its index. I have not found how to configure it to do that... ---
**Author:** ![Mormaii](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mormaii/32/10790_2.png) [@Mormaii](https://discuss.elastic.co/u/Mormaii)\ **Post date:** [January 23, 2017, 12:48pm UTC](https://discuss.elastic.co/t/limit-access-to-dashboard/72308/6 "2017-01-23T12:48:29Z")
It would be nice to see this implemented. Right now we have limited our users permissions by using field level security but we would like them to be able to only access certain dashboards which to me it makes the most sense. ---
**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:** [January 24, 2017, 2:44am UTC](https://discuss.elastic.co/t/limit-access-to-dashboard/72308/7 "2017-01-24T02:44:42Z")
It's something we are working on 🙂 ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [February 21, 2017, 2:44am UTC](https://discuss.elastic.co/t/limit-access-to-dashboard/72308/8 "2017-02-21T02:44:44Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.