From 060ca7693721378e75064a79993046171eff9720 Mon Sep 17 00:00:00 2001
From: Fabio Busatto <52658645+bytebilly@users.noreply.github.com>
Date: Fri, 3 Nov 2023 17:47:21 +0100
Subject: [PATCH] =?UTF-8?q?[DOCS]=C2=A0Clarify=20required=20privileges=20t?=
 =?UTF-8?q?o=20create=20CSV=20reports=20when=20using=20index=20aliases=20(?=
 =?UTF-8?q?#170524)?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

## Summary

If a CSV export is performed on an index alias, it also requires read
access to underlying indices.
This PR adds a note in Kibana docs to make users aware of this
requirement.

(cherry picked from commit ef67add16c2baadc15ca0a1c7d7e4e1322a8fe36)
---
 docs/setup/configuring-reporting.asciidoc | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/docs/setup/configuring-reporting.asciidoc b/docs/setup/configuring-reporting.asciidoc
index 3cb20866d7753..903f6fdfb5afd 100644
--- a/docs/setup/configuring-reporting.asciidoc
+++ b/docs/setup/configuring-reporting.asciidoc
@@ -72,6 +72,8 @@ NOTE: If you use the default settings, you can still create a custom role that g
 +
 Access to data is an index-level privilege. For each index that contains the data you want to include in reports, add a line, then give each index `read` and `view_index_metadata` privileges.
 +
+NOTE: If you use index aliases, you must also grant `read` and `view_index_metadata` privileges to underlying indices to generate CSV reports.
++
 For more information, refer to {ref}/security-privileges.html[Security privileges].
 
 . Add the {kib} privileges.