# Read Only to Everything in Elastic/Kibana **URL:** \ **Category:** Kibana\ **Created:** [January 15, 2024, 4:34pm UTC](https://discuss.elastic.co/t/read-only-to-everything-in-elastic-kibana/351089 "2024-01-15T16:34:55Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![ryans](https://avatars.discourse-cdn.com/v4/letter/r/90db22/32.png) [@ryans](https://discuss.elastic.co/u/ryans)\ **Post date:** [January 15, 2024, 4:34pm UTC](https://discuss.elastic.co/t/read-only-to-everything-in-elastic-kibana/351089/1 "2024-01-15T16:34:55Z")
Is there a quick/easy setting in Kibana Roles that would give a user full read only permissions to everything within the Elastic Stack? Basically, I want to create a user with a Role where they can see everything an admin can, but can't take any actions at all. ---
**Author:** ![carly.richmond](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/carly.richmond/32/104935_2.png) [@carly.richmond](https://discuss.elastic.co/u/carly.richmond)\ **Post date:** [January 17, 2024, 10:27am UTC](https://discuss.elastic.co/t/read-only-to-everything-in-elastic-kibana/351089/2 "2024-01-17T10:27:55Z")
Hi @ryans, Have you tried creating a role with 'read' as the priviledge for all features [as per the screenshot in the documentation](https://www.elastic.co/guide/en/kibana/8.11/kibana-privileges.html)? ---
**Author:** ![sholzhauer](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sholzhauer/32/110282_2.png) [@sholzhauer](https://discuss.elastic.co/u/sholzhauer)\ **Post date:** [January 17, 2024, 12:02pm UTC](https://discuss.elastic.co/t/read-only-to-everything-in-elastic-kibana/351089/3 "2024-01-17T12:02:58Z")
As @carly.richmond said you can create a role which achieves this for ~95%. There are some features which require admin/superuser privileges to access which cannot be achieved with `read` permissions. Your role will need the following things: 1. Kibana permissions 2. cluster read permissions 3. index read permissions. ---
**Author:** ![ryans](https://avatars.discourse-cdn.com/v4/letter/r/90db22/32.png) [@ryans](https://discuss.elastic.co/u/ryans)\ **Post date:** [January 17, 2024, 2:07pm UTC](https://discuss.elastic.co/t/read-only-to-everything-in-elastic-kibana/351089/4 "2024-01-17T14:07:51Z")
Thank you for that. I added those, but it doesn't help with the Elasticsearch pieces. ---
**Author:** ![ryans](https://avatars.discourse-cdn.com/v4/letter/r/90db22/32.png) [@ryans](https://discuss.elastic.co/u/ryans)\ **Post date:** [January 17, 2024, 3:04pm UTC](https://discuss.elastic.co/t/read-only-to-everything-in-elastic-kibana/351089/5 "2024-01-17T15:04:38Z")
Thank you for that additional information. I did add some of those and got closer, but noticed I need to include some enterprise\* roles to see App Search engines. So while there is a way to get the perms I want, apparently there is no easy "grant read to everything" option. It still takes a lot of tinkering. ---
**Author:** ![ryans](https://avatars.discourse-cdn.com/v4/letter/r/90db22/32.png) [@ryans](https://discuss.elastic.co/u/ryans)\ **Post date:** [January 17, 2024, 9:03pm UTC](https://discuss.elastic.co/t/read-only-to-everything-in-elastic-kibana/351089/6 "2024-01-17T21:03:27Z")
I discovered today while working with support that users that are created within App Search get hidden privileges that can not be (or not obviously) found in Kibana. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [February 14, 2024, 9:03pm UTC](https://discuss.elastic.co/t/read-only-to-everything-in-elastic-kibana/351089/7 "2024-02-14T21:03:31Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.