# Roles, users and viewing the dashboard

**URL:** https://discuss.elastic.co/t/roles-users-and-viewing-the-dashboard/205826
**Category:** Kibana
**Created:** [October 30, 2019, 10:59am UTC](https://discuss.elastic.co/t/roles-users-and-viewing-the-dashboard/205826 "2019-10-30T10:59:28Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![\_Louw](https://avatars.discourse-cdn.com/v4/letter/_/ee7513/32.png) [@\_Louw](https://discuss.elastic.co/u/_Louw)
#### Post date: [October 30, 2019, 10:59am UTC](https://discuss.elastic.co/t/roles-users-and-viewing-the-dashboard/205826/1 "2019-10-30T10:59:28Z")

</div>

I have two dashboards - one displaying data from the client system and one displaying data from Kibanas own .security index.

I have made two roles:  
user\_data  
user\_security

I want the people in "user\_data" to be able to view the dashboard from the client system, and I want people with also the "user\_security" role to be able to view the dashboard from .security.

The dashboard with client data works fine.  
I simply can't get Kibana to view the individual visualizations from the .security dashboard. Unless the user is a superuser, all the visualizations just says "0" og "No results found".

I have even tried making a new role and copying all information from the superuser-role, but it doesn't work either.

My security role looks like this:

 ![securityrole](https://us1.discourse-cdn.com/elastic/original/3X/a/5/a50e90b91329a25e37d70dc6cdeff29043575e16.png)

Is it something with the .security index that works differently than others?

---

<div class="post-metadata">

### Author: ![Larry\_Gregory](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/larry_gregory/32/34969_2.png) [@Larry\_Gregory](https://discuss.elastic.co/u/Larry_Gregory)
#### Post date: [November 1, 2019, 11:08am UTC](https://discuss.elastic.co/t/roles-users-and-viewing-the-dashboard/205826/2 "2019-11-01T11:08:01Z")

</div>

Hey @_Louw,

Yes, the `.security` index does behave differently. It's intentionally excluded from index privileges by default, as users _typically_ do not intend for this index to be viewable by anyone.

If you need to grant access to `.security`, then you'll want to use Kibana's Role API instead, and when you specify your index privilege for `.security`, you'll want to set `allow_restricted_indices: true`. So your role might look something like:

```auto
{
   "cluster": ["all"],
   "indices" [{
       "names": [".security*"],
       "privileges": ["all"],
       "field_security": { "grant": ["*"]},
       "allow_restricted_indices": true
   }]
}

```

You can set this flag to `true` once via the API for a specific role, and then continue editing it within the Kibana role management screen, and it will remember the setting. We just don't expose this as an option in the interface currently.

---

<div class="post-metadata">

### Author: ![\_Louw](https://avatars.discourse-cdn.com/v4/letter/_/ee7513/32.png) [@\_Louw](https://discuss.elastic.co/u/_Louw)
#### Post date: [November 4, 2019, 8:55am UTC](https://discuss.elastic.co/t/roles-users-and-viewing-the-dashboard/205826/3 "2019-11-04T08:55:19Z")

</div>

Thank you! This works perfectly :).

---

<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: [December 2, 2019, 8:55am UTC](https://discuss.elastic.co/t/roles-users-and-viewing-the-dashboard/205826/4 "2019-12-02T08:55:28Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.