diff --git a/docs/en/ingest-management/fleet/fleet-integration-outputs.asciidoc b/docs/en/ingest-management/fleet/fleet-integration-outputs.asciidoc
new file mode 100644
index 000000000..f44c1c99b
--- /dev/null
+++ b/docs/en/ingest-management/fleet/fleet-integration-outputs.asciidoc
@@ -0,0 +1,12 @@
+:type: output-elasticsearch-fleet-settings
+
+[[fleet-integration-outputs]]
+= Setting outputs per integration
+
+If you have an `Enterprise` link:https://www.elastic.co/subscriptions[{stack} subscription], you can configure {agent} data to be sent to different outputs for different integration policies. Integration-level outputs are very useful for certain scenarios. For example:
+
+* You can may want to send security logs monitored by an {agent} to one {ls} output, while informational logs are sent to a another {ls} output.
+* If you operate multiple {beats} on a system and want to migrate these to {agent}, integration-level outputs enable you to maintain the distinct outputs that are currently used by each Beat.
+
+
+Order of precedence...
\ No newline at end of file
diff --git a/docs/en/ingest-management/index.asciidoc b/docs/en/ingest-management/index.asciidoc
index e77ff5f90..02d75f28d 100644
--- a/docs/en/ingest-management/index.asciidoc
+++ b/docs/en/ingest-management/index.asciidoc
@@ -109,6 +109,8 @@ include::fleet/fleet-settings-output-kafka.asciidoc[leveloffset=+3]
 
 include::fleet/fleet-settings-remote-elasticsearch.asciidoc[leveloffset=+3]
 
+include::fleet/fleet-integration-outputs.asciidoc[leveloffset=+3]
+
 include::fleet/fleet-settings-changing-outputs.asciidoc[leveloffset=+3]
 
 include::fleet/fleet-manage-agents.asciidoc[leveloffset=+2]