[DOCS] Fixes inconsistency with role management link (#121351)

* [DOCS] Fixes inconsistency with role management link

* Update docs/redirects.asciidoc

Co-authored-by: Lisa Cawley <lcawley@elastic.co>

Co-authored-by: Lisa Cawley <lcawley@elastic.co>

docs/concepts/data-views.asciidoc

@@ -12,10 +12,10 @@ or all indices that contain your data.
 [[data-views-read-only-access]]
 === Required permissions
 
-* Access to *Data Views* requires the <<xpack-kibana-role-management, {kib} privilege>>
+* Access to *Data Views* requires the <<kibana-role-management, {kib} privilege>>
 `Data View Management`.
 
-* To create a data view, you must have the <<xpack-kibana-role-management,{es} privilege>>
+* To create a data view, you must have the <<kibana-role-management,{es} privilege>>
 `view_index_metadata`.
 
 * If a read-only indicator appears in {kib}, you have insufficient privileges

docs/management/connectors/action-types/index.asciidoc

@@ -74,7 +74,7 @@ Example of the index document for Index Threshold rule:
     "rule_name": "{{ruleName}}",
     "alert_id": "{{alertId}}",
     "context_message": "{{context.message}}"
-} 
+}
 --------------------------------------------------
 
 Example of creating a test index using the API.
@@ -108,7 +108,7 @@ experimental[] {kib} offers a preconfigured index connector to facilitate indexi
 This functionality is experimental and may be changed or removed completely in a future release.
 ==================================================
 
-To use this connector, set the <<action-settings, `xpack.actions.preconfiguredAlertHistoryEsIndex`>> configuration to `true`. 
+To use this connector, set the <<action-settings, `xpack.actions.preconfiguredAlertHistoryEsIndex`>> configuration to `true`.
 
 ```js
   xpack.actions.preconfiguredAlertHistoryEsIndex: true
@@ -123,11 +123,11 @@ Documents are indexed using a preconfigured schema that captures the <<defining-
 
 [IMPORTANT]
 ==============================================
-To write documents to the preconfigured index, you must have `all` or `write` privileges to the `kibana-alert-history-*` indices. Refer to <<xpack-kibana-role-management>> for more information.
+To write documents to the preconfigured index, you must have `all` or `write` privileges to the `kibana-alert-history-*` indices. Refer to <<kibana-role-management>> for more information.
 ==============================================
 
 [NOTE]
 ==================================================
 The `kibana-alert-history-*` indices are not configured to use ILM so they must be maintained manually. If the index size grows large,
 consider using the {ref}/docs-delete-by-query.html[delete by query] API to clean up older documents in the index.
-==================================================
+==================================================

docs/maps/import-geospatial-data.asciidoc

@@ -17,7 +17,7 @@ The {stack-security-features} provide roles and privileges that control which us
 You can manage your roles, privileges, and
 spaces in **{stack-manage-app}** in {kib}. For more information, see
 {ref}/security-privileges.html[Security privileges],
-<<kibana-privileges, {kib} privileges>>, and <<xpack-kibana-role-management, {kib} role management>>.
+<<kibana-privileges, {kib} privileges>>, and <<kibana-role-management, {kib} role management>>.
 
 To upload GeoJSON files in {kib} with *Maps*, you must have:
 

docs/redirects.asciidoc

@@ -440,3 +440,8 @@ This content has moved. Refer to <<data-views-runtime-field-api-upsert>>.
 == Index patterns has been renamed to data views.
 
 This content has moved. Refer to <<data-views-api-update>>.
+
+[role="exclude",id="xpack-kibana-role-management"]
+== Kibana role management.
+
+This content has moved. Refer to <<kibana-role-management>>.

docs/user/management.asciidoc

@@ -106,7 +106,7 @@ a| <<xpack-security, Users>>
 Add or delete users and assign roles that give users
 specific privileges.
 
-| <<xpack-kibana-role-management, Roles>>
+| <<kibana-role-management, Roles>>
 |View the roles that exist on your cluster. Customize
 the actions that a user with the role can perform, on a cluster, index, and space level.
 

docs/user/security/authorization/index.asciidoc

@@ -23,7 +23,7 @@ Whichever approach you use, be careful when granting cluster privileges and inde
 cluster, and {kib} spaces do not prevent you from granting users of two different tenants access to the same index.
 
 [role="xpack"]
-[[xpack-kibana-role-management]]
+[[kibana-role-management]]
 === {kib} role management
 
 Roles are a collection of privileges that allow you to perform actions in {kib} and {es}. Users are not directly granted privileges, but are instead assigned one or more roles that describe the desired level of access. When you assign a user multiple roles, the user receives a union of the roles’ privileges. This means that you cannot reduce the privileges of a user by assigning them an additional role. You must instead remove or edit one of their existing roles.

docs/user/security/tutorials/how-to-secure-access-to-kibana.asciidoc

@@ -131,6 +131,6 @@ This guide is an introduction to {kib}'s security features. Check out these addi
 
 * View the <<kibana-authentication, authentication guide>> to learn more about single-sign on and other login features.
 
-* View the <<xpack-kibana-role-management, authorization guide>> to learn more about authorizing access to {kib}'s features.
+* View the <<kibana-role-management, authorization guide>> to learn more about authorizing access to {kib}'s features.
 
 Still have questions? Ask  on our https://discuss.elastic.co/c/kibana[Kibana discuss forum] and a fellow community member or Elastic engineer will help out.