# Reporting\_user deprecated and don't want to grant "all" access on discover/dashboard **URL:** \ **Category:** Kibana\ **Tags:** elastic-stack-reporting\ **Created:** [August 30, 2022, 8:08am UTC](https://discuss.elastic.co/t/reporting-user-deprecated-and-dont-want-to-grant-all-access-on-discover-dashboard/313226 "2022-08-30T08:08:21Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![rmacd](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rmacd/32/110158_2.png) [@rmacd](https://discuss.elastic.co/u/rmacd)\ **Post date:** [August 30, 2022, 8:08am UTC](https://discuss.elastic.co/t/reporting-user-deprecated-and-dont-want-to-grant-all-access-on-discover-dashboard/313226/1 "2022-08-30T08:08:21Z")
Hi - on 7.17.x, basic / OSS. Older versions of Kibana permitted manipulation of the `reporting_user` privilege so that read-only users could be granted access to reporting. Now ([[1](https://www.elastic.co/guide/en/kibana/7.17/reporting-settings-kb.html)], [[2](https://discuss.elastic.co/t/role-reporting-user-is-deprecated-please-use-kibana-feature-privileges-instead/294593)]) the role is "cusomisable" via the UI, but _only by granting "all" access to dashboard and/or discover_. The problem is that this doesn't work in a situation where folks are being given read-only access to a dashboard: this would then permit them to modify the dashboard (which we don't want). Have I got that right? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [September 27, 2022, 8:08am UTC](https://discuss.elastic.co/t/reporting-user-deprecated-and-dont-want-to-grant-all-access-on-discover-dashboard/313226/2 "2022-09-27T08:08:44Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.