# Kibana 4 specific Dashboard access control by user

**URL:** <https://discuss.elastic.co/t/kibana-4-specific-dashboard-access-control-by-user/60479>\
**Category:** Kibana\
**Created:** [September 14, 2016, 9:54am UTC](https://discuss.elastic.co/t/kibana-4-specific-dashboard-access-control-by-user/60479 "2016-09-14T09:54:34Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Fernando\_Romano](https://avatars.discourse-cdn.com/v4/letter/f/82dd89/32.png) [@Fernando\_Romano](https://discuss.elastic.co/u/Fernando_Romano)\
**Post date:** [September 14, 2016, 9:54am UTC](https://discuss.elastic.co/t/kibana-4-specific-dashboard-access-control-by-user/60479/1 "2016-09-14T09:54:34Z")

</div>

Hi there,

We're using Elastic and Kibana in the Cloud environment.

We have a Dashboards for each client. Is there any way to restrict access to a client user to a specific Dashboard with Search and Time period without Discover, Visualizations and so on features?

I searched in forums and couldn't find a solution.

Thanks in advance.

---

<div class="post-metadata">

**Author:** ![tsullivan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tsullivan/32/31077_2.png) [@tsullivan](https://discuss.elastic.co/u/tsullivan)\
**Post date:** [September 14, 2016, 6:49pm UTC](https://discuss.elastic.co/t/kibana-4-specific-dashboard-access-control-by-user/60479/2 "2016-09-14T18:49:17Z")

</div>

One way to do it would be to "share" the dashboard and get the Embed code, then embed the Dashboard into another page, and give the client that new page. Then they will get just their own Dashboard and not have access to Discover, Visualize, etc.

 ![](https://us1.discourse-cdn.com/elastic/original/2X/7/70b68caad6ec422eda618dc03d44cb160f0622ec.png)

---

<div class="post-metadata">

**Author:** ![Fernando\_Romano](https://avatars.discourse-cdn.com/v4/letter/f/82dd89/32.png) [@Fernando\_Romano](https://discuss.elastic.co/u/Fernando_Romano)\
**Post date:** [September 16, 2016, 4:33pm UTC](https://discuss.elastic.co/t/kibana-4-specific-dashboard-access-control-by-user/60479/3 "2016-09-16T16:33:50Z")

</div>

Hi Tim, thanks for the answer.

We already have done that in clients backoffice. But now we have a different issue:

How t make an auto-authentication to Kibana to avoid client to enter Kibana login?

Please, remember that we're working in your cloud subscription environment.

Thanks in advance.

---

<div class="post-metadata">

**Author:** ![Joe\_Fleming](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/joe_fleming/32/3561_2.png) [@Joe\_Fleming](https://discuss.elastic.co/u/Joe_Fleming)\
**Post date:** [September 16, 2016, 5:51pm UTC](https://discuss.elastic.co/t/kibana-4-specific-dashboard-access-control-by-user/60479/4 "2016-09-16T17:51:48Z")

</div>

> How t make an auto-authentication to Kibana to avoid client to enter Kibana login?

You'd have to somehow inject authentication headers into the original request. I don't think there's a way to do this in Cloud directly, you'd have to pass requests through an external proxy server that would add Basic auth headers or handle some other Shield-supported authentication scheme.

Keep in mind then that requests that go through that server are unprotected, and would be like Kibana running without Shield.

---

<div class="post-metadata">

**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:38pm UTC](https://discuss.elastic.co/t/kibana-4-specific-dashboard-access-control-by-user/60479/5 "2017-07-06T13:38:53Z")

</div>

Closed on July 6, 2017, 1:38pm UTC