From c9767152b8bc02c9293b879b5e02eb7c3237aab4 Mon Sep 17 00:00:00 2001 From: Lawrence Lee Keener Date: Tue, 21 Jul 2026 10:29:21 -0500 Subject: [PATCH 1/5] Document KOTS/kURL adoption for the new Enterprise Portal MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Explains how vendors can move KOTS/kURL customers onto the new Enterprise Portal today: the per-customer Portal Version toggle, its Vendor API equivalent, pairing it with the separate Security Center toggle, why there's no single app-level switch for an existing customer base, and how Download Portal, Classic Enterprise Portal, and the new Enterprise Portal coexist. Scoped to what's currently merged (KOTS/kURL instance visibility, license labeling, Security Center gating) — install/upgrade commands, default download pages, and air gap instance creation for KOTS/kURL are still in flight and intentionally left out. Co-Authored-By: Claude Sonnet 5 --- docs/vendor/enterprise-portal-v2-about.mdx | 34 ++++++++++++++++++++-- docs/vendor/enterprise-portal-v2-use.mdx | 14 +++++++-- 2 files changed, 42 insertions(+), 6 deletions(-) diff --git a/docs/vendor/enterprise-portal-v2-about.mdx b/docs/vendor/enterprise-portal-v2-about.mdx index 4a203044b0..7167017b9f 100644 --- a/docs/vendor/enterprise-portal-v2-about.mdx +++ b/docs/vendor/enterprise-portal-v2-about.mdx @@ -36,9 +36,9 @@ The new Enterprise Portal is a complete rebuild of the customer portal experienc ## Current limitations {#current-limitations} -- Installation and upgrade instructions are available only for Embedded Cluster and Helm CLI installations. The Enterprise Portal does not provide instructions for KOTS or kURL. -- Air gap instance records do not appear until the customer creates one from the Instances & Updates page, either by manually entering instance information or by extracting details from an uploaded support bundle. -- Security Center data (CVE reports and SBOMs) is available for Helm and Embedded Cluster installations only. Security data is not displayed for KOTS or kURL installations. +- Step-by-step, in-console install and upgrade instructions, and structured install-step customization, are available only for Embedded Cluster and Helm CLI installations. The Enterprise Portal does not provide install or upgrade commands for KOTS or kURL. For more information, see [KOTS and kURL customers](#kots-and-kurl-customers). +- Air gap instance records do not appear until the customer creates one from the Instances & Updates page, either by manually entering instance information or by extracting details from an uploaded support bundle. This is available for Embedded Cluster and Helm air gap installations. It is not yet available for KOTS or kURL, so only KOTS and kURL instances that have already checked in appear in the portal. +- Security Center data (CVE reports and SBOMs) is available for Helm and Embedded Cluster installations only. Customers whose only instances are KOTS or kURL do not see Security Center at all. Customers with a mix of instance types see Security Center data for their Helm and Embedded Cluster instances. - If you have many version branches and need to make a change across all versions, you must update each branch individually. ## Requirements @@ -70,3 +70,31 @@ The new Enterprise Portal runs at a different domain (`{appSlug}.enterpriseporta ### Vendor Portal view vs. customer portal version The **New Portal** / **Classic Portal** toggle appears only in mixed mode. It controls the Vendor Portal view that you see. It does not change which portal your customers see. Use the Portal Version toggle on each customer's EP access tab to change their portal. + +## KOTS and kURL customers {#kots-and-kurl-customers} + +The Classic Enterprise Portal never supported KOTS or kURL installations. Customers using these install types have historically used the [Download Portal](/vendor/releases-share-download-portal) instead. The new Enterprise Portal supports KOTS and kURL customers as well, with some differences from Helm and Embedded Cluster customers. For details on what your KOTS and kURL customers see, including current limitations, see [KOTS and kURL instances](/vendor/enterprise-portal-v2-use#kots-and-kurl-instances) in _Log in to and Use the Enterprise Portal_. + +### Move a KOTS or kURL customer to the new Enterprise Portal + +On the customer's **Enterprise Portal access** tab, switch **Portal Version** to the new Enterprise Portal. This is the same toggle used for Helm and Embedded Cluster customers. There is no separate setting based on install type. + +Changing a customer's Portal Version immediately invalidates their active Enterprise Portal sessions. The next time the customer logs in, they land on the portal version you selected. + +To automate this instead of using the Vendor Portal UI, use [Update Enterprise Portal settings](https://replicated-vendor-api.readme.io/reference/updateenterpriseportalsettings) in the Vendor API v3 with `portalVersion: "v2"`. For more information, see [Customer access](/vendor/enterprise-portal-v2-vendor-api-automation#customer-access) in _Enterprise Portal Headless Automation_. + +If you also want this customer to see Security Center, enable it on the same **Enterprise Portal access** tab. This is a separate toggle from Portal Version. For a KOTS or kURL customer, Security Center only shows data after the customer also has a Helm or Embedded Cluster instance. See [Security](/vendor/enterprise-portal-v2-use#security). For more information about the Security Center toggle, see [Enable Customer Access to Security Information](/vendor/security-center-enable-customer-access). + +### Enable the new Enterprise Portal for all customers + +There is no single switch that moves your entire existing customer base to the new Enterprise Portal at once. The Portal Version setting is per customer, and any customer without an explicit setting stays on their current portal (Classic Enterprise Portal or Download Portal). Enabling mixed mode for your app does not move any existing customers, including those on KOTS or kURL. After you move them, KOTS and kURL customers land on a portal that supports their install type, including instance visibility and license information. See [KOTS and kURL instances](/vendor/enterprise-portal-v2-use#kots-and-kurl-instances) for what's supported today. + +To move many customers at once, call [Update Enterprise Portal settings](https://replicated-vendor-api.readme.io/reference/updateenterpriseportalsettings) for each customer instead of switching them individually in Vendor Portal. + +New customers that you create after you enable mixed mode default to the new Enterprise Portal, regardless of install type. + +### Portal coexistence + +You can run the Download Portal, the Classic Enterprise Portal, and the new Enterprise Portal at the same time, with different customers on each. This is an intended, ongoing state, not only a step along the way to a full migration. Each customer's Portal Version is independent, so you can move customers over gradually and leave others on their current portal indefinitely. + +Moving a customer's Portal Version to the new Enterprise Portal does not disable their Download Portal access. The two are independent. If a KOTS or kURL customer relies on the Download Portal today, you can keep sharing that link. This works even after you move them to the new Enterprise Portal. diff --git a/docs/vendor/enterprise-portal-v2-use.mdx b/docs/vendor/enterprise-portal-v2-use.mdx index 750839764e..8e209785e9 100644 --- a/docs/vendor/enterprise-portal-v2-use.mdx +++ b/docs/vendor/enterprise-portal-v2-use.mdx @@ -32,7 +32,7 @@ All users invited to the same customer team share access to the same pull tokens Once logged in, customers see a sidebar with the navigation defined by the vendor's `toc.yaml`. The default template organizes content into: -- **Installation**: Requirements, release history, and step-by-step install instructions for Linux and Helm +- **Installation**: Requirements, release history, and step-by-step install instructions for Linux (Embedded Cluster) and Helm - **Operations**: Security reports and support bundle management - **Updates**: Check for updates and follow upgrade instructions - **Support**: FAQ and contact support information @@ -76,6 +76,14 @@ Depending on the install method and license entitlements, customers can download For Embedded Cluster air gap installations, customers using a private registry can enter their registry hostname directly in the install flow. The instructions update to include image pull, tag, and push commands targeting that registry, along with the appropriate `--registry` flags on the install command. This is also available during Embedded Cluster upgrades when the instance was originally installed with a private registry. +### KOTS and kURL instances {#kots-and-kurl-instances} + +KOTS and kURL instances appear on the **Instances & Updates** page alongside Helm and Embedded Cluster instances, labeled **KOTS** or **kURL**. Each instance shows its current version and status. + +The Enterprise Portal does not provide step-by-step, in-console install or upgrade instructions for KOTS or kURL. These instance cards don't expand into inline upgrade steps the way Helm and Embedded Cluster cards do. + +Air gap instance records for KOTS and kURL are not yet available. Only KOTS and kURL instances that have already checked in appear in the portal. Customers can't manually add a record or extract one from a support bundle for these install types yet. + ## Team management Customer team admins can manage their portal team from the Team Settings page: @@ -112,9 +120,9 @@ When Security Center is enabled by the vendor, customers with Helm or Embedded C - **SBOMs**: Download the Software Bill of Materials for any release version. SBOMs are accessible to all portal team members regardless of role. :::note -Security Center data is available for Helm and Embedded Cluster installations only. Security data is not displayed for KOTS or kURL installations. +Security Center data is available for Helm and Embedded Cluster installations only. KOTS and kURL instances don't contribute CVE data or upgrade recommendations, and they aren't counted toward instance totals in Security Center. Customers whose only instances are KOTS or kURL don't see Security Center at all. Customers with a mix of instance types still see Security Center for their Helm and Embedded Cluster instances. ::: ## License information -Customers can view their license details including expiration date, license type, assigned channel, and any custom license fields configured by the vendor. This information is accessible from the portal but is read-only for customers. +Customers can view their license details including expiration date, license type, assigned channel, and any custom license fields configured by the vendor. This information is accessible from the portal but is read-only for customers. License details, including the install type label (Helm, Linux (Embedded Cluster), KOTS, or kURL), display correctly regardless of which install types the customer uses. From ab6ff9c3e32f9875d3da87f1d9e614f537c7d604 Mon Sep 17 00:00:00 2001 From: Lawrence Lee Keener Date: Tue, 21 Jul 2026 12:00:39 -0500 Subject: [PATCH 2/5] Add KOTS/kURL air gap instance creation now that sc-138600 merged MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Restores the manual/support-bundle air gap instance record creation content for KOTS/kURL that was trimmed earlier — vandoor PR #10233 merged, so this is now live. Co-Authored-By: Claude Sonnet 5 --- docs/vendor/enterprise-portal-v2-about.mdx | 2 +- docs/vendor/enterprise-portal-v2-use.mdx | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/vendor/enterprise-portal-v2-about.mdx b/docs/vendor/enterprise-portal-v2-about.mdx index 7167017b9f..a0200eae6a 100644 --- a/docs/vendor/enterprise-portal-v2-about.mdx +++ b/docs/vendor/enterprise-portal-v2-about.mdx @@ -37,7 +37,7 @@ The new Enterprise Portal is a complete rebuild of the customer portal experienc ## Current limitations {#current-limitations} - Step-by-step, in-console install and upgrade instructions, and structured install-step customization, are available only for Embedded Cluster and Helm CLI installations. The Enterprise Portal does not provide install or upgrade commands for KOTS or kURL. For more information, see [KOTS and kURL customers](#kots-and-kurl-customers). -- Air gap instance records do not appear until the customer creates one from the Instances & Updates page, either by manually entering instance information or by extracting details from an uploaded support bundle. This is available for Embedded Cluster and Helm air gap installations. It is not yet available for KOTS or kURL, so only KOTS and kURL instances that have already checked in appear in the portal. +- Air gap instance records do not appear until the customer creates one from the Instances & Updates page, either by manually entering instance information or by extracting details from an uploaded support bundle. Availability depends on the customer's license having the corresponding install type and air gap option enabled. - Security Center data (CVE reports and SBOMs) is available for Helm and Embedded Cluster installations only. Customers whose only instances are KOTS or kURL do not see Security Center at all. Customers with a mix of instance types see Security Center data for their Helm and Embedded Cluster instances. - If you have many version branches and need to make a change across all versions, you must update each branch individually. diff --git a/docs/vendor/enterprise-portal-v2-use.mdx b/docs/vendor/enterprise-portal-v2-use.mdx index 8e209785e9..c13e469107 100644 --- a/docs/vendor/enterprise-portal-v2-use.mdx +++ b/docs/vendor/enterprise-portal-v2-use.mdx @@ -82,7 +82,7 @@ KOTS and kURL instances appear on the **Instances & Updates** page alongside Hel The Enterprise Portal does not provide step-by-step, in-console install or upgrade instructions for KOTS or kURL. These instance cards don't expand into inline upgrade steps the way Helm and Embedded Cluster cards do. -Air gap instance records for KOTS and kURL are not yet available. Only KOTS and kURL instances that have already checked in appear in the portal. Customers can't manually add a record or extract one from a support bundle for these install types yet. +Customers can create air gap instance records for KOTS and kURL the same way as for Helm and Embedded Cluster. They can enter instance information manually from the Instances & Updates page, or extract details from an uploaded support bundle. Availability depends on the customer's license having the corresponding install type and air gap option enabled. ## Team management From a47fa3f40dd09b9dc2d5f6c3f5225836df07186a Mon Sep 17 00:00:00 2001 From: Lawrence Lee Keener Date: Tue, 21 Jul 2026 16:37:29 -0500 Subject: [PATCH 3/5] Address review: correct toggle flow, terminology, and Security Center wording - Fix the customer move flow: Enterprise Portal access must be enabled before the Portal Version control appears (two steps, not one) - Add the real app-level bulk toggle (Enable Enterprise Portal for all customers) in place of the incorrect 'no single switch exists' claim - Drop the 'new customers default to v2' claim (depends on team config, not safe to generalize) - Fix per-customer coexistence: access is an alternative to the Download Portal for a given customer, not concurrent with it - Remove the 'license label list' claim that doesn't match the UI - Reword 'do not see Security Center at all' to 'see an explanatory message instead of security data' (3 places) - Remove internal 'mixed mode' terminology; use real button/toggle labels - Present-tense the Classic EP / Download Portal relationship - Simplify 'structured install-step customization' jargon - Consolidate general bulk-enable/coexistence content into the existing Classic Enterprise Portal section per review feedback --- docs/vendor/enterprise-portal-v2-about.mdx | 47 +++++++++------------- docs/vendor/enterprise-portal-v2-use.mdx | 4 +- 2 files changed, 22 insertions(+), 29 deletions(-) diff --git a/docs/vendor/enterprise-portal-v2-about.mdx b/docs/vendor/enterprise-portal-v2-about.mdx index a0200eae6a..4ba6b541c2 100644 --- a/docs/vendor/enterprise-portal-v2-about.mdx +++ b/docs/vendor/enterprise-portal-v2-about.mdx @@ -36,9 +36,9 @@ The new Enterprise Portal is a complete rebuild of the customer portal experienc ## Current limitations {#current-limitations} -- Step-by-step, in-console install and upgrade instructions, and structured install-step customization, are available only for Embedded Cluster and Helm CLI installations. The Enterprise Portal does not provide install or upgrade commands for KOTS or kURL. For more information, see [KOTS and kURL customers](#kots-and-kurl-customers). +- Installation and upgrade instructions are available only for Embedded Cluster and Helm CLI installations. The Enterprise Portal does not provide instructions for KOTS or kURL. For more information, see [KOTS and kURL customers](#kots-and-kurl-customers). - Air gap instance records do not appear until the customer creates one from the Instances & Updates page, either by manually entering instance information or by extracting details from an uploaded support bundle. Availability depends on the customer's license having the corresponding install type and air gap option enabled. -- Security Center data (CVE reports and SBOMs) is available for Helm and Embedded Cluster installations only. Customers whose only instances are KOTS or kURL do not see Security Center at all. Customers with a mix of instance types see Security Center data for their Helm and Embedded Cluster instances. +- Security Center data (CVE reports and SBOMs) is available for Helm and Embedded Cluster installations only. Customers whose only instances are KOTS or kURL see an explanatory message instead of security data. Customers with a mix of instance types see Security Center data for their Helm and Embedded Cluster instances. - If you have many version branches and need to make a change across all versions, you must update each branch individually. ## Requirements @@ -55,46 +55,39 @@ Some Enterprise Portal capabilities require additional access: ## For vendors already using the Classic Enterprise Portal -If your team already uses the Classic Enterprise Portal, you can adopt the New Enterprise Portal incrementally. To avoid disrupting existing customers, run both portal versions in mixed mode. +If your team already uses the Classic Enterprise Portal, you can adopt the new Enterprise Portal incrementally. Run both portals side by side, then move customers over individually or all at once. The new Enterprise Portal runs at a different domain (`{appSlug}.enterpriseportal.app`) than Classic (`get.replicated.com/{appSlug}/...`). Both portals share the same backend, so customer data, licenses, and instance information are consistent across both. -### How to get started +### How to get started {#how-to-get-started} -1. **Enable mixed mode.** Contact Replicated to run the New Enterprise Portal alongside the Classic Enterprise Portal. Customers continue using their current portal until you move them to the new version. +1. **Run both portals side by side.** Contact Replicated to enable the new Enterprise Portal for your team alongside the Classic Enterprise Portal. Customers continue using their current portal until you move them. 1. **Connect a content repo.** Follow the setup steps in [Connect a Git Repo](/vendor/enterprise-portal-v2-connect-repo). Connecting a repo has zero effect on any customer's portal version. No customer sees the new portal until you explicitly switch them. -1. **Test it yourself.** Use the local CLI preview (`replicated enterprise-portal preview`) or open the new portal URL directly to see how your content renders. The Vendor Portal also has a "Login as customer" button on each customer's EP access tab. -1. **Move individual customers.** On the customer's **Enterprise Portal access** tab in Vendor Portal, set the **Portal Version** toggle to use the new Enterprise Portal. Only that customer is affected. -1. **Move customers back if needed.** Set the Portal Version toggle back to Classic at any time. The customer immediately returns to the Classic experience. +1. **Test it yourself.** Use the local CLI preview (`replicated enterprise-portal preview`) or open the new portal URL directly to see how your content renders. The Vendor Portal also has a "Login as customer" button on each customer's Enterprise Portal access tab. +1. **Move individual customers.** On the customer's **Enterprise Portal access** tab, set **Portal Version** to **Use new Enterprise Portal for this customer**. This affects only that customer. If the customer doesn't have Enterprise Portal access yet, turn on **Enable Enterprise Portal for this customer** first — the Portal Version control only appears after access is on. +1. **Move customers back if needed.** Set Portal Version back to Classic at any time. The customer immediately returns to the Classic experience. +1. **Move everyone at the same time, if you don't need a gradual rollout.** On **Enterprise Portal > Customer Access**, turn on **Enable Enterprise Portal for all customers** to move every customer, including those on KOTS or kURL, off the Download Portal immediately. This doesn't change any customer's individual access or Portal Version setting — it overrides the result while it's on, and turning it back off returns each customer to their individual setting. ### Vendor Portal view vs. customer portal version -The **New Portal** / **Classic Portal** toggle appears only in mixed mode. It controls the Vendor Portal view that you see. It does not change which portal your customers see. Use the Portal Version toggle on each customer's EP access tab to change their portal. +The **New Portal** / **Classic Portal** toggle appears only when both portals are running for your team. It controls the Vendor Portal view that you see. It does not change which portal your customers see. Use each customer's **Portal Version** setting to change their portal. -## KOTS and kURL customers {#kots-and-kurl-customers} - -The Classic Enterprise Portal never supported KOTS or kURL installations. Customers using these install types have historically used the [Download Portal](/vendor/releases-share-download-portal) instead. The new Enterprise Portal supports KOTS and kURL customers as well, with some differences from Helm and Embedded Cluster customers. For details on what your KOTS and kURL customers see, including current limitations, see [KOTS and kURL instances](/vendor/enterprise-portal-v2-use#kots-and-kurl-instances) in _Log in to and Use the Enterprise Portal_. - -### Move a KOTS or kURL customer to the new Enterprise Portal - -On the customer's **Enterprise Portal access** tab, switch **Portal Version** to the new Enterprise Portal. This is the same toggle used for Helm and Embedded Cluster customers. There is no separate setting based on install type. - -Changing a customer's Portal Version immediately invalidates their active Enterprise Portal sessions. The next time the customer logs in, they land on the portal version you selected. +### Portal coexistence -To automate this instead of using the Vendor Portal UI, use [Update Enterprise Portal settings](https://replicated-vendor-api.readme.io/reference/updateenterpriseportalsettings) in the Vendor API v3 with `portalVersion: "v2"`. For more information, see [Customer access](/vendor/enterprise-portal-v2-vendor-api-automation#customer-access) in _Enterprise Portal Headless Automation_. +You can run the Download Portal and the new Enterprise Portal side by side, with different customers on each, indefinitely. This is intended and ongoing, not only a step toward a full migration. -If you also want this customer to see Security Center, enable it on the same **Enterprise Portal access** tab. This is a separate toggle from Portal Version. For a KOTS or kURL customer, Security Center only shows data after the customer also has a Helm or Embedded Cluster instance. See [Security](/vendor/enterprise-portal-v2-use#security). For more information about the Security Center toggle, see [Enable Customer Access to Security Information](/vendor/security-center-enable-customer-access). +For a single customer, though, these are alternatives, not concurrent options. Turning on Enterprise Portal access for a customer moves that customer off the Download Portal onto whichever portal version their Portal Version setting selects. -### Enable the new Enterprise Portal for all customers +## KOTS and kURL customers {#kots-and-kurl-customers} -There is no single switch that moves your entire existing customer base to the new Enterprise Portal at once. The Portal Version setting is per customer, and any customer without an explicit setting stays on their current portal (Classic Enterprise Portal or Download Portal). Enabling mixed mode for your app does not move any existing customers, including those on KOTS or kURL. After you move them, KOTS and kURL customers land on a portal that supports their install type, including instance visibility and license information. See [KOTS and kURL instances](/vendor/enterprise-portal-v2-use#kots-and-kurl-instances) for what's supported today. +The Classic Enterprise Portal does not support KOTS or kURL installations. Customers using these install types use the [Download Portal](/vendor/releases-share-download-portal) instead. The new Enterprise Portal supports KOTS and kURL customers as well, with some differences from Helm and Embedded Cluster customers. For details on what your KOTS and kURL customers see, including current limitations, see [KOTS and kURL instances](/vendor/enterprise-portal-v2-use#kots-and-kurl-instances) in _Log in to and Use the Enterprise Portal_. -To move many customers at once, call [Update Enterprise Portal settings](https://replicated-vendor-api.readme.io/reference/updateenterpriseportalsettings) for each customer instead of switching them individually in Vendor Portal. +### Move a KOTS or kURL customer to the new Enterprise Portal -New customers that you create after you enable mixed mode default to the new Enterprise Portal, regardless of install type. +Follow the steps in [How to get started](#how-to-get-started) to run the new Enterprise Portal for your team. This works the same way for KOTS and kURL customers as it does for Helm and Embedded Cluster customers. The app-level **Enable Enterprise Portal for all customers** option applies to KOTS and kURL customers too. -### Portal coexistence +One thing to plan for: most KOTS and kURL customers don't have Enterprise Portal access enabled yet, since they've been using the Download Portal. You need to turn on **Enable Enterprise Portal for this customer** before the **Portal Version** control appears. Classic Enterprise Portal does not support KOTS or kURL. Leaving Portal Version at its default after enabling access does not give the customer a working portal. Set it to **Use new Enterprise Portal for this customer** explicitly. -You can run the Download Portal, the Classic Enterprise Portal, and the new Enterprise Portal at the same time, with different customers on each. This is an intended, ongoing state, not only a step along the way to a full migration. Each customer's Portal Version is independent, so you can move customers over gradually and leave others on their current portal indefinitely. +To automate this instead of using the Vendor Portal UI: use [Patch a customer](https://replicated-vendor-api.readme.io/reference/patchcustomer) with `is_enterprise_portal_enabled: true` to grant access, then [Update Enterprise Portal settings](https://replicated-vendor-api.readme.io/reference/updateenterpriseportalsettings) with `portalVersion: "v2"` to select the new Enterprise Portal. For more information, see [Customer access](/vendor/enterprise-portal-v2-vendor-api-automation#customer-access) in _Enterprise Portal Headless Automation_. -Moving a customer's Portal Version to the new Enterprise Portal does not disable their Download Portal access. The two are independent. If a KOTS or kURL customer relies on the Download Portal today, you can keep sharing that link. This works even after you move them to the new Enterprise Portal. +If you also want this customer to see Security Center, enable it on the same **Enterprise Portal access** tab. This is a separate toggle from Portal Version. For a KOTS or kURL customer, Security Center shows an explanatory message instead of security data until they also have a Helm or Embedded Cluster instance. See [Security](/vendor/enterprise-portal-v2-use#security). For more information about the Security Center toggle, see [Enable Customer Access to Security Information](/vendor/security-center-enable-customer-access). diff --git a/docs/vendor/enterprise-portal-v2-use.mdx b/docs/vendor/enterprise-portal-v2-use.mdx index c13e469107..619035ab19 100644 --- a/docs/vendor/enterprise-portal-v2-use.mdx +++ b/docs/vendor/enterprise-portal-v2-use.mdx @@ -120,9 +120,9 @@ When Security Center is enabled by the vendor, customers with Helm or Embedded C - **SBOMs**: Download the Software Bill of Materials for any release version. SBOMs are accessible to all portal team members regardless of role. :::note -Security Center data is available for Helm and Embedded Cluster installations only. KOTS and kURL instances don't contribute CVE data or upgrade recommendations, and they aren't counted toward instance totals in Security Center. Customers whose only instances are KOTS or kURL don't see Security Center at all. Customers with a mix of instance types still see Security Center for their Helm and Embedded Cluster instances. +Security Center data is available for Helm and Embedded Cluster installations only. KOTS and kURL instances don't contribute CVE data or upgrade recommendations, and they aren't counted toward instance totals in Security Center. Customers whose only instances are KOTS or kURL see an explanatory message instead of security data. Customers with a mix of instance types still see Security Center for their Helm and Embedded Cluster instances. ::: ## License information -Customers can view their license details including expiration date, license type, assigned channel, and any custom license fields configured by the vendor. This information is accessible from the portal but is read-only for customers. License details, including the install type label (Helm, Linux (Embedded Cluster), KOTS, or kURL), display correctly regardless of which install types the customer uses. +Customers can view their license details including expiration date, license type, assigned channel, and any custom license fields configured by the vendor. This information is accessible from the portal but is read-only for customers. License details display correctly regardless of which install types the customer uses. From 5366d1f0efc23c36003424915450f75b092ef1ed Mon Sep 17 00:00:00 2001 From: Lawrence Lee Keener Date: Wed, 22 Jul 2026 11:47:09 -0500 Subject: [PATCH 4/5] Fix vale flags from CI review: WordSwaps and Passive voice - 'at once' -> 'all together' (Replicated.WordSwaps: once) - 'This is intended and ongoing' -> 'Treat this as an ongoing state' (Replicated.Passive) - 'is read-only for customers' -> 'cannot edit it' (Replicated.Passive) --- docs/vendor/enterprise-portal-v2-about.mdx | 4 ++-- docs/vendor/enterprise-portal-v2-use.mdx | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/vendor/enterprise-portal-v2-about.mdx b/docs/vendor/enterprise-portal-v2-about.mdx index 4ba6b541c2..b6c06af398 100644 --- a/docs/vendor/enterprise-portal-v2-about.mdx +++ b/docs/vendor/enterprise-portal-v2-about.mdx @@ -55,7 +55,7 @@ Some Enterprise Portal capabilities require additional access: ## For vendors already using the Classic Enterprise Portal -If your team already uses the Classic Enterprise Portal, you can adopt the new Enterprise Portal incrementally. Run both portals side by side, then move customers over individually or all at once. +If your team already uses the Classic Enterprise Portal, you can adopt the new Enterprise Portal incrementally. Run both portals side by side, then move customers over individually or all together. The new Enterprise Portal runs at a different domain (`{appSlug}.enterpriseportal.app`) than Classic (`get.replicated.com/{appSlug}/...`). Both portals share the same backend, so customer data, licenses, and instance information are consistent across both. @@ -74,7 +74,7 @@ The **New Portal** / **Classic Portal** toggle appears only when both portals ar ### Portal coexistence -You can run the Download Portal and the new Enterprise Portal side by side, with different customers on each, indefinitely. This is intended and ongoing, not only a step toward a full migration. +You can run the Download Portal and the new Enterprise Portal side by side, with different customers on each, indefinitely. Treat this as an ongoing state, not only a step toward a full migration. For a single customer, though, these are alternatives, not concurrent options. Turning on Enterprise Portal access for a customer moves that customer off the Download Portal onto whichever portal version their Portal Version setting selects. diff --git a/docs/vendor/enterprise-portal-v2-use.mdx b/docs/vendor/enterprise-portal-v2-use.mdx index 619035ab19..2e26810065 100644 --- a/docs/vendor/enterprise-portal-v2-use.mdx +++ b/docs/vendor/enterprise-portal-v2-use.mdx @@ -125,4 +125,4 @@ Security Center data is available for Helm and Embedded Cluster installations on ## License information -Customers can view their license details including expiration date, license type, assigned channel, and any custom license fields configured by the vendor. This information is accessible from the portal but is read-only for customers. License details display correctly regardless of which install types the customer uses. +Customers can view their license details including expiration date, license type, assigned channel, and any custom license fields configured by the vendor. Customers can access this information from the portal but cannot edit it. License details display correctly regardless of which install types the customer uses. From e14007f41ffc6110cb3d173d17768cdd2e2beadc Mon Sep 17 00:00:00 2001 From: Lawrence Lee Keener Date: Thu, 23 Jul 2026 15:15:59 -0500 Subject: [PATCH 5/5] Revert license information wording to original per review Reverts the reword of the read-only license details sentence back to the original text. Not part of this PR's scope. --- docs/vendor/enterprise-portal-v2-use.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/vendor/enterprise-portal-v2-use.mdx b/docs/vendor/enterprise-portal-v2-use.mdx index 2e26810065..e7dcc88172 100644 --- a/docs/vendor/enterprise-portal-v2-use.mdx +++ b/docs/vendor/enterprise-portal-v2-use.mdx @@ -125,4 +125,4 @@ Security Center data is available for Helm and Embedded Cluster installations on ## License information -Customers can view their license details including expiration date, license type, assigned channel, and any custom license fields configured by the vendor. Customers can access this information from the portal but cannot edit it. License details display correctly regardless of which install types the customer uses. +Customers can view their license details including expiration date, license type, assigned channel, and any custom license fields configured by the vendor. This information is accessible from the portal but is read-only for customers.