diff --git a/images/custom-sso/github-oauth.png b/images/custom-sso/github-oauth.png
new file mode 100644
index 0000000..1b99b79
Binary files /dev/null and b/images/custom-sso/github-oauth.png differ
diff --git a/images/custom-sso/google-oauth.png b/images/custom-sso/google-oauth.png
new file mode 100644
index 0000000..db23a91
Binary files /dev/null and b/images/custom-sso/google-oauth.png differ
diff --git a/images/custom-sso/oidc-config.png b/images/custom-sso/oidc-config.png
deleted file mode 100644
index 2833ec7..0000000
Binary files a/images/custom-sso/oidc-config.png and /dev/null differ
diff --git a/images/custom-sso/oidc-oauth.png b/images/custom-sso/oidc-oauth.png
new file mode 100644
index 0000000..0559edc
Binary files /dev/null and b/images/custom-sso/oidc-oauth.png differ
diff --git a/images/custom-sso/saml-config.png b/images/custom-sso/saml-config.png
deleted file mode 100644
index dee392c..0000000
Binary files a/images/custom-sso/saml-config.png and /dev/null differ
diff --git a/images/custom-sso/saml-oauth.png b/images/custom-sso/saml-oauth.png
new file mode 100644
index 0000000..6df64f3
Binary files /dev/null and b/images/custom-sso/saml-oauth.png differ
diff --git a/plane-one/governance/authentication/custom-sso.mdx b/plane-one/governance/authentication/custom-sso.mdx
index 230e04f..9735267 100644
--- a/plane-one/governance/authentication/custom-sso.mdx
+++ b/plane-one/governance/authentication/custom-sso.mdx
@@ -2,7 +2,7 @@
title: OIDC and SAML
sidebarTitle: Custom SSO
---
-Plane One enables custom SSO via any identity provider with an official and supported implementation of OIDC + SAML standards. This page cites examples from Okta, but we will soon publish provider-specific instructions in phases.
+Plane enables custom SSO via any identity provider with an official and supported implementation of OIDC + SAML standards. This page cites examples from Okta, but we will soon publish provider-specific instructions in phases.
## OIDC
@@ -30,7 +30,7 @@ Go to `/god-mode/authentication/oidc` on your Plane app and find the configs ↓
Your IdP will generate some of the following configs for you. Others, you will specify yourself. Just copy them over to each field.
-
+
- Copy the `CLIENT_ID` for the Plane client or app you just created over from your IdP and paste it in the field for it.
@@ -100,7 +100,7 @@ By default, your IdP will send the value listed under `Property`. You have to ma
### On Plane
-
+
You will find all of the values for the fields below in the `/metadata` endpoint your IdP generates for the Plane app or client.
diff --git a/self-hosting/govern/github-oauth.mdx b/self-hosting/govern/github-oauth.mdx
index f5e141d..b34f67f 100644
--- a/self-hosting/govern/github-oauth.mdx
+++ b/self-hosting/govern/github-oauth.mdx
@@ -22,6 +22,8 @@ Plane also supports GitHub OAuth so your users can sign-in with GitHub instead.
## Configure Plane
+
+
1. Go to `GitHub` on the Authentication screen of `/god mode`.
2. Add the client ID + the client secret from the GitHub app you just registered.
3. Click `Save `.
diff --git a/self-hosting/govern/google-oauth.mdx b/self-hosting/govern/google-oauth.mdx
index 8f1183b..91ca977 100644
--- a/self-hosting/govern/google-oauth.mdx
+++ b/self-hosting/govern/google-oauth.mdx
@@ -25,6 +25,7 @@ First, you will need to identify Plane as an approved OAuth app to Google.

## Configure Plane
+
1. Go to `Google` on the Authentication screen of `/god mode`.
2. Add the client ID + the client secret from Google API Console.
diff --git a/self-hosting/govern/oidc-sso.mdx b/self-hosting/govern/oidc-sso.mdx
index ba664e7..ef96148 100644
--- a/self-hosting/govern/oidc-sso.mdx
+++ b/self-hosting/govern/oidc-sso.mdx
@@ -3,9 +3,9 @@ title: OIDC SSO
sidebarTitle: OIDC SSO
---
-> **Plan**: Plane One, Plane Pro
+> **Plan**: Pro, Business
-Plane One enables custom SSO via any identity provider with an official and supported implementation of OIDC standards. This page cites examples from Okta, but we will soon publish provider-specific instructions in phases.
+Plane enables custom SSO via any identity provider with an official and supported implementation of OIDC standards. This page cites examples from Okta, but we will soon publish provider-specific instructions in phases.
## OIDC
@@ -33,7 +33,7 @@ Go to `/god-mode/authentication/oidc` on your Plane app and find the configs ↓
Your IdP will generate some of the following configs for you. Others, you will specify yourself. Just copy them over to each field.
-
+
- Copy the `CLIENT_ID` for the Plane client or app you just created over from your IdP and paste it in the field for it.
diff --git a/self-hosting/govern/saml-sso.mdx b/self-hosting/govern/saml-sso.mdx
index 939dd65..d9cd150 100644
--- a/self-hosting/govern/saml-sso.mdx
+++ b/self-hosting/govern/saml-sso.mdx
@@ -3,9 +3,9 @@ title: SAML SSO
sidebarTitle: SAML SSO
---
-> **Plan**: Plane One, Plane Pro
+> **Plan**: Pro, Business
-Plane One enables custom SSO via any identity provider with an official and supported implementation of SAML standards. This page cites examples from Okta, but we will soon publish provider-specific instructions in phases.
+Plane enables custom SSO via any identity provider with an official and supported implementation of SAML standards. This page cites examples from Okta, but we will soon publish provider-specific instructions in phases.
## SAML
@@ -49,7 +49,7 @@ By default, your IdP will send the value listed under `Property`. You have to ma
### On Plane
-
+
You will find all of the values for the fields below in the `/metadata` endpoint your IdP generates for the Plane app or client.
diff --git a/self-hosting/manage/migrate-plane.mdx b/self-hosting/manage/migrate-plane.mdx
index 6d9d013..7312ea9 100644
--- a/self-hosting/manage/migrate-plane.mdx
+++ b/self-hosting/manage/migrate-plane.mdx
@@ -18,7 +18,7 @@ If you need to change your domain during migration, contact our support team for
## Steps
1. **Delink licenses**
-Log in to Plane on your current server. Head to each paid workspace like One or Pro and [delink the licenses](https://docs.plane.so/workspaces-and-users/upgrade-plan#delink-license-key). This will free up the licenses for activation on your new server. Ideally, you have just one paid workspace.
+Log in to Plane on your current server. Head to each paid workspace like Pro or Business and [delink the licenses](https://docs.plane.so/workspaces-and-users/upgrade-plan#delink-license-key). This will free up the licenses for activation on your new server. Ideally, you have just one paid workspace.
2. **Backup data**
Create a backup of your Plane instance with ↓: