From c7ec77f25feb9ca251781d118c9011d0899ad285 Mon Sep 17 00:00:00 2001
From: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
Date: Tue, 28 Nov 2023 06:31:10 -0500
Subject: [PATCH] [8.11] [DOCS] Linking reporting and sharing page with
 configure reporting page (#171977) (#172048)

# Backport

This will backport the following commits from `main` to `8.11`:
- [[DOCS] Linking reporting and sharing page with configure reporting
page (#171977)](https://github.com/elastic/kibana/pull/171977)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT
[{"author":{"name":"amyjtechwriter","email":"61687663+amyjtechwriter@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-11-28T11:08:01Z","message":"[DOCS]
Linking reporting and sharing page with configure reporting page
(#171977)\n\n## Summary\r\n\r\nLinking the \"[Reporting
and\r\nSharing](https://www.elastic.co/guide/en/kibana/current/reporting-settings-kb.html#reporting-advanced-settings)\"\r\nand
the
\"[Configure\r\nreporting](https://www.elastic.co/guide/en/kibana/current/secure-reporting.html)\"\r\ndocumentation
pages to each other as they contain information that\r\nrelate to each
page. Also contains a small formatting fix to a NOTE on\r\nthe Configure
reporting page.\r\n\r\nCloses:
#169065","sha":"0b0110a2dd8448649ab6b09672bd5f81c4daeba3","branchLabelMapping":{"^v8.12.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Docs","Feature:Reporting","release_note:skip","docs","v8.12.0","v8.11.2"],"number":171977,"url":"https://github.com/elastic/kibana/pull/171977","mergeCommit":{"message":"[DOCS]
Linking reporting and sharing page with configure reporting page
(#171977)\n\n## Summary\r\n\r\nLinking the \"[Reporting
and\r\nSharing](https://www.elastic.co/guide/en/kibana/current/reporting-settings-kb.html#reporting-advanced-settings)\"\r\nand
the
\"[Configure\r\nreporting](https://www.elastic.co/guide/en/kibana/current/secure-reporting.html)\"\r\ndocumentation
pages to each other as they contain information that\r\nrelate to each
page. Also contains a small formatting fix to a NOTE on\r\nthe Configure
reporting page.\r\n\r\nCloses:
#169065","sha":"0b0110a2dd8448649ab6b09672bd5f81c4daeba3"}},"sourceBranch":"main","suggestedTargetBranches":["8.11"],"targetPullRequestStates":[{"branch":"main","label":"v8.12.0","labelRegex":"^v8.12.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/171977","number":171977,"mergeCommit":{"message":"[DOCS]
Linking reporting and sharing page with configure reporting page
(#171977)\n\n## Summary\r\n\r\nLinking the \"[Reporting
and\r\nSharing](https://www.elastic.co/guide/en/kibana/current/reporting-settings-kb.html#reporting-advanced-settings)\"\r\nand
the
\"[Configure\r\nreporting](https://www.elastic.co/guide/en/kibana/current/secure-reporting.html)\"\r\ndocumentation
pages to each other as they contain information that\r\nrelate to each
page. Also contains a small formatting fix to a NOTE on\r\nthe Configure
reporting page.\r\n\r\nCloses:
#169065","sha":"0b0110a2dd8448649ab6b09672bd5f81c4daeba3"}},{"branch":"8.11","label":"v8.11.2","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: amyjtechwriter <61687663+amyjtechwriter@users.noreply.github.com>
---
 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