diff --git a/deploy-manage/manage-spaces.md b/deploy-manage/manage-spaces.md
index b9ac03522b..f9dd690194 100644
--- a/deploy-manage/manage-spaces.md
+++ b/deploy-manage/manage-spaces.md
@@ -1,10 +1,13 @@
 ---
+applies:
+  stack: ga 9.0
+  serverless:
 mapped_urls:
   - https://www.elastic.co/guide/en/kibana/current/xpack-spaces.html
   - https://www.elastic.co/guide/en/serverless/current/spaces.html
 ---
 
-# Manage spaces
+# Manage spaces [xpack-spaces]
 
 % What needs to be done: Refine
 
@@ -23,4 +26,106 @@ $$$spaces-control-feature-visibility$$$
 
 $$$spaces-control-user-access$$$
 
-$$$spaces-managing$$$
\ No newline at end of file
+$$$spaces-managing$$$
+
+**Spaces** let you organize your content and users according to your needs.
+
+- **\[Not available in serverless]** Each space has its own navigation.
+- 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.
+
+{{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.
+
+:::{image} ../images/kibana-change-space.png
+:alt: Change current space menu
+:class: screenshot
+:::
+
+To go to **Spaces**, find **Stack Management** in the navigation menu or use the [global search bar](/get-started/the-stack.md#kibana-navigation-search).
+
+
+## Required permissions [_required_privileges_3]
+
+The `kibana_admin` role or equivalent is required to manage **Spaces**.
+
+::::{note}
+In a serverless project, you must have an admin role on that project to manage its **Spaces**.
+::::
+
+
+## Create a space [spaces-managing]
+
+$$$spaces-control-feature-visibility$$$
+You can have up to 1,000 spaces by default. The maximum number of spaces can be configured by the `xpack.spaces.maxSpaces` setting (refer to [Spaces settings in {{kib}}](https://www.elastic.co/guide/en/kibana/current/spaces-settings-kb.html)).
+
+::::{note}
+In a serverless project, the number of spaces is limited to 100.
+::::
+
+1. Select **Create space** and provide a name, description, and URL identifier.
+
+    The URL identifier is a short text string that becomes part of the {{kib}} URL when you are inside that space. {{kib}} suggests a URL identifier based on the name of your space, but you can customize the identifier to your liking. You cannot change the space identifier once you create the space.
+
+2. **\[Not available in serverless]** Select a **Solution view**. This setting controls the navigation that all users of the space will get:
+
+    * **Search**: A light navigation menu focused on analytics and Search use cases. Features specific to Observability and Security are hidden.
+    * **Observability**: A light navigation menu focused on analytics and Observability use cases. Features specific to Search and Security are hidden.
+    * **Security**: A light navigation menu focused on analytics and Security use cases. Features specific to Observability and Search are hidden.
+    * **Classic**: All features from all solutions are visible by default using the classic, multilayered navigation menus. You can customize which features are visible individually.
+
+3. **\[Not available in serverless]** If you selected the **Classic*** solution view, you can customize the ***Feature visibility** as you need it to be for that space.
+   ::::{note}
+   Even when disabled in this menu, some Management features can remain visible to some users depending on their privileges. Additionally, controlling feature visibility is not a security feature. To secure access to specific features on a per-user basis, you must configure [{{kib}} Security](/deploy-manage/users-roles/cluster-or-deployment-auth/built-in-roles.md).
+   ::::
+
+4. Customize the avatar of the space to your liking.
+5. Save your new space by selecting **Create space**.
+
+You can edit all of the space settings you just defined at any time, except for the URL identifier.
+
+{{kib}} also has an [API](https://www.elastic.co/guide/en/kibana/current/spaces-api.html) if you prefer to create spaces programmatically.
+
+
+## Define access to a space [spaces-control-user-access]
+
+::::{note}
+In serverless projects, customizing access to a space is available for the following project types only: [![Elasticsearch](../images/serverless-es-badge.svg "")](/solutions/search.md) [![Security](../images/serverless-sec-badge.svg "")](/solutions/security/elastic-security-serverless.md)
+::::
+
+Users can access spaces based on the roles that they have.
+
+* Certain reserved roles can view and access all spaces by default. You can’t prevent those roles from accessing a space. Instead, you can grant different roles to your users.
+* When creating or editing a role, you can define which existing spaces that role can access, and with which permissions. Role management differs between Kibana version 9.0 and serverless projects.
+  - For Kibana version 9.0 and later, check [Creating or editing a role](/deploy-manage/users-roles/cluster-or-deployment-auth/defining-roles.md).
+  - For serverless projects, check [Custom roles](/deploy-manage/users-roles/cloud-organization/user-roles.md).
+*  **\[Not available in serverless]** When editing a space, you can assign roles to the space and define the permissions within the space for these roles. To do that, go to the **Permissions** tab of the space you’re editing.
+
+    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).
+
+
+## Configure a space-level landing page [spaces-default-route]
+
+You can create a custom experience for users by configuring the {{kib}} landing page on a per-space basis. The landing page can route users to a specific dashboard, application, or saved object as they enter each space.
+
+To configure the landing page, use the default route setting in [Stack Management > {{kib}} > Advanced settings](https://www.elastic.co/guide/en/kibana/current/advanced-options.html#kibana-general-settings). For example, you might set the default route to `/app/dashboards`.
+
+:::{image} ../images/kibana-spaces-configure-landing-page.png
+:alt: Configure space-level landing page
+:class: screenshot
+:::
+
+
+## Disable spaces [spaces-delete-started]
+
+Since {{kib}} 8.0, the Spaces feature cannot be disabled.
\ No newline at end of file
diff --git a/deploy-manage/manage-spaces/manage-spaces-serverless.md b/deploy-manage/manage-spaces/manage-spaces-serverless.md
new file mode 100644
index 0000000000..788c0e4964
--- /dev/null
+++ b/deploy-manage/manage-spaces/manage-spaces-serverless.md
@@ -0,0 +1,50 @@
+---
+applies:
+  serverless:
+---
+
+# Manage spaces in serverless projects [spaces]
+
+
+This content applies to: [![Elasticsearch](../../images/serverless-es-badge.svg "")](/solutions/search.md) [![Observability](../../images/serverless-obs-badge.svg "")](/solutions/observability.md) [![Security](../../images/serverless-sec-badge.svg "")](/solutions/security/elastic-security-serverless.md)
+
+
+
+## Required permissions [spaces-required-permissions]
+
+You must have an admin role on a project to manage its **Spaces**.
+
+
+## Create or edit a space [spaces-create-or-edit-a-space]
+
+You can have up to 100 spaces in a project.
+
+1. Click **Create space** or select the space you want to edit.
+2. Provide:
+
+    * A meaningful name and description for the space.
+    * A URL identifier. The URL identifier is a short text string that becomes part of the {{kib}} URL. {{kib}} suggests a URL identifier based on the name of your space, but you can customize the identifier to your liking. You cannot change the space identifier later.
+
+3. Customize the avatar of the space to your liking.
+4. Save the space.
+
+{{kib}} also has an [API](https://www.elastic.co/docs/api/doc/serverless/group/endpoint-spaces) if you prefer to create spaces programmatically.
+
+
+## Customize access to space [spaces-customize-access-to-space]
+
+Customizing access to a space is available for the following project types only: [![Elasticsearch](../../images/serverless-es-badge.svg "")](/solutions/search.md) [![Security](../../images/serverless-sec-badge.svg "")](/solutions/security/elastic-security-serverless.md)
+
+As an administrator, you can define custom roles with specific access to certain spaces and features in a project. Refer to [Custom roles](/deploy-manage/users-roles/cloud-organization/user-roles.md).
+
+
+## Delete a space [spaces-delete-a-space]
+
+Deleting a space permanently removes the space and all of its contents. Find the space on the *Spaces* 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-move-saved-objects-between-spaces]
+
+To move saved objects between spaces, you can [copy objects](/explore-analyze/find-and-organize.md#saved-objects-copy-to-other-spaces) or [export and import objects](/explore-analyze/find-and-organize.md#saved-objects-import-and-export).
diff --git a/deploy-manage/manage-spaces/manage-spaces-stack.md b/deploy-manage/manage-spaces/manage-spaces-stack.md
new file mode 100644
index 0000000000..e2467cda2f
--- /dev/null
+++ b/deploy-manage/manage-spaces/manage-spaces-stack.md
@@ -0,0 +1,81 @@
+---
+applies:
+  stack: ga 9.0
+---
+
+# Manage spaces in Elastic Stack 9.0 [xpack-spaces]
+
+
+## Required privileges [_required_privileges_3]
+
+The `kibana_admin` role or equivalent is required to manage **Spaces**.
+
+
+## Create a space [spaces-managing]
+
+$$$spaces-control-feature-visibility$$$
+You can have up to 1,000 spaces by default. The maximum number of spaces can be configured by the `xpack.spaces.maxSpaces` setting (refer to [Spaces settings in {{kib}}](https://www.elastic.co/guide/en/kibana/current/spaces-settings-kb.html)).
+
+1. Select **Create space** and provide a name, description, and URL identifier.
+
+    The URL identifier is a short text string that becomes part of the {{kib}} URL when you are inside that space. {{kib}} suggests a URL identifier based on the name of your space, but you can customize the identifier to your liking. You cannot change the space identifier once you create the space.
+
+2. Select a **Solution view**. This setting controls the navigation that all users of the space will get:
+
+    * **Search**: A light navigation menu focused on analytics and Search use cases. Features specific to Observability and Security are hidden.
+    * **Observability**: A light navigation menu focused on analytics and Observability use cases. Features specific to Search and Security are hidden.
+    * **Security**: A light navigation menu focused on analytics and Security use cases. Features specific to Observability and Search are hidden.
+    * **Classic**: All features from all solutions are visible by default using the classic, multilayered navigation menus. You can customize which features are visible individually.
+
+3. If you selected the **Classic*** solution view, you can customize the ***Feature visibility** as you need it to be for that space.
+
+   ::::{note}
+   Even when disabled in this menu, some Management features can remain visible to some users depending on their privileges. Additionally, controlling feature visibility is not a security feature. To secure access to specific features on a per-user basis, you must configure [{{kib}} Security](/deploy-manage/users-roles/cluster-or-deployment-auth/built-in-roles.md).
+   ::::
+
+4. Customize the avatar of the space to your liking.
+5. Save your new space by selecting **Create space**.
+
+You can edit all of the space settings you just defined at any time, except for the URL identifier.
+
+{{kib}} also has an [API](https://www.elastic.co/guide/en/kibana/current/spaces-api.html) if you prefer to create spaces programmatically.
+
+
+## Define access to a space [spaces-control-user-access]
+
+
+Users can access spaces based on the roles that they have.
+
+* Certain reserved roles can view and access all spaces by default. You can’t prevent those roles from accessing a space. Instead, you can grant different roles to your users.
+* When [creating or editing a role](/deploy-manage/users-roles/cluster-or-deployment-auth/defining-roles.md), you can define which existing spaces that role can access, and with which permissions.
+* When editing a space, you can assign roles to the space and define the permissions within the space for these roles. To do that, go to the **Permissions** tab of the space you’re editing.
+
+    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).
+
+
+## Configure a space-level landing page [spaces-default-route]
+
+You can create a custom experience for users by configuring the {{kib}} landing page on a per-space basis. The landing page can route users to a specific dashboard, application, or saved object as they enter each space.
+
+To configure the landing page, use the default route setting in [Stack Management > {{kib}} > Advanced settings](https://www.elastic.co/guide/en/kibana/current/advanced-options.html#kibana-general-settings). For example, you might set the default route to `/app/dashboards`.
+
+:::{image} ../../images/kibana-spaces-configure-landing-page.png
+:alt: Configure space-level landing page
+:class: screenshot
+:::
+
+
+## Disable spaces [spaces-delete-started]
+
+Since {{kib}} 8.0, the Spaces feature cannot be disabled.
diff --git a/deploy-manage/manage-spaces2.md b/deploy-manage/manage-spaces2.md
new file mode 100644
index 0000000000..300edd543d
--- /dev/null
+++ b/deploy-manage/manage-spaces2.md
@@ -0,0 +1,183 @@
+---
+applies:
+  stack: ga 9.0
+  serverless:
+mapped_urls:
+  - https://www.elastic.co/guide/en/kibana/current/xpack-spaces.html
+  - https://www.elastic.co/guide/en/serverless/current/spaces.html
+---
+
+# Manage spaces [xpack-spaces]
+
+% What needs to be done: Refine
+
+% GitHub issue: https://github.com/elastic/docs-projects/issues/348
+
+% Scope notes: Create a new landing page including the content that is relevant for both serverless and stateful Highlight the differences in subheadings for serverless and stateful Link to solution topics on spaces
+
+% Use migrated content from existing pages that map to this page:
+
+% - [ ] ./raw-migrated-files/kibana/kibana/xpack-spaces.md
+% - [ ] ./raw-migrated-files/docs-content/serverless/spaces.md
+
+% Internal links rely on the following IDs being on this page (e.g. as a heading ID, paragraph ID, etc):
+
+$$$spaces-control-feature-visibility$$$
+
+$$$spaces-control-user-access$$$
+
+$$$spaces-managing$$$
+
+**Spaces** let you organize your content and users according to your needs.
+
+- **\[Not available in serverless]** Each space has its own navigation.
+- 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.
+
+{{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.
+
+:::{image} ../images/kibana-change-space.png
+:alt: Change current space menu
+:class: screenshot
+:::
+
+To go to **Spaces**, find **Stack Management** in the navigation menu or use the [global search bar](/get-started/the-stack.md#kibana-navigation-search).
+
+
+## Required permissions [_required_privileges_3]
+
+::::{tab-set}
+:group: stack-serverless
+
+:::{tab-item} Kibana 9.0 and later
+:sync: stack
+The `kibana_admin` role or equivalent is required to manage **Spaces**.
+:::
+
+:::{tab-item} Serverless
+:sync: serverless
+
+You must have the admin role on your serverless project to manage its **Spaces**.
+:::
+
+::::
+
+
+
+## Create a space [spaces-managing]
+
+::::{tab-set}
+:group: stack-serverless
+
+:::{tab-item} Kibana 9.0 and later
+:sync: stack
+
+You can have up to 1,000 spaces by default. The maximum number of spaces can be configured by the `xpack.spaces.maxSpaces` setting (refer to [Spaces settings in {{kib}}](https://www.elastic.co/guide/en/kibana/current/spaces-settings-kb.html)).
+
+1. Select **Create space** and provide a name, description, and URL identifier.
+   The URL identifier is a short text string that becomes part of the {{kib}} URL when you are inside that space. {{kib}} suggests a URL identifier based on the name of your space, but you can customize the identifier to your liking. You cannot change the space identifier once you create the space.
+
+2. Select a **Solution view**. This setting controls the navigation that all users of the space will get:
+   * **Search**: A light navigation menu focused on analytics and Search use cases. Features specific to Observability and Security are hidden.
+   * **Observability**: A light navigation menu focused on analytics and Observability use cases. Features specific to Search and Security are hidden.
+   * **Security**: A light navigation menu focused on analytics and Security use cases. Features specific to Observability and Search are hidden.
+   * **Classic**: All features from all solutions are visible by default using the classic, multilayered navigation menus. You can customize which features are visible individually.
+
+3. If you selected the **Classic*** solution view, you can customize the ***Feature visibility** as you need it to be for that space.
+
+   % This is hacking since proper admonition blocks are currently breaking my tabs
+   > **Note:** Even when disabled in this menu, some Management features can remain visible to some users depending on their privileges. Additionally, controlling feature visibility is not a security feature. To secure access to specific features on a per-user basis, you must configure [{{kib}} Security](/deploy-manage/users-roles/cluster-or-deployment-auth/built-in-roles.md).
+
+
+4. Customize the avatar of the space to your liking.
+5. Save your new space by selecting **Create space**.
+
+You can edit all of the space settings you just defined at any time, except for the URL identifier.
+
+{{kib}} also has an [API](https://www.elastic.co/guide/en/kibana/current/spaces-api.html) if you prefer to create spaces programmatically.
+
+:::
+
+:::{tab-item} Serverless
+:sync: serverless
+
+You can have up to 100 spaces in a project.
+
+1. Click **Create space** or select the space you want to edit.
+2. Provide:
+
+    * A meaningful name and description for the space.
+    * A URL identifier. The URL identifier is a short text string that becomes part of the {{kib}} URL. {{kib}} suggests a URL identifier based on the name of your space, but you can customize the identifier to your liking. You cannot change the space identifier later.
+
+3. Customize the avatar of the space to your liking.
+4. Save the space.
+
+{{kib}} also has an [API](https://www.elastic.co/docs/api/doc/serverless/group/endpoint-spaces) if you prefer to create spaces programmatically.
+:::
+
+::::
+
+
+## Define access to a space [spaces-control-user-access]
+
+::::{tab-set}
+:group: stack-serverless
+
+:::{tab-item} Kibana 9.0 and later
+:sync: stack
+
+Users can access spaces based on the roles that they have.
+
+* Certain reserved roles can view and access all spaces by default. You can’t prevent those roles from accessing a space. Instead, you can grant different roles to your users.
+* When [creating or editing a role](/deploy-manage/users-roles/cluster-or-deployment-auth/defining-roles.md), you can define which existing spaces that role can access, and with which permissions.
+* When editing a space, you can assign roles to the space and define the permissions within the space for these roles. To do that, go to the **Permissions** tab of the space you’re editing.
+
+    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.
+:::
+
+:::{tab-item} Serverless
+:sync: serverless
+
+Customizing access to a space is available for the following project types only: [![Elasticsearch](../images/serverless-es-badge.svg "")](/solutions/search.md) [![Security](../images/serverless-sec-badge.svg "")](/solutions/security/elastic-security-serverless.md)
+
+As an administrator, you can define custom roles with specific access to certain spaces and features in a project. Refer to [Custom roles](/deploy-manage/users-roles/cloud-organization/user-roles.md).
+:::
+
+::::
+
+
+
+## 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).
+
+
+## Configure a space-level landing page [spaces-default-route]
+
+::::{tab-set}
+:group: stack-serverless
+
+:::{tab-item} Kibana 9.0 and later
+:sync: stack
+
+You can create a custom experience for users by configuring the {{kib}} landing page on a per-space basis. The landing page can route users to a specific dashboard, application, or saved object as they enter each space.
+
+To configure the landing page, use the default route setting in [Stack Management > {{kib}} > Advanced settings](https://www.elastic.co/guide/en/kibana/current/advanced-options.html#kibana-general-settings). For example, you might set the default route to `/app/dashboards`.
+
+![Configure space-level landing page](../images/kibana-spaces-configure-landing-page.png)
+:::
+
+:::{tab-item} Serverless
+:sync: serverless
+
+This capability is not available in serverless projects.
+:::
+
+::::
\ No newline at end of file
diff --git a/deploy-manage/manage-spaces3.md b/deploy-manage/manage-spaces3.md
new file mode 100644
index 0000000000..387f23e646
--- /dev/null
+++ b/deploy-manage/manage-spaces3.md
@@ -0,0 +1,48 @@
+---
+applies:
+  stack: ga 9.0
+  serverless:
+mapped_urls:
+  - https://www.elastic.co/guide/en/kibana/current/xpack-spaces.html
+  - https://www.elastic.co/guide/en/serverless/current/spaces.html
+---
+
+# Manage spaces [xpack-spaces]
+
+% What needs to be done: Refine
+
+% GitHub issue: https://github.com/elastic/docs-projects/issues/348
+
+% Scope notes: Create a new landing page including the content that is relevant for both serverless and stateful Highlight the differences in subheadings for serverless and stateful Link to solution topics on spaces
+
+% Use migrated content from existing pages that map to this page:
+
+% - [ ] ./raw-migrated-files/kibana/kibana/xpack-spaces.md
+% - [ ] ./raw-migrated-files/docs-content/serverless/spaces.md
+
+% Internal links rely on the following IDs being on this page (e.g. as a heading ID, paragraph ID, etc):
+
+$$$spaces-control-feature-visibility$$$
+
+$$$spaces-control-user-access$$$
+
+$$$spaces-managing$$$
+
+**Spaces** let you organize your content and users according to your needs.
+
+- **\[Not available in serverless]** Each space has its own navigation.
+- 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.
+
+{{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.
+
+:::{image} ../images/kibana-change-space.png
+:alt: Change current space menu
+:class: screenshot
+:::
+
+To go to **Spaces**, find **Stack Management** in the navigation menu or use the [global search bar](/get-started/the-stack.md#kibana-navigation-search).
+
+Spaces provide different capabilities depending on the type of environment you're running:
+- [Managing spaces in Kibana version 9.0.0 or later](manage-spaces/manage-spaces-stack.md)
+- [Managing spaces in Elastic Cloud Serverless](manage-spaces/manage-spaces-serverless.md)
\ No newline at end of file
diff --git a/deploy-manage/manage-spaces4.md b/deploy-manage/manage-spaces4.md
new file mode 100644
index 0000000000..a65786d863
--- /dev/null
+++ b/deploy-manage/manage-spaces4.md
@@ -0,0 +1,146 @@
+---
+applies:
+  stack: all
+  serverless: all
+mapped_urls:
+  - https://www.elastic.co/guide/en/kibana/current/xpack-spaces.html
+  - https://www.elastic.co/guide/en/serverless/current/spaces.html
+---
+
+# Manage spaces [xpack-spaces]
+
+% What needs to be done: Refine
+
+% GitHub issue: https://github.com/elastic/docs-projects/issues/348
+
+% Scope notes: Create a new landing page including the content that is relevant for both serverless and stateful Highlight the differences in subheadings for serverless and stateful Link to solution topics on spaces
+
+% Use migrated content from existing pages that map to this page:
+
+% - [ ] ./raw-migrated-files/kibana/kibana/xpack-spaces.md
+% - [ ] ./raw-migrated-files/docs-content/serverless/spaces.md
+
+% Internal links rely on the following IDs being on this page (e.g. as a heading ID, paragraph ID, etc):
+
+$$$spaces-control-feature-visibility$$$
+
+$$$spaces-control-user-access$$$
+
+$$$spaces-managing$$$
+
+**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.
+- Each space has its own navigation **[Non-serverless deployments only]**
+
+{{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.
+
+:::{image} ../images/kibana-change-space.png
+:alt: Change current space menu
+:class: screenshot
+:::
+
+To go to **Spaces**, find **Stack Management** in the navigation menu or use the [global search bar](/get-started/the-stack.md#kibana-navigation-search).
+
+
+## Required permissions [_required_privileges_3]
+
+* **Serverless projects:** `Admin` or equivalent 
+* **Non-serverless deployments:** `kibana_admin` or equivalent
+
+
+## Create a space [spaces-managing]
+
+The maximum number of spaces that you can have differs by deployment type: 
+
+* **Serverless:** Maximum of 100 spaces.
+* **Non-serverless deployments:** Controlled by the [`xpack.spaces.maxSpaces`](https://www.elastic.co/guide/en/kibana/current/spaces-settings-kb.html) setting. Default is 1000.
+
+To create a space: 
+
+::::{tab-set}
+:group: stack-serverless
+
+:::{tab-item} Serverless projects
+:sync: serverless
+
+1. Click **Create space** or select the space you want to edit.
+2. Provide:
+
+    * A meaningful name and description for the space.
+    * A URL identifier. The URL identifier is a short text string that becomes part of the {{kib}} URL. {{kib}} suggests a URL identifier based on the name of your space, but you can customize the identifier to your liking. You cannot change the space identifier later.
+
+3. Customize the avatar of the space to your liking.
+4. Save the space.
+:::
+
+:::{tab-item} Non-serverless deployments
+:sync: stack
+
+1. Select **Create space** and provide a name, description, and URL identifier.
+   The URL identifier is a short text string that becomes part of the {{kib}} URL when you are inside that space. {{kib}} suggests a URL identifier based on the name of your space, but you can customize the identifier to your liking. You cannot change the space identifier once you create the space.
+
+2. Select a **Solution view**. This setting controls the navigation that all users of the space will get:
+   * **Search**: A light navigation menu focused on analytics and Search use cases. Features specific to Observability and Security are hidden.
+   * **Observability**: A light navigation menu focused on analytics and Observability use cases. Features specific to Search and Security are hidden.
+   * **Security**: A light navigation menu focused on analytics and Security use cases. Features specific to Observability and Search are hidden.
+   * **Classic**: All features from all solutions are visible by default using the classic, multilayered navigation menus. You can customize which features are visible individually.
+
+3. If you selected the **Classic** solution view, you can customize the **Feature visibility** as you need it to be for that space.
+
+   % This is hacking since proper admonition blocks are currently breaking my tabs
+   > **Note:** Even when disabled in this menu, some Management features can remain visible to some users depending on their privileges. Additionally, controlling feature visibility is not a security feature. To secure access to specific features on a per-user basis, you must configure [{{kib}} Security](/deploy-manage/users-roles/cluster-or-deployment-auth/built-in-roles.md).
+
+4. Customize the avatar of the space to your liking.
+5. Save your new space by selecting **Create space**.
+:::
+
+::::
+
+You can edit all of the space settings you just defined at any time, except for the URL identifier.
+
+Elastic also allows you to manage spaces using APIs: 
+
+* **Serverless projects:** [Spaces API](https://www.elastic.co/docs/api/doc/serverless/operation/operation-get-spaces-space)
+* **Non-serverless deployments:** [Spaces API](https://www.elastic.co/docs/api/doc/kibana/operation/operation-post-spaces-copy-saved-objects)
+
+
+## Define access to a space [spaces-control-user-access]
+
+**Serverless project types:** [![Elasticsearch](../images/serverless-es-badge.svg "")](/solutions/search.md) [![Security](../images/serverless-sec-badge.svg "")](/solutions/security/elastic-security-serverless.md)
+
+Users can access spaces based on the roles that they have.
+
+* Certain reserved roles can view and access all spaces by default. You can’t prevent those roles from accessing a space. Instead, you can grant different roles to your users.
+* When creating or editing a role, you can define which existing spaces that role can access, and with which permissions. Role management differs between non-serverless deployments and serverless projects.
+  - For non-Serverless deployments, check [Creating or editing a role](/deploy-manage/users-roles/cluster-or-deployment-auth/defining-roles.md).
+  - For Serverless projects, check [Custom roles](/deploy-manage/users-roles/cloud-organization/user-roles.md).
+
+
+If you're managing a non-serverless deployment, then you can also assign roles and define permissions for a space from the **Permissions** tab of the space settings. 
+
+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).
+
+
+## Configure a space-level landing page [spaces-default-route]
+
+You can create a custom experience for users by configuring the {{kib}} landing page on a per-space basis. The landing page can route users to a specific dashboard, application, or saved object as they enter each space.
+
+To configure the landing page, use the default route setting in [Stack Management > {{kib}} > Advanced settings](https://www.elastic.co/guide/en/kibana/current/advanced-options.html#kibana-general-settings). For example, you might set the default route to `/app/dashboards`.
+
+:::{image} ../images/kibana-spaces-configure-landing-page.png
+:alt: Configure space-level landing page
+:class: screenshot
+:::
\ No newline at end of file
diff --git a/deploy-manage/toc.yml b/deploy-manage/toc.yml
index 6102870923..ab1ff45994 100644
--- a/deploy-manage/toc.yml
+++ b/deploy-manage/toc.yml
@@ -678,6 +678,12 @@ 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
+  - file: manage-spaces2.md
+  - file: manage-spaces3.md
+    children: 
+      - file: manage-spaces/manage-spaces-stack.md
+      - file: manage-spaces/manage-spaces-serverless.md
+  - file: manage-spaces4.md
   - file: api-keys.md
     children:
       - file: api-keys/elasticsearch-api-keys.md