diff --git a/docs/reference/redirects.asciidoc b/docs/reference/redirects.asciidoc
index 56a6560080795..6e53567ccf24b 100644
--- a/docs/reference/redirects.asciidoc
+++ b/docs/reference/redirects.asciidoc
@@ -498,3 +498,12 @@ guide to the {painless}/index.html[Painless Scripting Language].
 
 See the {painless}/painless-api-reference.html[Painless API Reference] in
 the guide to the {painless}/index.html[Painless Scripting Language].
+
+[role="exclude", id="security-api-roles"]
+=== Role management APIs
+
+You can use the following APIs to add, remove, and retrieve roles in the native realm:
+
+* <<security-api-put-role,Create role>>, <<security-api-delete-role,Delete role>>
+* <<security-api-clear-role-cache,Clear roles cache>>
+* <<security-api-get-role,Get roles>>
\ No newline at end of file
diff --git a/x-pack/docs/en/rest-api/security.asciidoc b/x-pack/docs/en/rest-api/security.asciidoc
index 7d2fc7101f1b1..476c9b95bfda3 100644
--- a/x-pack/docs/en/rest-api/security.asciidoc
+++ b/x-pack/docs/en/rest-api/security.asciidoc
@@ -13,6 +13,7 @@ You can use the following APIs to perform {security} activities.
 * <<security-api-users>>
 
 [float]
+[[security-role-apis]]
 === Roles
 
 You can use the following APIs to add, remove, and retrieve roles in the native realm:
@@ -29,7 +30,6 @@ include::security/create-roles.asciidoc[]
 include::security/delete-roles.asciidoc[]
 include::security/get-roles.asciidoc[]
 include::security/privileges.asciidoc[]
-include::security/roles.asciidoc[]
 include::security/role-mapping.asciidoc[]
 include::security/ssl.asciidoc[]
 include::security/tokens.asciidoc[]
diff --git a/x-pack/docs/en/rest-api/security/get-roles.asciidoc b/x-pack/docs/en/rest-api/security/get-roles.asciidoc
index fa6e91b519b6f..433617c0c43ff 100644
--- a/x-pack/docs/en/rest-api/security/get-roles.asciidoc
+++ b/x-pack/docs/en/rest-api/security/get-roles.asciidoc
@@ -58,7 +58,6 @@ role. If the role is not defined in the native realm, the request returns 404.
           "grant" : [ "title", "body" ]}
       }   
     ],
-    "applications" : [ ],
     "run_as" : [ "other_user" ],
     "metadata" : {
       "version" : 1
diff --git a/x-pack/docs/en/rest-api/security/role-mapping.asciidoc b/x-pack/docs/en/rest-api/security/role-mapping.asciidoc
index 3844e30c62dc0..c8006346d4e8f 100644
--- a/x-pack/docs/en/rest-api/security/role-mapping.asciidoc
+++ b/x-pack/docs/en/rest-api/security/role-mapping.asciidoc
@@ -22,7 +22,7 @@ Role mappings have _rules_ that identify users and a list of _roles_ that are
 granted to those users.
 
 NOTE: This API does not create roles. Rather, it maps users to existing roles.
-Roles can be created by using <<security-api-roles, Role Management APIs>> or
+Roles can be created by using <<security-role-apis,role management APIs>> or
 {xpack-ref}/defining-roles.html#roles-management-file[roles files].
 
 The role mapping rule is a logical condition that is expressed using a JSON DSL.
diff --git a/x-pack/docs/en/rest-api/security/roles.asciidoc b/x-pack/docs/en/rest-api/security/roles.asciidoc
deleted file mode 100644
index ada8198a377af..0000000000000
--- a/x-pack/docs/en/rest-api/security/roles.asciidoc
+++ /dev/null
@@ -1,9 +0,0 @@
-[role="xpack"]
-[[security-api-roles]]
-=== Role management APIs
-
-You can use the following APIs to add, remove, and retrieve roles in the native realm:
-
-* <<security-api-put-role,Create role>>, <<security-api-delete-role,Delete role>>
-* <<security-api-clear-role-cache,Clear roles cache>>
-* <<security-api-get-role,Get roles>>
diff --git a/x-pack/docs/en/security/authorization/managing-roles.asciidoc b/x-pack/docs/en/security/authorization/managing-roles.asciidoc
index 4d9d539a3dc96..f550c900edce0 100644
--- a/x-pack/docs/en/security/authorization/managing-roles.asciidoc
+++ b/x-pack/docs/en/security/authorization/managing-roles.asciidoc
@@ -130,7 +130,7 @@ manage roles, log in to {kib} and go to *Management / Elasticsearch / Roles*.
 The _Role Management APIs_ enable you to add, update, remove and retrieve roles
 dynamically. When you use the APIs to manage roles in the `native` realm, the
 roles are stored in an internal {es} index. For more information and examples, 
-see {ref}/security-api-roles.html[role management APIs]. 
+see {ref}/security-api.html#security-role-apis[role management APIs]. 
 
 [float]
 [[roles-management-file]]
diff --git a/x-pack/docs/en/security/authorization/mapping-roles.asciidoc b/x-pack/docs/en/security/authorization/mapping-roles.asciidoc
index 5bac1f59e2aca..36f3a1f27f346 100644
--- a/x-pack/docs/en/security/authorization/mapping-roles.asciidoc
+++ b/x-pack/docs/en/security/authorization/mapping-roles.asciidoc
@@ -18,7 +18,7 @@ the API, and other roles that are mapped through files.
 
 When you use role-mappings, you assign existing roles to users.
 The available roles should either be added using the
-{ref}/security-api-roles.html[role management APIs] or defined in the
+{ref}/security-api.html#security-role-apis[role management APIs] or defined in the
 <<roles-management-file, roles file>>. Either role-mapping method can use
 either role management method. For example, when you use the role mapping API,
 you are able to map users to both API-managed roles and file-managed roles