From d53be1fb55768bb76217868eaaae80776690ae62 Mon Sep 17 00:00:00 2001
From: gchaps <33642766+gchaps@users.noreply.github.com>
Date: Tue, 7 Jan 2020 08:37:58 -0800
Subject: [PATCH] [DOCS][Reporting] Adds info about using a custom reporting
 index (#54052)

* [DOCS][Reporting] Adds info about using a custom reporting index

* [DOCS] Incorporates edits into reporting security doc
---
 docs/user/security/reporting.asciidoc | 24 ++++++++++++++++++++++++
 1 file changed, 24 insertions(+)

diff --git a/docs/user/security/reporting.asciidoc b/docs/user/security/reporting.asciidoc
index 86599be9af375..c2ed295e83ce9 100644
--- a/docs/user/security/reporting.asciidoc
+++ b/docs/user/security/reporting.asciidoc
@@ -57,6 +57,30 @@ that provides read and write privileges in
 Go to *Management > Users*, add a new user, and assign the user the built-in
 `reporting_user` role and your new custom role, `custom_reporting_user`.
 
+[float]
+==== With a custom index
+
+If you are using Reporting with a custom index,
+the `xpack.reporting.index` setting should begin 
+with `.reporting-*`. The default {kib} system user has
+`all` privileges against the `.reporting-*` pattern of indices.
+
+[source,js]
+xpack.reporting.index: '.reporting-custom-index'
+
+If you use a different pattern for the `xpack.reporting.index` setting,
+you must create a custom role with appropriate access to the index, similar
+to the following:
+
+. Go to *Management > Roles*, and click *Create role*.
+. Name the role `custom-reporting-user`.
+. Specify the custom index and assign it the `all` index privilege.
+. Go to *Management > Users* and create a new user with
+the `kibana_system` role and the `custom-reporting-user` role.
+. Configure {kib} to use the new account:
+[source,js]
+elasticsearch.username: 'custom_kibana_system'
+
 [float]
 [[reporting-roles-user-api]]
 ==== With the user API