Merge branch 'main' into theletterf-patch-1

Author: theletterf

deploy-manage/images/kibana-space-add-asset.png

@@ -0,0 +1,92 @@
+---
+products:
+  - id: kibana
+  - id: elastic-agent
+applies_to:
+  stack: ga 9.1
+  serverless: ga
+---
+
+# Using Spaces with {{fleet}} [spaces-fleet]
+
+Fleet supports a **space-aware** data model. You can use [Kibana spaces](/deploy-manage/manage-spaces.md) to manage Agent policies and integrations per space. Combined with granular [user roles](/reference/fleet/fleet-roles-privileges.md), this feature enables true role-based access control for {{agent}} management.
+
+For **new deployments** on {{stack}} 9.1.0 or later, space awareness is enabled by default.
+For **upgraded deployments** from earlier versions, you must explicitly [enable space awareness](#spaces-fleet-enable).
+
+To use space awareness with {{fleet}}:
+
+- [Enable the space awareness feature](#spaces-fleet-enable) (for upgraded deployments)
+- [Assign and manage Agent policies across spaces](#spaces-manage-policies)
+- [Make integration assets available across spaces](#spaces-manage-assets)
+
+## Enable space awareness in Fleet [spaces-fleet-enable]
+
+You must enable space awareness for deployments upgraded to 9.1.0 or later. Space awareness requires a one-time migration that copies your existing {{fleet}} data into a new, space-aware model. Previous data is preserved in snapshots in case you need to roll back.
+
+To enable space awareness in upgraded deployments:
+
+1. Navigate to the **Fleet** app.
+2. Click the **Settings** tab.
+3. Scroll to **Advanced settings**.
+4. Under **Migrate to space-aware agent policies**, click **Start migration**.
+5. Confirm the migration.
+
+
+## Manage Agent policies across spaces [spaces-manage-policies]
+
+To control where an Agent Policy is available:
+
+1. Navigate to the Agent Policy’s **Settings** tab.
+
+   :::{image} /deploy-manage/images/kibana-space-fleet-policy.png
+   :alt: Agent Policy settings tab
+   :screenshot:
+   :::
+
+2. Use the **Spaces** dropdown to select one or more spaces.
+
+   :::{image} /deploy-manage/images/kibana-space-policy-settings.png
+   :alt: Agent Policy spaces dropdown
+   :screenshot:
+   :::
+
+Agent policies can be assigned to multiple spaces. In this example, the policy is visible in both the "Default" space and "My second space."
+
+:::{image} /deploy-manage/images/kibana-space-multispace.png
+:alt: Policy in multiple spaces
+:screenshot:
+:::
+
+
+Access to a policy is still governed by each user's {{fleet}} permissions within selected spaces.
+
+## Manage integration assets across spaces [spaces-manage-assets]
+
+When you add an integration to an Agent policy, assets such as dashboards and visualizations are installed **only in the current space** by default.
+
+If the Agent Policy spans multiple spaces, install the integration's assets in each space manually:
+
+1. Switch to the desired Kibana space.
+2. Go to the **Integrations** app > **Installed integrations** tab.
+3. Click the name of the integration.
+
+   :::{image} /deploy-manage/images/kibana-space-integration.png
+   :alt: Installed integrations list
+   :screenshot:
+   :::
+
+4. Open the **Assets** tab.
+
+   :::{image} /deploy-manage/images/kibana-space-add-asset.png
+   :alt: Kibana Assets tab
+   :screenshot:
+   :::
+
+5. Click **Install Kibana assets in current space**.
+
+  This installs dashboards and other UI assets into the selected space.
+
+:::{note}
+Due to limitations in Kibana’s saved object model, integration assets are copied per space. These saved objects are considered **managed** and are **readonly**.
+:::

deploy-manage/images/kibana-space-fleet-policy.png

@@ -15,7 +15,7 @@ products:
 **Spaces** let you organize your content and users according to your needs.
 
 - Each space has its own saved objects.
-- Users can only access the spaces that they have been granted access to. This access is based on user roles, and a given role can have different permissions per space.
+- Users can access only the spaces that they have been granted access to. This access is based on user roles, and a given role can have different permissions per space.
 - In {{stack}} deployments on version 8.16 and later, each space has its own navigation, called solution view.
 
 {{kib}} creates a default space for you. When you create more spaces, users are asked to choose a space when they log in, and can change their current space at any time from the top menu.
@@ -27,6 +27,14 @@ products:
 
 To go to **Spaces**, find **Stack Management** in the navigation menu or use the [global search bar](/explore-analyze/find-and-organize/find-apps-and-objects.md).
 
+For more info on working with spaces, check out: 
+- [Create a space](#spaces-managing)
+- [Define access to a space](#spaces-control-user-access)
+- [Move saved objects between spaces](#spaces-moving-objects)
+- [Configure a space-level landing page](#spaces-default-route)
+- [Delete a space](#_delete_a_space)
+
+Check out [Using Spaces with Fleet](/deploy-manage/manage-spaces-fleet.md) for info on using spaces with {{fleet}} in a space-aware data model.
 
 ## Required permissions [_required_privileges_3]
 
@@ -113,12 +121,6 @@ If you're managing an {{stack}} deployment, then you can also assign roles and d
 When a role is assigned to *All Spaces*, you can’t remove its access from the space settings. You must instead edit the role to give it more granular access to individual spaces.
 
 
-
-## Delete a space [_delete_a_space]
-
-Deleting a space permanently removes the space and all of its contents. Find the space on the **Spaces** overview page and click the trash icon in the Actions column. You can’t delete the default space, but you can customize it to your liking.
-
-
 ## Move saved objects between spaces [spaces-moving-objects]
 
 To move saved objects between spaces, you can [copy objects](/explore-analyze/find-and-organize/saved-objects.md#managing-saved-objects-copy-to-space), or [export and import objects](/explore-analyze/find-and-organize/saved-objects.md#managing-saved-objects-export-objects).
@@ -137,4 +139,9 @@ To configure the landing page, use the default route setting in [Stack Managemen
 :::{image} /deploy-manage/images/kibana-spaces-configure-landing-page.png
 :alt: Configure space-level landing page
 :screenshot:
-:::
+:::
+
+
+## Delete a space [_delete_a_space]
+
+Deleting a space permanently removes the space and all of its contents. Find the space on the **Spaces** overview page and click the trash icon in the Actions column. You can’t delete the default space, but you can customize it to your liking.

deploy-manage/images/kibana-space-integration.png

@@ -78,14 +78,14 @@ spec:
     elasticsearchRef:
       name: cluster-two
       namespace: ns-two
-      apiKey:
-        access:
-          search:
-            names:
-              - kibana_sample_data_ecommerce  <1>
-          replication:
-            names:
-              - kibana_sample_data_ecommerce  <1>
+    apiKey:
+      access:
+        search:
+          names:
+            - kibana_sample_data_ecommerce  <1>
+        replication:
+          names:
+            - kibana_sample_data_ecommerce  <1>
   version: 8.16.1
 ```
 

deploy-manage/images/kibana-space-multispace.png

@@ -617,6 +617,8 @@ toc:
               - file: users-roles/cluster-or-deployment-auth/controlling-access-at-document-field-level.md
               - file: users-roles/cluster-or-deployment-auth/submitting-requests-on-behalf-of-other-users.md
   - file: manage-spaces.md
+    children:
+      - file: manage-spaces-fleet.md
   - file: api-keys.md
     children:
       - file: api-keys/elasticsearch-api-keys.md

deploy-manage/images/kibana-space-policy-settings.png

@@ -7,7 +7,18 @@ navigation_title: Elastic Inference
 
 # Elastic {{infer-cap}}
 
-There are several ways to perform {{infer}} in the {{stack}}. This page provides a brief overview of the different methods:
+## Overview
 
-* [Using the {{infer}} API](elastic-inference/inference-api.md)
-* [Trained models deployed in your cluster](machine-learning/nlp/ml-nlp-overview.md)
+{{infer-cap}} is a process of using a {{ml}} trained model to make predictions or operations - such as text embedding, or reranking - on your data.
+You can use {{infer}} during ingest time (for example, to create embeddings from textual data you ingest) or search time (to perform [semantic search](/solutions/search/semantic-search.md) based on the embeddings created previously).
+There are several ways to perform {{infer}} in the {{stack}}, depending on the underlying {{infer}} infrastructure and the interface you use:
+
+- **{{infer-cap}} infrastructure:**
+
+  - [Elastic {{infer-cap}} Service](elastic-inference/eis.md): a managed service that runs {infer} outside your cluster resources.
+  - [Trained models deployed in your cluster](machine-learning/nlp/ml-nlp-overview.md): models run on your own {{ml}} nodes
+
+- **Access methods:**
+
+  - [The `semantic_text` workflow](/solutions/search/semantic-search/semantic-search-semantic-text.md): a simplified method that uses the {{infer}} API behind the scenes to enable semantic search.
+  - [The {{infer}} API](elastic-inference/inference-api.md): a general-purpose API that enables you to run {{infer}} using EIS, your own models, or third-party services.