# How to restrict developers to only read and edit dashboards?

**URL:** https://discuss.elastic.co/t/how-to-restrict-developers-to-only-read-and-edit-dashboards/202108
**Category:** Kibana
**Tags:** elastic-stack-security
**Created:** [October 3, 2019, 7:54am UTC](https://discuss.elastic.co/t/how-to-restrict-developers-to-only-read-and-edit-dashboards/202108 "2019-10-03T07:54:09Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![soumendra](https://avatars.discourse-cdn.com/v4/letter/s/b2d939/32.png) [@soumendra](https://discuss.elastic.co/u/soumendra)
#### Post date: [October 3, 2019, 7:54am UTC](https://discuss.elastic.co/t/how-to-restrict-developers-to-only-read-and-edit-dashboards/202108/1 "2019-10-03T07:54:09Z")

</div>

ES Version: 7.3.2  
Tier: Platinum X-Pack

I have given all users **kibana\_dashboard\_only** access for an OIDC realm.  
Now to edit the dashboards in Kibana, I am giving 'superuser' access to developers. There comes the risk of accessing the user role management parts.

Is there any way to restrict the developers to only read and edit the Kibana dashboards and not to interfere with User role management?

---

<div class="post-metadata">

### Author: ![TimV](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/timv/32/13162_2.png) [@TimV](https://discuss.elastic.co/u/TimV)
#### Post date: [October 4, 2019, 5:50am UTC](https://discuss.elastic.co/t/how-to-restrict-developers-to-only-read-and-edit-dashboards/202108/2 "2019-10-04T05:50:12Z")

</div>

> [@soumendra](#):
>
> I am giving 'superuser' access to developers.  
> ...  
> Is there any way to restrict the developers to only read and edit the Kibana dashboards and not to interfere with User role management?

Don't give the developers `superuser` access.  
You should create a new role with the specific privileges that they need. If you don't give them the `all` or `manage_security` cluster privileges then they won't be permitted to use security management.

---

<div class="post-metadata">

### Author: ![soumendra](https://avatars.discourse-cdn.com/v4/letter/s/b2d939/32.png) [@soumendra](https://discuss.elastic.co/u/soumendra)
#### Post date: [October 7, 2019, 4:23am UTC](https://discuss.elastic.co/t/how-to-restrict-developers-to-only-read-and-edit-dashboards/202108/3 "2019-10-07T04:23:07Z")

</div>

Thanks TimV,

As per your suggestion, I have created a role, `developer` and given all the cluster roles except `all` and `manage_security`. Still the user assigned to the `developer` role is unable to edit any of the dashboards.  
Then I have given the user `kibana_system`, `kibana_user` access along with the `developer` access. However, no change. The user unable to edit the dashboards.

Note: All the users are SSO enabled (Open ID) and by default to all users I have given `kibana_dashboard_only_user` access.

Do you need any other info to help me on this?

---

<div class="post-metadata">

### Author: ![soumendra](https://avatars.discourse-cdn.com/v4/letter/s/b2d939/32.png) [@soumendra](https://discuss.elastic.co/u/soumendra)
#### Post date: [October 16, 2019, 12:53pm UTC](https://discuss.elastic.co/t/how-to-restrict-developers-to-only-read-and-edit-dashboards/202108/4 "2019-10-16T12:53:48Z")

</div>

By giving all users default access as `kibana_dashboard_only_user` was the issue. I thought if I add more roles on top of this role, Elasticsearch will take the union of all the roles.

Unfortunately for this case it was not the case. `kibana_dashboard_only_user` seems like an exclusive role, where unions will not work unless or until the user is a `superuser`.  
I removed this default role from the `OpenID` realm, and **it worked**.  
Thanks.

---

<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: [November 13, 2019, 12:53pm UTC](https://discuss.elastic.co/t/how-to-restrict-developers-to-only-read-and-edit-dashboards/202108/5 "2019-11-13T12:53:53Z")

</div>

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