Skip to content

Commit 04d6357

Browse files
committed
Refine content
1 parent 12fd2d0 commit 04d6357

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

deploy-manage/manage-spaces-fleet.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -7,9 +7,9 @@ applies_to:
77
serverless: ga
88
---
99

10-
# Using Spaces with {{fleet}}[spaces-fleet]
10+
# Using Spaces with {{fleet}}
1111

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.
12+
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, this feature enables true role-based access control for {{agent}} management.
1313

1414
For **new deployments** on 9.1.0 or later, space awareness is enabled by default.
1515
For **upgraded deployments** from earlier versions, you must explicitly [enable space awareness](#enable-space-awareness-in-fleetspaces-fleet-enable).
@@ -20,7 +20,7 @@ To use space awareness with {{fleet}}:
2020
- [Assign and manage Agent policies across spaces](#managing-agent-policies-across-spaces)
2121
- [Make integration assets available across spaces](#managing-integration-assets-across-spaces)
2222

23-
## Enable space awareness in Fleet [spaces-fleet-enable]
23+
## Enable space awareness in Fleet
2424

2525
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.
2626

@@ -33,7 +33,7 @@ To enable space awareness in upgraded deployments:
3333
5. Confirm the migration.
3434

3535

36-
## Manage Agent policies across spaces[spaces-manage-policies]
36+
## Manage Agent policies across spaces
3737

3838
To control where an Agent Policy is available:
3939

@@ -61,7 +61,7 @@ Agent policies can be assigned to multiple spaces. In this example, the policy i
6161

6262
Access to a policy is still governed by each user's {{fleet}} permissions within selected spaces.
6363

64-
## Manage integration assets across spaces[spaces-manage-assets]
64+
## Manage integration assets across spaces
6565

6666
When you add an integration to an Agent policy, assets such as dashboards and visualizations are installed **only in the current space** by default.
6767

0 commit comments

Comments
 (0)