Merge branch 'main' into streams-274-md

yetanothertw · web-flow · commit 87908b8f8e2d · 2025-10-22T22:25:50.000+01:00
diff --git a/deploy-manage/tools/snapshot-and-restore/_snippets/restore-snapshot-common-prerequisites.md b/deploy-manage/tools/snapshot-and-restore/_snippets/restore-snapshot-common-prerequisites.md
@@ -0,0 +1,6 @@
+* To use {{kib}}'s **Snapshot and Restore** feature, you must have the following permissions:
+
+    * [Cluster privileges](elasticsearch://reference/elasticsearch/security-privileges.md#privileges-list-cluster): `monitor`, `manage_slm`, `cluster:admin/snapshot`, and `cluster:admin/repository`
+    * [Index privilege](elasticsearch://reference/elasticsearch/security-privileges.md#privileges-list-indices): `monitor` privilege on all the indices
+
+* To register a snapshot repository or restore a snapshot, the cluster’s global metadata must be writeable. Ensure there aren’t any [cluster blocks](elasticsearch://reference/elasticsearch/configuration-reference/miscellaneous-cluster-settings.md#cluster-read-only) that prevent write access. The restore operation ignores index blocks.
diff --git a/deploy-manage/tools/snapshot-and-restore/elastic-cloud-hosted.md b/deploy-manage/tools/snapshot-and-restore/elastic-cloud-hosted.md
@@ -26,12 +26,8 @@ From within {{ech}}, you can restore a snapshot from a different deployment in t
 
 ## Prerequisites for {{ech}}
 
-To use Kibana's Snapshot and Restore feature, you must have the following permissions:
-
-- Cluster privileges: `monitor`, `manage_slm`, `cluster:admin/snapshot`, and `cluster:admin/repository`
-- Index privilege: `all` on the monitor index
-
-To register a snapshot repository, the cluster’s global metadata must be writable. Ensure there aren’t any cluster blocks that prevent write access.
+:::{include} _snippets/restore-snapshot-common-prerequisites.md
+:::
 
 ## Considerations
 
diff --git a/deploy-manage/tools/snapshot-and-restore/restore-snapshot.md b/deploy-manage/tools/snapshot-and-restore/restore-snapshot.md
@@ -27,12 +27,11 @@ In this guide, you’ll learn how to:
 This guide also provides tips for [restoring to another cluster](#restore-different-cluster) and [troubleshooting common restore errors](#troubleshoot-restore).
 
 ## Prerequisites
-- To use Kibana’s Snapshot and Restore feature, you must have the following permissions:
-  - [Cluster privileges](elasticsearch://reference/elasticsearch/security-privileges.md#privileges-list-cluster): `monitor`, `manage_slm`, `cluster:admin/snapshot`, and `cluster:admin/repository`
-  - [Index privilege](elasticsearch://reference/elasticsearch/security-privileges.md#privileges-list-indices): `all` on the monitor index
+:::{include} _snippets/restore-snapshot-common-prerequisites.md
+:::
+
 - You can only restore a snapshot to a running cluster with an elected [master node](/deploy-manage/distributed-architecture/clusters-nodes-shards/node-roles.md#master-node-role). The snapshot’s repository must be registered and available to the cluster.
 - The snapshot and cluster versions must be compatible. See [Snapshot compatibility](/deploy-manage/tools/snapshot-and-restore.md#snapshot-compatibility).
-- To restore a snapshot, the cluster’s global metadata must be writable. Ensure there aren’t any cluster blocks that prevent writes. The restore operation ignores index blocks.
 - Before you restore a data stream, ensure the cluster contains a [matching index template](/manage-data/use-case-use-elasticsearch-to-manage-time-series-data.md#create-ts-index-template) with data stream enabled. To check, use [Kibana’s Index Management](/manage-data/data-store/index-basics.md#index-management-manage-index-templates) feature or the get index template API:
 
   ```console
diff --git a/deploy-manage/tools/snapshot-and-restore/self-managed.md b/deploy-manage/tools/snapshot-and-restore/self-managed.md
@@ -21,12 +21,8 @@ In this guide, you’ll learn how to:
 
 ## Prerequisites [snapshot-repo-prereqs]
 
-* To use {{kib}}'s **Snapshot and Restore** feature, you must have the following permissions:
-
-    * [Cluster privileges](elasticsearch://reference/elasticsearch/security-privileges.md#privileges-list-cluster): `monitor`, `manage_slm`, `cluster:admin/snapshot`, and `cluster:admin/repository`
-    * [Index privilege](elasticsearch://reference/elasticsearch/security-privileges.md#privileges-list-indices): `all` on the `monitor` index
-
-* To register a snapshot repository, the cluster’s global metadata must be writeable. Ensure there aren’t any [cluster blocks](elasticsearch://reference/elasticsearch/configuration-reference/miscellaneous-cluster-settings.md#cluster-read-only) that prevent write access.
+:::{include} _snippets/restore-snapshot-common-prerequisites.md
+:::
 
 ## Considerations [snapshot-repo-considerations]
 
diff --git a/explore-analyze/images/ai-assistant-settings-page-serverless.png b/explore-analyze/images/ai-assistant-settings-page-serverless.png
diff --git a/explore-analyze/images/ai-assistant-settings-page.png b/explore-analyze/images/ai-assistant-settings-page.png
diff --git a/explore-analyze/manage-access-to-ai-assistant.md b/explore-analyze/manage-access-to-ai-assistant.md
@@ -0,0 +1,59 @@
+---
+applies_to:
+  stack: ga 9.2
+  serverless: ga
+products:
+  - id: kibana
+  - id: observability
+  - id: security
+  - id: cloud-serverless
+---
+
+# Manage access to AI Features
+
+This page describes how to use the GenAI Settings page to control access to AI-powered features in your deployments in the following ways:
+
+
+- Manage which AI connectors are available in your environment. 
+- Enable or disable AI Assistant and other AI-powered features in your environment.
+- {applies_to}`stack: ga 9.2` {applies_to}`serverless: unavailable` Specify in which Elastic solutions the `AI Assistant for Observability and Search` and the `AI Assistant for Security` appear.
+
+
+## Requirements
+
+- To access the **GenAI Settings** page, you need the `Actions and connectors: all` or `Actions and connectors: read` [{{kib}} privilege](/deploy-manage/users-roles/cluster-or-deployment-auth/kibana-privileges.md).
+- To modify the settings on this page, you need the `Advanced Settings: all` {{kib}} privilege.
+
+## The GenAI Settings page
+
+To manage these settings, go to the **GenAI Settings** page by using the navigation menu or the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).
+
+::::{applies-switch}
+
+:::{applies-item} stack: ga 9.2
+
+![GenAI Settings page for Stack](/explore-analyze/images/ai-assistant-settings-page.png "")
+
+
+The **GenAI Settings** page has the following settings:
+
+- **Default AI Connector**: Use this setting to specify which connector is selected by default. This affects all AI-powered features, not just AI Assistant. 
+- **Disallow all other connectors**: Enable this setting to prevent connectors other than the default connector specified above from being used in your space. This affects all AI-powered features, not just AI Assistant. 
+- **AI feature visibility**: This button opens the current Space's settings page. Here you can specify which features should appear in your environment, including AI-powered features. 
+- **AI Assistant visibility**: This setting allows you to choose which AI Assistants are available to use and where. You can choose to only show the AI Assistants in their native solutions, in other {{kib}} pages (for example, Discover, Dashboards, and Stack Management), or select **Hide all assistants** to disable AI Assistant throughout {{kib}}.
+
+:::
+
+:::{applies-item} serverless:
+
+![GenAI Settings page for Serverless](/explore-analyze/images/ai-assistant-settings-page-serverless.png "")
+
+The **GenAI Settings** page has the following settings:
+
+- **Default AI Connector**: Click **Manage connectors** to open the **Connectors** page, where you can create or delete AI connectors. To update these settings, you need the `Actions and connectors: all` [{{kib}} privilege](/deploy-manage/users-roles/cluster-or-deployment-auth/kibana-privileges.md).
+- **AI feature visibility**: Click **Go to Permissions tab** to access the active {{kib}} space's settings page, where you can specify which features each custom user role has access to in your environment. This includes AI-powered features such as AI Assistant. 
+
+:::
+
+::::
+
diff --git a/explore-analyze/toc.yml b/explore-analyze/toc.yml
@@ -153,6 +153,7 @@ toc:
       - file: scripting/modules-scripting-engine.md
       - file: scripting/painless-lab.md
   - file: ai-assistant.md
+  - file: manage-access-to-ai-assistant.md
   - file: discover.md
     children:
       - file: discover/discover-get-started.md
diff --git a/reference/fleet/install-uninstall-integration-assets.md b/reference/fleet/install-uninstall-integration-assets.md
@@ -21,12 +21,19 @@ products:
 
 Note that it’s currently not possible to have multiple versions of the same integration installed. When you upgrade an integration, the previous version assets are removed and replaced by the current version.
 
-::::{admonition} Current limitations with integrations and {{kib}} spaces
-:class: important
+::::{admonition} Spaces support for integration assets
 
-{{agent}} integration assets can be installed only on a single {{kib}} [space](/deploy-manage/manage-spaces.md). If you want to access assets in a different space, you can [copy them](/explore-analyze/find-and-organize/saved-objects.md#managing-saved-objects-copy-to-space). However, many integrations include markdown panels with dynamically generated links to other dashboards. When assets are copied between spaces, these links may not behave as expected and can result in a 404 `Dashboard not found` error. Refer to known issue [#175072](https://github.com/elastic/kibana/issues/175072) for details.
+Elastic Agent integrations and associated assets, such as dashboards, visualizations, and saved searches, behave differently depending on your {{stack}} version:
 
-These limitations and future plans for {{fleet}}'s integrations support in multi-space environments are currently being discussed in [#175831](https://github.com/elastic/kibana/issues/175831). Feedback is very welcome. For now, we recommend reviewing the specific integration documentation for any space-related considerations.
+* {applies_to}`stack: ga 9.1` Fleet uses a space-aware data model for {{agent}} policies and integrations. Agent policies can now span multiple spaces, while integration assets remain space-specific. 
+  
+  Integration assets are still installed per space, but can be managed and reinstalled independently in each space.
+  
+  If you upgraded from an earlier version, enable space awareness in Fleet before managing integrations across spaces.
+  
+  For more details, refer to [Using Spaces with Fleet](../../deploy-manage/manage-spaces-fleet.md).
+
+* {applies_to}`stack: ga 9.0` In versions earlier than {{stack}} 9.1, integration assets can be installed in only one {{kib}} space. You can manually [copy them](/explore-analyze/find-and-organize/saved-objects.md#managing-saved-objects-copy-to-space) to other spaces. However, many integrations include markdown panels with dynamically generated links to other dashboards. When copied between spaces, these links might not behave as expected and can result in a `Dashboard not found` (404) error. Refer to known issue [#175072](https://github.com/elastic/kibana/issues/175072) for details.
 
 ::::
 
diff --git a/solutions/observability/connect-to-own-local-llm.md b/solutions/observability/connect-to-own-local-llm.md
@@ -147,3 +147,10 @@ Setup is now complete. You can use the model you’ve loaded in LM Studio to pow
 ::::{note}
 While local (open-weight) LLMs offer greater privacy and control, they generally do not match the raw performance and advanced reasoning capabilities of proprietary models by LLM providers mentioned in [Set up the AI Assistant](/solutions/observability/observability-ai-assistant.md#obs-ai-set-up).
 ::::
+
+## Air-gapped environments
+
+Local LLMs in air-gapped environments have specific installation and configuration instructions for deploying ELSER and configuring product documentation. Refer to the following links for more information:
+
+- [Deploy ELSER in an air-gapped environment](../../explore-analyze/machine-learning/nlp/ml-nlp-elser.md#air-gapped-install)
+- [Configure product documentation for air-gapped-environments](kibana://reference/configuration-reference/ai-assistant-settings.md#configuring-product-doc-for-airgap)
diff --git a/solutions/observability/observability-ai-assistant.md b/solutions/observability/observability-ai-assistant.md
@@ -53,6 +53,19 @@ The AI assistant requires the following:
 
 * A self-deployed connector service if [content connectors](elasticsearch://reference/search-connectors/index.md) are used to populate external data into the knowledge base.
 
+## Manage access to AI Assistant
+
+```{applies_to}
+stack: ga 9.2
+serverless: ga
+```
+
+The [**GenAI settings**](/explore-analyze/manage-access-to-ai-assistant.md) page allows you to:
+
+- Manage which AI connectors are available in your environment. 
+- Enable or disable AI Assistant and other AI-powered features in your environment.
+- {applies_to}`stack: ga 9.2` {applies_to}`serverless: unavailable` Specify in which Elastic solutions the `AI Assistant for Observability and Search` and the `AI Assistant for Security` appear.
+
 ## Your data and the AI Assistant [data-information]
 
 It's important to understand how your data is handled when using the AI Assistant. Here are some key points:
diff --git a/solutions/security/ai/ai-assistant.md b/solutions/security/ai/ai-assistant.md
@@ -35,6 +35,21 @@ The Elastic AI Assistant is designed to enhance your analysis with smart dialogu
 * A [machine learning node](/explore-analyze/machine-learning/setting-up-machine-learning.md).
 ::::
 
+## Manage access to AI Assistant
+
+```{applies_to}
+stack: ga 9.2
+serverless: ga
+```
+
+The [**GenAI settings**](/explore-analyze/manage-access-to-ai-assistant.md) page allows you to:
+
+- Manage which AI connectors are available in your environment. 
+- Enable or disable AI Assistant and other AI-powered features in your environment.
+- {applies_to}`stack: ga 9.2` {applies_to}`serverless: unavailable` Specify in which Elastic solutions the `AI Assistant for Observability and Search` and the `AI Assistant for Security` appear.
+
+
+
 ## Your data and AI Assistant [data-information]
 
 Elastic does not store or examine prompts or results used by AI Assistant, or use this data for model training. This includes anything you send the model, such as alert or event data, detection rule configurations, queries, and prompts. However, any data you provide to AI Assistant will be processed by the third-party large language model (LLM) provider you connected to as part of AI Assistant setup.
@@ -401,15 +416,6 @@ When you include a particular event as context, such as an alert from the Alerts
 
 The **Knowledge base** tab of the **Security AI settings** page allows you to enable AI Assistant to remember specified information, and use it as context to improve response quality. To learn more, refer to [AI Assistant Knowledge Base](/solutions/security/ai/ai-assistant-knowledge-base.md).
 
-### AI Assistant visibility [ai-assistant-visibility]
-```{applies_to}
-stack: ga 9.1
-serverless: ga
-```
-:::{include} ../../_snippets/ai-assistant-visibility.md
-:::
-If you select the option to show the Security AI Assistant in other apps, the Security AI Assistant becomes **accessible outside of the Security solution**, for example, in Discover. The chat history remains persistent and is available no matter where you access the assistant within Kibana. 
-
 ### Get the most from your queries [rag-for-esql]
 
 Elastic AI Assistant allows you to take full advantage of the {{elastic-sec}} platform to improve your security operations. It can help you write an {{esql}} query for a particular use case, or answer general questions about how to use the platform. Its ability to assist you depends on the specificity and detail of your questions. The more context and detail you provide, the more tailored and useful its responses will be.
