First draft updates (#2736)

Author: joepeeples

docs/getting-started/configure-integration-policy.asciidoc

@@ -9,7 +9,11 @@ event filters, host isolation exceptions, and blocked applications to meet your
 
 You can also create multiple {elastic-defend} integration policies to maintain unique configuration profiles. To create an additional {elastic-defend} integration policy, go to **Management** -> **Integrations**, then follow the steps for <<add-security-integration, adding the {elastic-defend} integration>>.
 
-NOTE: You must have the {kib} `superuser` role to configure an integration policy in the {security-app}.
+.Requirements
+[sidebar]
+--
+You must have the `superuser` {ref}/built-in-roles.html[built-in user role] to configure an integration policy in the {security-app}.
+--
 
 To configure an integration policy:
 

docs/getting-started/install-endpoint.asciidoc

@@ -3,7 +3,13 @@
 
 Like other Elastic integrations, {elastic-defend} can be integrated into the {agent} using {fleet-guide}/fleet-overview.html[{fleet}]. Upon configuration, the integration allows the {agent} to monitor events on your host and send data to the {security-app}.
 
-NOTE: To configure the {elastic-defend} integration on the {agent}, you must have permission to use {fleet} in {kib}. You must also have admin permissions in {kib} to access the **Endpoints** page in the {security-app}.
+.Requirements
+[sidebar]
+--
+* To configure the {elastic-defend} integration on the {agent}, you must have permission to use {fleet} in {kib}. 
+
+* You must have the `superuser` {ref}/built-in-roles.html[built-in user role] to configure an integration policy and to access the **Endpoints** page in the {security-app}.
+--
 
 [discrete]
 [[security-before-you-begin]]