[Streams] Add section on managed assets (#3679)

This PR closes #3624 and adds section on managed Streams assets.

---------

Co-authored-by: Nastasha Solomon <79124755+nastasha-solomon@users.noreply.github.com>

Author: mdbirnstiehl

solutions/observability/streams/management/advanced.md

@@ -26,19 +26,19 @@ Features provide useful information for AI processes, such as significant events
 
 ## Index configuration [streams-advanced-index-config]
 
-:::{note}
-Processing and schema changes should typically be done through the Streams interface, and none of these configuration processes are required. This feature mainly exists to help advanced users maintain familiar workflows.
+:::{Important}
+Avoid editing components marked as **managed** or any per-data-stream mappings and settings. Processing and schema changes should typically be done through the Streams interface or API, and none of these configuration processes are required. This feature mainly exists to help advanced users maintain familiar workflows.
 :::
 
-For classic streams, you can manually configure:
+For classic streams, you can access the following components:
 
 - [Index templates](../../../../manage-data/data-store/templates.md#index-templates)
 - [Component templates](../../../../manage-data/data-store/templates.md#component-templates)
 - [Pipelines](../../../../manage-data/ingest/transform-enrich.md)
-- [Data streams](../../../../manage-data/data-store/data-streams.md).
+- [Data streams](../../../../manage-data/data-store/data-streams.md)
 
-For both wired ({applies_to}`stack: preview 9.2`) and classic streams, you can manually configure:
+For both wired ({applies_to}`stack: preview 9.2` {applies_to}`serverless: preview`) and classic streams, you can manually configure:
 
 - **Shards:** Control how the index is split across nodes. More shards can improve parallelism but may increase overhead.
 - **Replicas:** Define how many copies of the data exist. More replicas improve resilience and read performance but increase storage usage.
-- **Refresh interval:** Control how frequently new data becomes visible for search. A longer interval reduces resource usage; a short one makes data searchable sooner.
+- **Refresh interval:** Control how frequently new data becomes visible for search. A longer interval reduces resource usage; a short one makes data searchable sooner.

solutions/observability/streams/streams.md

@@ -37,6 +37,11 @@ Wired streams:
 
 For more information, refer to [sending data to wired streams](./wired-streams.md).
 
+## Managed components
+When you configure classic or wired streams through the Streams UI or [Streams API](#streams-api), {{es}}-level components like templates and pipelines are created for the stream. These components are considered *managed* and shouldn't be modified using {{es}} APIs. When managing a stream through the Streams UI or API, continue doing so whenever possible.
+
+You can still edit non-managed ingest pipelines, templates, and other components, but avoid those marked as managed or any per-data-stream mappings and settings. This behavior is similar to how Elasticsearch handles components managed by integrations. Refer to the [**Advanced** tab](./management/advanced.md) to review managed components.
+
 ## Required permissions
 
 Streams requires the following permissions: