From 3e13eb5a41aa70802c5529aad3a36657adec8476 Mon Sep 17 00:00:00 2001
From: amyjtechwriter <61687663+amyjtechwriter@users.noreply.github.com>
Date: Tue, 28 Nov 2023 11:08:01 +0000
Subject: [PATCH] [DOCS] Linking reporting and sharing page with configure
 reporting page (#171977)

## Summary

Linking the "[Reporting and
Sharing](https://www.elastic.co/guide/en/kibana/current/reporting-settings-kb.html#reporting-advanced-settings)"
and the "[Configure
reporting](https://www.elastic.co/guide/en/kibana/current/secure-reporting.html)"
documentation pages to each other as they contain information that
relate to each page. Also contains a small formatting fix to a NOTE on
the Configure reporting page.

Closes: #169065
(cherry picked from commit 0b0110a2dd8448649ab6b09672bd5f81c4daeba3)
---
 docs/setup/configuring-reporting.asciidoc | 4 +++-
 docs/user/reporting/index.asciidoc        | 2 ++
 2 files changed, 5 insertions(+), 1 deletion(-)

diff --git a/docs/setup/configuring-reporting.asciidoc b/docs/setup/configuring-reporting.asciidoc
index 903f6fdfb5afd..d8ff9e1b202b6 100644
--- a/docs/setup/configuring-reporting.asciidoc
+++ b/docs/setup/configuring-reporting.asciidoc
@@ -113,7 +113,7 @@ Granting the privilege to generate reports also grants the user the privilege to
 ==== Grant access with the role API
 With <<grant-user-access, {kib} application privileges>> enabled in Reporting, you can also use the {ref}/security-api-put-role.html[role API] to grant access to the {report-features}, using *All* privileges, or sub-feature privileges.
 
-NOTE: this [API request](https://www.elastic.co/guide/en/kibana/current/role-management-api-put.html) needs to be executed against the Kibana API endpoint
+NOTE: This link:https://www.elastic.co/guide/en/kibana/current/role-management-api-put.html[API request] needs to be executed against the link:https://www.elastic.co/guide/en/kibana/current/api.html[Kibana API endpoint].
 [source, sh]
 ---------------------------------------------------------------
 POST <kibana host>:<port>/api/_security/role/custom_reporting_user
@@ -229,3 +229,5 @@ For more information, see {ref}/notification-settings.html#ssl-notification-sett
 . Add one or more users who have access to the {report-features}.
 +
 Once you've enabled SSL for {kib}, all requests to the reporting endpoints must include valid credentials.
+
+For more information on sharing reports, direct links, and more, refer to <<reporting-getting-started, Reporting and sharing>>.
diff --git a/docs/user/reporting/index.asciidoc b/docs/user/reporting/index.asciidoc
index 8d53018dec572..676fb430b9c66 100644
--- a/docs/user/reporting/index.asciidoc
+++ b/docs/user/reporting/index.asciidoc
@@ -31,6 +31,8 @@ You access the options from the *Share* menu in the toolbar. The sharing options
 NOTE: For Elastic Cloud deployments, {kib} instances require a minimum of 2GB RAM to generate PDF or PNG reports. To
 change {kib} sizing, {ess-console}[edit the deployment].
 
+For more information on how to configure reporting in {kib}, refer to <<secure-reporting,Configure reporting in {kib}>>
+
 [float]
 [[manually-generate-reports]]
 == Create reports