diff --git a/src/pages/docs/getting-started/managing-octopus-subscriptions.md b/src/pages/docs/getting-started/managing-octopus-subscriptions.md
index aa6551a45c..deb0022444 100644
--- a/src/pages/docs/getting-started/managing-octopus-subscriptions.md
+++ b/src/pages/docs/getting-started/managing-octopus-subscriptions.md
@@ -1,7 +1,7 @@
 ---
 layout: src/layouts/Default.astro
 pubDate: 2023-01-01
-modDate: 2025-05-16
+modDate: 2025-06-13
 title: Managing Octopus subscriptions
 description: Control Center is where you manage your Octopus subscriptions and their associated user access. 
 navOrder: 40
@@ -135,10 +135,10 @@ Otherwise, they will first need to **Register** a new account using the email ad
 |              | Administrator            | Technical Manager              | Billing Manager         |
 | ------------ | ------------------------ | ------------------------------ | ----------------------- |
 | **Control Center** <div class="table-hint">(billing.octopus.com)</div> | View Overview <br>Manage Billing</br> Manage Configuration <br>Manage User Access</br> | View Overview <br>Manage Configuration</br> Manage User Access | View Overview <br>Manage Billing</br> |
-| **Octopus Instance** <div class="table-hint">(example.octopus.com)</div> | “Octopus Administrators" team | “Octopus Managers” team | -  |
+| **Octopus Instance** <div class="table-hint">(example.octopus.com)</div> | “Octopus Managers" team | “Space Managers” team | -  |
 
 :::div{.hint}
-Octopus uses teams and user roles to manage permissions. The “Octopus Administrators” and “Octopus Managers” teams provide different levels of access in your instance. Learn about best practices for [users, roles, and teams](/docs/best-practices/octopus-administration/users-roles-and-teams).
+Octopus uses teams and user roles to manage permissions. The “Octopus Managers” and “Space Managers” teams provide different levels of access in your instance. Learn about best practices for [users, roles, and teams](/docs/best-practices/octopus-administration/users-roles-and-teams).
 :::
 
 </details>
@@ -197,13 +197,13 @@ Otherwise, they will first need to **Register** a new account using the email ad
 <details data-group="subscription-level">
 <summary>Cloud</summary>
 
-|              | Cloud Subscription Owner           | Cloud Subscription User         |
-| ------------ | ---------------------------------- | --------------------------------|
-| **Control Center** <div class="table-hint">(billing.octopus.com)</div> | View Overview <br>Manage Billing</br> Manage Configuration <br>Manage User Access</br> | View Overview |
-| **Octopus Instance** <div class="table-hint">(example.octopus.com)</div> | “Octopus Managers” team <div class="table-hint">By default, this team includes full permissions – a user can sign in and see and do everything.</div>| “Everyone” team  <div class="table-hint">By default, this team includes no permissions – a user can sign in but can’t see or do anything.</div> |
+|                             | Cloud Subscription Owner                 | Cloud Subscription User (Contributor)            | Cloud Subscription User (Base)                   |
+| --------------------------- | ---------------------------------------- | ------------------------------------------------ | ------------------------------------------------ |
+| **Control Center** <div class="table-hint">(billing.octopus.com)</div> | View Overview <br>Manage Billing</br> Manage Configuration <br>Manage User Access</br> | View Overview | View Overview |
+| **Octopus Instance** <div class="table-hint">(example.octopus.com)</div> | “Octopus Managers” team <div class="table-hint">By default, the user has full permissions across all spaces.</div>| “Space Managers” team  <div class="table-hint">By default, the user has full permissions in the “Default” space only.</div> <div class="table-hint" style="padding-top: 8px;">If you delete the “Default” space, the user will be added to the “Everyone” team.</div> | “Everyone” team  <div class="table-hint">By default, the user can sign in but can't view or do anything.</div> |
 
 :::div{.hint}
-Octopus uses teams and user roles to manage permissions. The “Octopus Managers” and “Everyone” teams provide different levels of access in your instance. Learn about best practices for [users, roles, and teams](/docs/best-practices/octopus-administration/users-roles-and-teams).
+Octopus uses teams and user roles to manage permissions. The “Octopus Managers”, “Space Managers”, and “Everyone” teams provide different levels of access in your instance. Learn about best practices for [users, roles, and teams](/docs/best-practices/octopus-administration/users-roles-and-teams).
 :::
 
 </details>
