From 98a5de036bf1009ffbcf2c04011c9ad29c23ca65 Mon Sep 17 00:00:00 2001 From: Ellen Date: Mon, 9 Jun 2025 12:22:48 +1000 Subject: [PATCH 1/2] Updated documentation to include new user invite role --- .../managing-octopus-subscriptions.md | 12 ++++++------ .../getting-started-with-cloud.mdx | 19 ++++++++++--------- 2 files changed, 16 insertions(+), 15 deletions(-) diff --git a/src/pages/docs/getting-started/managing-octopus-subscriptions.md b/src/pages/docs/getting-started/managing-octopus-subscriptions.md index aa6551a45c..aeda47ef6c 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 @@ -197,13 +197,13 @@ Otherwise, they will first need to **Register** a new account using the email ad
Cloud -| | Cloud Subscription Owner | Cloud Subscription User | -| ------------ | ---------------------------------- | --------------------------------| -| **Control Center**
(billing.octopus.com)
| View Overview
Manage Billing
Manage Configuration
Manage User Access
| View Overview | -| **Octopus Instance**
(example.octopus.com)
| “Octopus Managers” team
By default, this team includes full permissions – a user can sign in and see and do everything.
| “Everyone” team
By default, this team includes no permissions – a user can sign in but can’t see or do anything.
| +| | Cloud Subscription Owner | Cloud Subscription User (Contributor) | Cloud Subscription User (Base) | +| --------------------------- | ---------------------------------------- | ------------------------------------------------ | ------------------------------------------------ | +| **Control Center**
(billing.octopus.com)
| View Overview
Manage Billing
Manage Configuration
Manage User Access
| View Overview | View Overview | +| **Octopus Instance**
(example.octopus.com)
| “Octopus Managers” team
By default, the user has full permissions across all spaces.
| “Space Managers” team
By default, the user has full permissions in the “Default” space only.
If you delete the “Default” space, the user will be added to the “Everyone” team.
| “Everyone” team
By default, the user can sign in but can't view or do anything.
| :::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). :::
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**
(billing.octopus.com)
| View Overview
Manage Billing
Manage Configuration
Manage User Access
| View Overview | -| **Octopus Instance**
(example.octopus.com)
| “Octopus Managers” team
By default, this team includes full permissions – a user can sign in and see and do everything.
| “Everyone” team
By default, this team includes no permissions – a user can sign in but can’t see or do anything.
| +| | Cloud Subscription Owner | Cloud Subscription User (Contributor) | Cloud Subscription User (Base) | +| --------------------------- | ---------------------------------------- | ------------------------------------------------ | ------------------------------------------------ | +| **Control Center**
(billing.octopus.com)
| View Overview
Manage Billing
Manage Configuration
Manage User Access
| View Overview | View Overview | +| **Octopus Instance**
(example.octopus.com)
| “Octopus Managers” team
By default, the user has full permissions across all spaces.
| “Space Managers” team
By default, the user has full permissions in the “Default” space only.
If you delete the “Default” space, the user will be added to the “Everyone” team.
| “Everyone” team
By default, the user can sign in but can't view or do anything.
| ### 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**. From 6401b136a8f1e8ec4f4b1443c46408d59a51b99b Mon Sep 17 00:00:00 2001 From: Ellen <80728059+ellen-octopus@users.noreply.github.com> Date: Tue, 1 Jul 2025 12:10:51 +1000 Subject: [PATCH 2/2] Update managing-octopus-subscriptions.md --- .../docs/getting-started/managing-octopus-subscriptions.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/pages/docs/getting-started/managing-octopus-subscriptions.md b/src/pages/docs/getting-started/managing-octopus-subscriptions.md index aeda47ef6c..deb0022444 100644 --- a/src/pages/docs/getting-started/managing-octopus-subscriptions.md +++ b/src/pages/docs/getting-started/managing-octopus-subscriptions.md @@ -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**
(billing.octopus.com)
| View Overview
Manage Billing
Manage Configuration
Manage User Access
| View Overview
Manage Configuration
Manage User Access | View Overview
Manage Billing
| -| **Octopus Instance**
(example.octopus.com)
| “Octopus Administrators" team | “Octopus Managers” team | - | +| **Octopus Instance**
(example.octopus.com)
| “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). ::: @@ -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.