From 57b64bb6bd2ff931eff5e7e7eb9ccba5f867e7f0 Mon Sep 17 00:00:00 2001 From: Itamar Smirra Date: Mon, 3 Feb 2025 13:49:08 +0200 Subject: [PATCH] fix callout for old versions --- docs/sso-rbac/rbac/as-blueprints-beta.md | 14 ++++---------- docs/sso-rbac/rbac/no-blueprints.md | 14 ++++---------- 2 files changed, 8 insertions(+), 20 deletions(-) diff --git a/docs/sso-rbac/rbac/as-blueprints-beta.md b/docs/sso-rbac/rbac/as-blueprints-beta.md index 03fdd38fb..a67fe6aaf 100644 --- a/docs/sso-rbac/rbac/as-blueprints-beta.md +++ b/docs/sso-rbac/rbac/as-blueprints-beta.md @@ -8,18 +8,12 @@ import TabItem from '@theme/TabItem' # As blueprints (beta version - deprecated) -:::warning New default behavior -The current behavior of users and teams is deprecated and will be replaced by the new behavior starting **January 14, 2025**. -Starting **January 14, 2025**, this will be the default behavior for all new Port accounts. +:::warning Migration required +Starting **January 14, 2025**, a new default behavior for managing users & teams is applied to all new Port accounts. -- If you created your account **before** this date, and enabled the `"Users & teams as blueprints beta feature"` in your organization, continue reading this page, which describes the **beta version behavior**. -Note that this behavior will be deprecated in the near future. +If you created your account **before** this date, you will need to migrate to the new behavior using this [migration guide](/sso-rbac/rbac/migration) by **May 1, 2025**. -- If you created your account **before** this date, and **did not** enable the beta feature, see the [**old users & teams behavior**](/sso-rbac/rbac/no-blueprints) page. - -- If you created your account **after** this date, see the [**users & teams as blueprints**](/sso-rbac/rbac/as-blueprints) page. - -To migrate to the new behavior, see the [migration guide](/sso-rbac/rbac/migration). +If you enabled the `"Users & teams as blueprints beta feature"` in your organization and do not wish to migrate yet, continue reading this page, which describes the **beta version behavior**. ::: ## Overview diff --git a/docs/sso-rbac/rbac/no-blueprints.md b/docs/sso-rbac/rbac/no-blueprints.md index 0e40d66e3..9274064c7 100644 --- a/docs/sso-rbac/rbac/no-blueprints.md +++ b/docs/sso-rbac/rbac/no-blueprints.md @@ -8,18 +8,12 @@ import TabItem from '@theme/TabItem' # No blueprints (old - deprecated) -:::warning New default behavior -A new mechanism to manage users and teams has been released, using dedicated blueprints. -Starting **January 14, 2025**, this will be the default behavior for all new Port accounts. +:::warning Migration required +Starting **January 14, 2025**, a new default behavior for managing users & teams is applied to all new Port accounts. -- If you created your account **before** this date, and did not enable the `"Users & teams as blueprints beta feature"` in your organization, continue reading this page, which describes the **old behavior**. -Note that this behavior will be deprecated in the near future. +If you created your account **before** this date, you will need to migrate to the new behavior using this [migration guide](/sso-rbac/rbac/migration) by **May 1, 2025**. -- If you created your account **before** this date, and enabled the beta feature, see the [**users & teams as blueprints beta**](/sso-rbac/rbac/as-blueprints-beta) page. - -- If you created your account **after** this date, see the [**users & teams as blueprints**](/sso-rbac/rbac/as-blueprints) page. - -To migrate to the new behavior, see the [migration guide](/sso-rbac/rbac/migration). +If you do not wish to migrate yet, continue reading this page, which describes the **old behavior**. ::: ## Overview