@@ -250,4 +250,4 @@ If you need help please contact our [support team](https://octopus.com/support).
 
 ### What is Control Center V1?
 
-[Control Center V1](https://octopus.com/control-center) is our legacy system where legacy subscriptions are managed. You should only access Control Center V1 if you need to manage a legacy subscription.
\ No newline at end of file
+[Control Center V1](https://octopus.com/control-center) is our legacy system where legacy subscriptions are managed. You should only access Control Center V1 if you need to manage a legacy subscription.
diff --git a/src/pages/docs/octopus-cloud/getting-started-with-cloud.mdx b/src/pages/docs/octopus-cloud/getting-started-with-cloud.mdx
index a9a6610fae..97ab3f8e82 100644
--- a/src/pages/docs/octopus-cloud/getting-started-with-cloud.mdx
+++ b/src/pages/docs/octopus-cloud/getting-started-with-cloud.mdx
@@ -1,7 +1,7 @@
 ---
 layout: src/layouts/Default.astro
 pubDate: 2023-01-01
-modDate: 2025-06-06
+modDate: 2025-06-13
 title: Getting started with Cloud
 navTitle: Getting started with Cloud
 navOrder: 20
@@ -69,31 +69,32 @@ Otherwise, they will first need to **Register** a new account using the email ad
 
 #### Role permissions \{#role-permissions}
 
-|                             | Cloud Subscription Owner                                  | Cloud Subscription User                          |
-| --------------------------- | --------------------------------------------------------- | ------------------------------------------------ |
-| **Control Center** <div class="table-hint">(billing.octopus.com)</div> | View Overview <br>Manage Billing</br> Manage Configuration <br>Manage User Access</br> | View Overview |
-| **Octopus Instance** <div class="table-hint">(example.octopus.com)</div> | “Octopus Managers” team <div class="table-hint">By default, this team includes full permissions – a user can sign in and see and do everything.</div>| “Everyone” team  <div class="table-hint">By default, this team includes no permissions – a user can sign in but can’t see or do anything.</div> |
+|                             | Cloud Subscription Owner                 | Cloud Subscription User (Contributor)            | Cloud Subscription User (Base)                   |
+| --------------------------- | ---------------------------------------- | ------------------------------------------------ | ------------------------------------------------ |
+| **Control Center** <div class="table-hint">(billing.octopus.com)</div> | View Overview <br>Manage Billing</br> Manage Configuration <br>Manage User Access</br> | View Overview | View Overview |
+| **Octopus Instance** <div class="table-hint">(example.octopus.com)</div> | “Octopus Managers” team <div class="table-hint">By default, the user has full permissions across all spaces.</div>| “Space Managers” team  <div class="table-hint">By default, the user has full permissions in the “Default” space only.</div> <div class="table-hint" style="padding-top: 8px;">If you delete the “Default” space, the user will be added to the “Everyone” team.</div> | “Everyone” team  <div class="table-hint">By default, the user can sign in but can't view or do anything.</div> |
 
 ### Manage user permissions in Octopus Cloud \{#manage-user-permissions-in-octopus-cloud}
 
-Invited users are only added to an Octopus Cloud instance after their first sign-in. To manage a newly invited user’s permissions, you will need to ask them to sign in to your Octopus Cloud instance first.
+Invited users are only added to an Octopus Cloud instance after their first sign-in. To manage a newly invited user's permissions, you will need to ask them to sign in to your Octopus Cloud instance first.
 
 Octopus uses teams and user roles to manage permissions. After the invited user first signs in, they are automatically assigned to one of these teams:
 
 - “Octopus Managers” team (Cloud Subscription Owner)
-- “Everyone” team (Cloud Subscription User)
+- “Space Managers” team (Cloud Subscription User (Contributor))
+- “Everyone” team (Cloud Subscription User (Base))
 
 By default, the “Everyone” team includes no user roles, so users assigned to this team can sign in to your Octopus Cloud instance but won’t have permission to see or do anything.
 
 :::div{.hint}
-To give an “Everyone” team user (Cloud Subscription User) the correct permissions, you can do one or both of the following in your Octopus Cloud instance:
+To give an “Everyone” team user (Cloud Subscription User (Base)) the correct permissions, you can do one or both of the following in your Octopus Cloud instance:
 
 - Edit the “Everyone” team to include the minimum permissions all users need.
 - Add the user to other teams with the correct permissions after they first sign in.
 
 :::
 
-To adjust a user’s permissions, you can add them to other teams:
+To adjust a user's permissions, you can add them to other teams:
 
 1. In your Octopus Cloud instance, go to **Configuration** (the cog icon in the bottom left sidebar).
 2. Select **Teams**.