[DOCS] Fleet managed integrations content (#970)

* Managed integrations badge

* corrections

* Typo corrections and a bit of re-wording for clarity

docs/en/ingest-management/index.asciidoc

@@ -189,6 +189,8 @@ include::integrations/view-integration-assets.asciidoc[leveloffset=+2]
 
 include::integrations/upgrade-integration.asciidoc[leveloffset=+2]
 
+include::integrations/managed-integrations-content.asciidoc[leveloffset=+2]
+
 include::data-streams.asciidoc[leveloffset=+2]
 
 include::processors/processors.asciidoc[leveloffset=+1]

docs/en/ingest-management/integrations/integrations.asciidoc

@@ -60,4 +60,4 @@ too.
 The *Integrations* app in {kib} needs access to the public {package-registry} to
 discover integrations. If your deployment has network restrictions, you can
 {fleet-guide}/air-gapped.html#air-gapped-diy-epr[deploy your own self-managed {package-registry}].
-====
+====

docs/en/ingest-management/integrations/managed-integrations-content.asciidoc

@@ -0,0 +1,20 @@
+[[managed-integrations-content]]
+= Managed integrations content
+
+++++
+<titleabbrev>Managed integrations content</titleabbrev>
+++++
+
+Most integration content installed by {fleet} isn’t editable. This content is tagged with a **Managed** badge in the {kib} UI. Managed content itself cannot be edited or deleted, however managed visualizations, dashboards, and saved searches can be cloned.   
+
+[role="screenshot"]
+image::images/system-managed.png[An image of the new managed badge.]
+
+When a managed dashboard is cloned, any linked or referenced panels become part of the clone without relying on external sources. The panels are integrated into the cloned dashboard as stand alone components. For example, with a cloned dashboard, the cloned panels become entirely self-contained copies without any dependencies on the original configuration. Clones can be customized and modified without accidentally affecting the original.
+
+[NOTE]
+====
+The cloned managed content retains the managed badge, but is independent from the original. 
+====
+
+With managed content relating to specific visualization editor such as Lens, TSVB, and Maps, the clones retain the original reference configurations. To clone the visualization, view it in the editor then begin to make edits. Once finished editing you are prompted to save the edits as a new visualization. The same applies to editing any saved searches in a managed visualization.