Using Spaces with Fleet
Stack Serverless
Fleet supports a space-aware data model. You can use Kibana spaces to manage Agent policies and integrations per space. Combined with granular user roles, this feature enables true role-based access control for Elastic Agent management.
For new deployments on Elastic Stack 9.1.0 or later, space awareness is enabled by default. For upgraded deployments from earlier versions, you must explicitly enable space awareness.
To use space awareness with Fleet:
- Enable the space awareness feature (for upgraded deployments)
- Assign and manage Agent policies across spaces
- Make integration assets available across spaces
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:
- Navigate to the Fleet app.
- Click the Settings tab.
- Scroll to Advanced settings.
- Under Migrate to space-aware agent policies, click Start migration.
- Confirm the migration.
To control where an Agent Policy is available:
Agent policies can be assigned to multiple spaces. In this example, the policy is visible in both the "Default" space and "My second space."

Access to a policy is still governed by each user's Fleet permissions within selected spaces.
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:
Switch to the desired Kibana space.
Go to the Integrations app > Installed integrations tab.
Click the name of the integration.
Open the Assets tab.
Click Install Kibana assets in current space.
This installs dashboards and other UI assets into the selected space.
Due to limitations in Kibana’s saved object model, integration assets are copied per space. These saved objects are considered managed and are readonly.