|
| 1 | +--- |
| 2 | +products: |
| 3 | + - id: kibana |
| 4 | + - id: elastic-agent |
| 5 | +applies_to: |
| 6 | + stack: preview 9.1 |
| 7 | + serverless: ga |
| 8 | +--- |
| 9 | + |
| 10 | +# Using Spaces with {{fleet}}[spaces-fleet] |
| 11 | + |
| 12 | +Fleet supports a **space-aware** data model. You can use [Kibana spaces](/deploy-manage/manage-spaces) to manage Agent policies and integrations per space. Combined with granular user roles, this feature enables true role-based access control for {{agent}} management. |
| 13 | + |
| 14 | +For **new deployments** on 9.1.0 or later, space awareness is enabled by default. |
| 15 | +For **upgraded deployments** from earlier versions, you must explicitly [enable space awareness](#enable-space-awareness-in-fleetspaces-fleet-enable). |
| 16 | + |
| 17 | +To use space awareness with {{fleet}}: |
| 18 | + |
| 19 | +- [Enable the space awareness feature](#enabling-space-awareness-in-fleet) |
| 20 | +- [Assign and manage Agent policies across spaces](#managing-agent-policies-across-spaces) |
| 21 | +- [Make integration assets available across spaces](#managing-integration-assets-across-spaces) |
| 22 | + |
| 23 | +## Enable space awareness in Fleet [spaces-fleet-enable] |
| 24 | + |
| 25 | +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. |
| 26 | + |
| 27 | +To enable space awareness in upgraded deployments: |
| 28 | + |
| 29 | +1. Navigate to the **Fleet** app. |
| 30 | +2. Click the **Settings** tab. |
| 31 | +3. Scroll to **Advanced settings**. |
| 32 | +4. Under **Migrate to space-aware agent policies**, click **Start migration**. |
| 33 | +5. Confirm the migration. |
| 34 | + |
| 35 | + |
| 36 | +## Manage Agent policies across spaces[spaces-manage-policies] |
| 37 | + |
| 38 | +To control where an Agent Policy is available: |
| 39 | + |
| 40 | +1. Navigate to the Agent Policy’s **Settings** tab. |
| 41 | + |
| 42 | + :::{image} /deploy-manage/images/kibana-space-fleet-policy.png |
| 43 | + :alt: Agent Policy settings tab |
| 44 | + :screenshot: |
| 45 | + ::: |
| 46 | + |
| 47 | +2. Use the **Spaces** dropdown to select one or more spaces. |
| 48 | + |
| 49 | + :::{image} /deploy-manage/images/kibana-space-policy-settings.png |
| 50 | + :alt: Agent Policy spaces dropdown |
| 51 | + :screenshot: |
| 52 | + ::: |
| 53 | + |
| 54 | +Agent policies can be assigned to multiple spaces. In this example, the policy is visible in both the "Default" space and "My second space." |
| 55 | + |
| 56 | +:::{image} /deploy-manage/images/kibana-space-multispace.png |
| 57 | +:alt: Policy in multiple spaces |
| 58 | +:screenshot: |
| 59 | +::: |
| 60 | + |
| 61 | + |
| 62 | +Access to a policy is still governed by each user's {{fleet}} permissions within selected spaces. |
| 63 | + |
| 64 | +## Manage integration assets across spaces[spaces-manage-assets] |
| 65 | + |
| 66 | +When you add an integration to an Agent policy, assets such as dashboards and visualizations are installed **only in the current space** by default. |
| 67 | + |
| 68 | +If the Agent Policy spans multiple spaces, install the integration's assets in each space manually: |
| 69 | + |
| 70 | +1. Switch to the desired Kibana space. |
| 71 | +2. Go to the **Integrations** app > **Installed integrations** tab. |
| 72 | +3. Click the name of the integration. |
| 73 | + |
| 74 | + :::{image} /deploy-manage/images/kibana-space-integration.png |
| 75 | + :alt: Installed integrations list |
| 76 | + :screenshot: |
| 77 | + ::: |
| 78 | + |
| 79 | +4. Open the **Assets** tab. |
| 80 | + |
| 81 | + :::{image} /deploy-manage/images/kibana-space-add-asset.png |
| 82 | + :alt: Kibana Assets tab |
| 83 | + :screenshot: |
| 84 | + ::: |
| 85 | + |
| 86 | +5. Click **Install Kibana assets in current space**. |
| 87 | + |
| 88 | + This installs dashboards and other UI assets into the selected space. |
| 89 | + |
| 90 | +:::{note} |
| 91 | +Due to limitations in Kibana’s saved object model, integration assets are copied per space. These saved objects are considered **managed** and are **readonly**. |
| 92 | +::: |
0 commit comments