Merge branch 'main' into docs-9.2.0

Author: claudia-correia

deploy-manage/remote-clusters/_snippets/ccs-compatibility-table.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.

deploy-manage/tools/snapshot-and-restore/_snippets/restore-snapshot-common-prerequisites.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
 

deploy-manage/tools/snapshot-and-restore/elastic-cloud-hosted.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

deploy-manage/tools/snapshot-and-restore/restore-snapshot.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]
 

deploy-manage/tools/snapshot-and-restore/self-managed.md

@@ -88,7 +88,7 @@ The behavior of allocations depends on several factors:
 If you enable adaptive allocations and set the `min_number_of_allocations` to a value greater than `0`, you will be charged for the machine learning resources, even if no inference requests are sent.
 
 However, setting the `min_number_of_allocations` to a value greater than `0` keeps the model always available without scaling delays. Choose the configuration that best fits your workload and availability needs.
-:::: 
+::::
 
 For more information about adaptive allocations and resources, refer to the [trained model autoscaling](/deploy-manage/autoscaling/trained-model-autoscaling.md) documentation.
 
@@ -105,9 +105,9 @@ By default, documents are split into sentences and grouped in sections up to 250
 
 ### Chunking strategies
 
-Several strategies are available for chunking: 
+Several strategies are available for chunking:
 
-#### `sentence` 
+#### `sentence`
 
 The `sentence` strategy splits the input text at sentence boundaries. Each chunk contains one or more complete sentences ensuring that the integrity of sentence-level context is preserved, except when a sentence causes a chunk to exceed a word count of `max_chunk_size`, in which case it will be split across chunks. The `sentence_overlap` option defines the number of sentences from the previous chunk to include in the current chunk which is either `0` or `1`.
 
@@ -134,7 +134,7 @@ The default chunking strategy is `sentence`.
 
 #### `word`
 
-The `word` strategy splits the input text on individual words up to the `max_chunk_size` limit. The `overlap` option is the number of words from the previous chunk to include in the current chunk. 
+The `word` strategy splits the input text on individual words up to the `max_chunk_size` limit. The `overlap` option is the number of words from the previous chunk to include in the current chunk.
 
 The following example creates an {{infer}} endpoint with the `elasticsearch` service that deploys the ELSER model and configures the chunking behavior with the `word` strategy, setting a maximum of 120 words per chunk and an overlap of 40 words between chunks.
 
@@ -158,7 +158,7 @@ PUT _inference/sparse_embedding/word_chunks
 #### `recursive`
 
 ```{applies_to}
-stack: ga 9.1`
+stack: ga 9.1
 ```
 
 The `recursive` strategy splits the input text based on a configurable list of separator patterns (for example, newlines or Markdown headers). The chunker applies these separators in order, recursively splitting any chunk that exceeds the `max_chunk_size` word limit. If no separator produces a small enough chunk, the strategy falls back to sentence-level splitting.
@@ -215,7 +215,7 @@ PUT _inference/sparse_embedding/recursive_custom_chunks
 #### `none`
 
 ```{applies_to}
-stack: ga 9.1`
+stack: ga 9.1
 ```
 
 The `none` strategy disables chunking and processes the entire input text as a single block, without any splitting or overlap. When using this strategy, you can instead [pre-chunk](https://www.elastic.co/docs/reference/elasticsearch/mapping-reference/semantic-text#auto-text-chunking) the input by providing an array of strings, where each element acts as a separate chunk to be sent directly to the inference service without further chunking.

explore-analyze/elastic-inference/inference-api.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. 
+
+:::
+
+::::
+

explore-analyze/images/ai-assistant-settings-page-serverless.png

@@ -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