diff --git a/docs/en/ingest-management/data-streams.asciidoc b/docs/en/ingest-management/data-streams.asciidoc
index aa9630310..5c9746d71 100644
--- a/docs/en/ingest-management/data-streams.asciidoc
+++ b/docs/en/ingest-management/data-streams.asciidoc
@@ -42,6 +42,13 @@ A `namespace` can be up to 100 bytes in length (multibyte characters will count
 Using a namespace makes it easier to search data from a given source by using a matching pattern.
 You can also use matching patterns to give users access to data when creating user roles.
 // Corresponds to the `data_stream.dataset` field.
++
+By default the namespace defined for an {agent} policy is propagated to all integrations in that policy. if you'd like to define a more granular namespace for a policy:
+
+. In {kib}, go to **Management -> Integrations**.
+. Open the **Integration policies** tab.
+. From the **Actions** menu next to the integration that you'd like to update, select *Edit integration*.
+. Open the advanced options and update the **Namespace** field. Data streams from the integration will now use the specified namespace rather than the default namespace inherited from the {agent} policy.
 
 The naming scheme separates each components with a `-` character: