# Kibana permissions - different behavior between read and custom privileges **URL:** \ **Category:** Kibana\ **Created:** [February 19, 2026, 11:51am UTC](https://discuss.elastic.co/t/kibana-permissions-different-behavior-between-read-and-custom-privileges/385112 "2026-02-19T11:51:39Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Ror](https://avatars.discourse-cdn.com/v4/letter/r/ee59a6/32.png) [@Ror](https://discuss.elastic.co/u/Ror)\ **Post date:** [February 19, 2026, 11:51am UTC](https://discuss.elastic.co/t/kibana-permissions-different-behavior-between-read-and-custom-privileges/385112/1 "2026-02-19T11:51:40Z")
I recently migrated from elastic cloud to elastic cloud on kubernetes. In order to migrate, I restored a snapshot with all the users and roles. I wanted to make a change to a custom role I created to allow a user to create CSV reports. When I changed the Kibana permissions from read to all to the discover feature, the user stopped to have access to the entire Analytics. I tested it a bit and I can see that creating a custom role with All or Read kibana privileges gives the user access to discover and the other features, but if I configure a Custom Kibana privilege with all read access (basically doing the same thing as Read privilege), the user does not have access to discover. Is it a bug or am I missing something ? TLDR : This gives access to discover : ![image](https://us1.discourse-cdn.com/elastic/original/3X/5/8/5876578a01e771ea24684304b9fb3668d91395b6.png) But this does not : ![image](https://us1.discourse-cdn.com/elastic/original/3X/6/b/6bc197c539243abf304f8c13363728d982a80281.png) Even though they are supposed to give the same access ---
**Author:** ![Ror](https://avatars.discourse-cdn.com/v4/letter/r/ee59a6/32.png) [@Ror](https://discuss.elastic.co/u/Ror)\ **Post date:** [February 19, 2026, 1:50pm UTC](https://discuss.elastic.co/t/kibana-permissions-different-behavior-between-read-and-custom-privileges/385112/2 "2026-02-19T13:50:58Z")
For some reason, `xpack.reporting.roles.enabled` was set to `false`. Enabling it solved the issue