Skip to content

Commit 02d805d

Browse files
Merge pull request #2743 from OctopusDeploy/ellen/user-invites-new-role
Updated documentation to include new user invite role in Control Center
2 parents 6e7d485 + 06708d6 commit 02d805d

2 files changed

Lines changed: 19 additions & 18 deletions

File tree

src/pages/docs/getting-started/managing-octopus-subscriptions.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
layout: src/layouts/Default.astro
33
pubDate: 2023-01-01
4-
modDate: 2025-05-16
4+
modDate: 2025-06-13
55
title: Managing Octopus subscriptions
66
description: Control Center is where you manage your Octopus subscriptions and their associated user access.
77
navOrder: 40
@@ -135,10 +135,10 @@ Otherwise, they will first need to **Register** a new account using the email ad
135135
| | Administrator | Technical Manager | Billing Manager |
136136
| ------------ | ------------------------ | ------------------------------ | ----------------------- |
137137
| **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 | - |
139139

140140
:::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).
142142
:::
143143

144144
</details>
@@ -197,13 +197,13 @@ Otherwise, they will first need to **Register** a new account using the email ad
197197
<details data-group="subscription-level">
198198
<summary>Cloud</summary>
199199

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> |
204204

205205
:::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).
207207
:::
208208

209209
</details>
@@ -250,4 +250,4 @@ If you need help please contact our [support team](https://octopus.com/support).
250250

251251
### What is Control Center V1?
252252

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.

src/pages/docs/octopus-cloud/getting-started-with-cloud.mdx

Lines changed: 10 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
layout: src/layouts/Default.astro
33
pubDate: 2023-01-01
4-
modDate: 2025-06-06
4+
modDate: 2025-06-13
55
title: Getting started with Cloud
66
navTitle: Getting started with Cloud
77
navOrder: 20
@@ -69,31 +69,32 @@ Otherwise, they will first need to **Register** a new account using the email ad
6969

7070
#### Role permissions \{#role-permissions}
7171

72-
| | Cloud Subscription Owner | Cloud Subscription User |
73-
| --------------------------- | --------------------------------------------------------- | ------------------------------------------------ |
74-
| **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 |
75-
| **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> |
72+
| | Cloud Subscription Owner | Cloud Subscription User (Contributor) | Cloud Subscription User (Base) |
73+
| --------------------------- | ---------------------------------------- | ------------------------------------------------ | ------------------------------------------------ |
74+
| **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 |
75+
| **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> |
7676

7777
### Manage user permissions in Octopus Cloud \{#manage-user-permissions-in-octopus-cloud}
7878

79-
Invited users are only added to an Octopus Cloud instance after their first sign-in. To manage a newly invited users permissions, you will need to ask them to sign in to your Octopus Cloud instance first.
79+
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.
8080

8181
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:
8282

8383
- “Octopus Managers” team (Cloud Subscription Owner)
84-
- “Everyone” team (Cloud Subscription User)
84+
- “Space Managers” team (Cloud Subscription User (Contributor))
85+
- “Everyone” team (Cloud Subscription User (Base))
8586

8687
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.
8788

8889
:::div{.hint}
89-
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:
90+
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:
9091

9192
- Edit the “Everyone” team to include the minimum permissions all users need.
9293
- Add the user to other teams with the correct permissions after they first sign in.
9394

9495
:::
9596

96-
To adjust a users permissions, you can add them to other teams:
97+
To adjust a user's permissions, you can add them to other teams:
9798

9899
1. In your Octopus Cloud instance, go to **Configuration** (the cog icon in the bottom left sidebar).
99100
2. Select **Teams**.

0 commit comments

Comments
 (0)