|
1 | 1 | --- |
2 | 2 | layout: src/layouts/Default.astro |
3 | 3 | pubDate: 2023-01-01 |
4 | | -modDate: 2025-05-16 |
| 4 | +modDate: 2025-06-13 |
5 | 5 | title: Managing Octopus subscriptions |
6 | 6 | description: Control Center is where you manage your Octopus subscriptions and their associated user access. |
7 | 7 | navOrder: 40 |
@@ -135,10 +135,10 @@ Otherwise, they will first need to **Register** a new account using the email ad |
135 | 135 | | | Administrator | Technical Manager | Billing Manager | |
136 | 136 | | ------------ | ------------------------ | ------------------------------ | ----------------------- | |
137 | 137 | | **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> | |
138 | | -| **Octopus Instance** <div class="table-hint">(example.octopus.com)</div> | “Octopus Administrators" team | “Octopus Managers” team | - | |
| 138 | +| **Octopus Instance** <div class="table-hint">(example.octopus.com)</div> | “Octopus Managers" team | “Space Managers” team | - | |
139 | 139 |
|
140 | 140 | :::div{.hint} |
141 | | -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). |
| 141 | +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). |
142 | 142 | ::: |
143 | 143 |
|
144 | 144 | </details> |
@@ -197,13 +197,13 @@ Otherwise, they will first need to **Register** a new account using the email ad |
197 | 197 | <details data-group="subscription-level"> |
198 | 198 | <summary>Cloud</summary> |
199 | 199 |
|
200 | | -| | Cloud Subscription Owner | Cloud Subscription User | |
201 | | -| ------------ | ---------------------------------- | --------------------------------| |
202 | | -| **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 | |
203 | | -| **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> | |
| 200 | +| | Cloud Subscription Owner | Cloud Subscription User (Contributor) | Cloud Subscription User (Base) | |
| 201 | +| --------------------------- | ---------------------------------------- | ------------------------------------------------ | ------------------------------------------------ | |
| 202 | +| **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 | |
| 203 | +| **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> | |
204 | 204 |
|
205 | 205 | :::div{.hint} |
206 | | -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). |
| 206 | +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). |
207 | 207 | ::: |
208 | 208 |
|
209 | 209 | </details> |
@@ -250,4 +250,4 @@ If you need help please contact our [support team](https://octopus.com/support). |
250 | 250 |
|
251 | 251 | ### What is Control Center V1? |
252 | 252 |
|
253 | | -[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. |
| 253 | +[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. |
0 commit comments