gravitational · ptgott · Mar 7, 2024 · Mar 5, 2024
diff --git a/docs/config.json b/docs/config.json
@@ -31,18 +31,12 @@
             {
               "title": "Teleport Cloud Agents (Linux)",
               "slug": "/upgrading/cloud-linux/",
-              "forScopes": [
-                "cloud",
-                "team"
-              ]
+              "forScopes": ["cloud"]
             },
             {
               "title": "Teleport Cloud Agents (Kubernetes)",
               "slug": "/upgrading/cloud-kubernetes/",
-              "forScopes": [
-                "cloud",
-                "team"
-              ]
+              "forScopes": ["cloud"]
             },
             {
               "title": "Self-Hosted Linux",
@@ -76,11 +70,7 @@
         {
           "title": "Usage Reporting and Billing",
           "slug": "/usage-billing/",
-          "forScopes": [
-            "cloud",
-            "team",
-            "enterprise"
-          ]
+          "forScopes": ["cloud", "enterprise"]
         },
         {
           "title": "Upcoming Releases",
@@ -108,20 +98,18 @@
           "title": "Introduction",
           "slug": "/choose-an-edition/introduction/"
         },
-        {
-          "title": "Teleport Team",
-          "slug": "/choose-an-edition/teleport-team/",
-          "forScopes": [
-            "team"
-          ]
-        },
         {
           "title": "Teleport Enterprise Cloud",
           "slug": "/choose-an-edition/teleport-cloud/introduction/",
           "forScopes": [
             "cloud"
           ],
           "entries": [
+            {
+              "title": "Get Started",
+              "slug": "/choose-an-edition/teleport-cloud/get-started/",
+              "forScopes": ["cloud"]
+            },
             {
               "title": "Architecture",
               "slug": "/choose-an-edition/teleport-cloud/architecture/",
@@ -421,12 +409,7 @@
         {
           "title": "Single Sign-On (SSO)",
           "slug": "/access-controls/sso/",
-          "forScopes": [
-            "oss",
-            "team",
-            "enterprise",
-            "cloud"
-          ],
+          "forScopes": ["oss", "enterprise", "cloud"],
           "entries": [
             {
               "title": "Active Directory (ADFS)",
@@ -447,12 +430,7 @@
             {
               "title": "GitHub",
               "slug": "/access-controls/sso/github-sso/",
-              "forScopes": [
-                "oss",
-                "team",
-                "enterprise",
-                "cloud"
-              ]
+              "forScopes": ["oss", "enterprise", "cloud"]
             },
             {
               "title": "GitLab",
@@ -499,47 +477,27 @@
         {
           "title": "Teleport as an IdP",
           "slug": "/access-controls/idps/",
-          "forScopes": [
-            "enterprise",
-            "cloud",
-            "team"
-          ],
+          "forScopes": ["enterprise", "cloud"],
           "entries": [
             {
               "title": "SAML Identity Provider Guide",
               "slug": "/access-controls/idps/saml-guide/",
-              "forScopes": [
-                "enterprise",
-                "cloud",
-                "team"
-              ]
+              "forScopes": ["enterprise", "cloud"]
             },
             {
               "title": "SAML Attribute Mapping",
               "slug": "/access-controls/idps/saml-attribute-mapping/",
-              "forScopes": [
-                "enterprise",
-                "cloud",
-                "team"
-              ]
+              "forScopes": ["enterprise", "cloud"]
             },
             {
               "title": "Authenticate to Grafana with Teleport SAML",
               "slug": "/access-controls/idps/saml-grafana/",
-              "forScopes": [
-                "enterprise",
-                "cloud",
-                "team"
-              ]
+              "forScopes": ["enterprise", "cloud"]
             },
             {
               "title": "SAML Identity Provider Reference",
               "slug": "/access-controls/idps/saml-reference/",
-              "forScopes": [
-                "enterprise",
-                "cloud",
-                "team"
-              ]
+              "forScopes": ["enterprise", "cloud"]
             }
           ]
         },
@@ -589,35 +547,31 @@
           "slug": "/access-controls/device-trust/",
           "forScopes": [
             "enterprise",
-            "cloud",
-            "team"
+            "cloud"
           ],
           "entries": [
             {
               "title": "Getting Started",
               "slug": "/access-controls/device-trust/guide/",
               "forScopes": [
                 "enterprise",
-                "cloud",
-                "team"
+                "cloud"
               ]
             },
             {
               "title": "Manage Trusted Devices",
               "slug": "/access-controls/device-trust/device-management/",
               "forScopes": [
                 "enterprise",
-                "cloud",
-                "team"
+                "cloud"
               ]
             },
             {
               "title": "Enforce Device Trust",
               "slug": "/access-controls/device-trust/enforcing-device-trust/",
               "forScopes": [
                 "enterprise",
-                "cloud",
-                "team"
+                "cloud"
               ]
             },
             {
@@ -660,7 +614,6 @@
           "title": "Access Graph",
           "slug": "/access-controls/access-graph/",
           "forScopes": [
-            "team",
             "enterprise"
           ],
           "entries": [
@@ -2720,7 +2673,7 @@
     },
     {
       "source": "/cloud/getting-started/",
-      "destination": "/choose-an-edition/teleport-team/",
+      "destination": "/choose-an-edition/teleport-cloud/get-started/",
       "permanent": true
     },
     {
@@ -2985,7 +2938,7 @@
     },
     {
       "source": "/deploy-a-cluster/teleport-cloud/getting-started/",
-      "destination": "/choose-an-edition/teleport-team/",
+      "destination": "/choose-an-edition/teleport-cloud/get-started/",
       "permanent": true
     },
     {
@@ -3085,7 +3038,7 @@
     },
     {
       "source": "/choose-an-edition/teleport-cloud/getting-started/",
-      "destination": "/choose-an-edition/teleport-team/",
+      "destination": "/choose-an-edition/teleport-cloud/get-started/",
       "permanent": true
     },
     {
@@ -3492,6 +3445,11 @@
       "source": "/server-access/guides/openssh/openssh/",
       "destination": "/server-access/openssh/openssh/",
       "permanent": true
+    },
+    {
+      "source": "/choose-an-edition/teleport-team/",
+      "destination": "/choose-an-edition/teleport-cloud/get-started/",
+      "permanent": true
     }
   ]
 }
diff --git a/docs/pages/access-controls/access-graph.mdx b/docs/pages/access-controls/access-graph.mdx
@@ -4,8 +4,7 @@ description: A reference for Teleport Access Graph.
 ---
 
 <Admonition type="tip" title="Preview">
-  Teleport Access Graph is currently in Preview. Currently, it is only available
-  to Teleport Team users, and only visualizes access to resources enrolled with your Teleport clusters.
+  Teleport Access Graph is currently in Preview.
 </Admonition>
 
 Teleport Access Graph visualizes and helps you understand access to your
@@ -17,6 +16,10 @@ questions like:
 - What users can access a specific resource?
 - What are the relationships between users, roles, and resources?
 
+Teleport Access Graph is a feature of the [Teleport
+Policy](https://goteleport.com/platform/policy/) product that is only available
+to Teleport Enterprise customers.
+
 After logging into the Teleport UI, go to the Management tab. If enabled, Access Graph options can be found
 under the Permission Management section.
 

diff --git a/docs/pages/access-controls/access-graph/self-hosted-helm.mdx b/docs/pages/access-controls/access-graph/self-hosted-helm.mdx
@@ -14,9 +14,9 @@ and enable the Access Graph feature in your Teleport cluster.
 
 The full listing of supported parameters can be found in the [`teleport-access-graph` Helm chart reference](../../reference/helm-reference/teleport-access-graph.mdx).
 
-Teleport Access Graph is enabled by default for Teleport Team users.
-You can skip the setup process and start using Access Graph right away
-by signing up for a [Teleport Team trial](https://goteleport.com/signup/).
+Teleport Access Graph is a feature of the [Teleport
+Policy](https://goteleport.com/platform/policy/) product that is only available
+to Teleport Enterprise customers.
 
 ## Prerequisites
 

diff --git a/docs/pages/access-controls/access-graph/self-hosted.mdx b/docs/pages/access-controls/access-graph/self-hosted.mdx
@@ -12,9 +12,9 @@ to collect information about resources and access.
 This guide will help you set up the TAG service
 and enable the Access Graph feature in your Teleport cluster.
 
-Teleport Access Graph is enabled by default for Teleport Team users.
-You can skip the setup process here and start using Access Graph right away
-by signing up for a [Teleport Team trial](https://goteleport.com/signup/).
+Teleport Access Graph is a feature of the [Teleport
+Policy](https://goteleport.com/platform/policy/) product that is only available
+to Teleport Enterprise customers.
 
 ## Prerequisites
 

diff --git a/docs/pages/access-controls/idps/saml-guide.mdx b/docs/pages/access-controls/idps/saml-guide.mdx
@@ -24,7 +24,7 @@ authenticate to external services.
 
 The minimum configuration values required to add a service provider are:
 1. **Entity ID:** The SAML metadata endpoint of the service provider.
-2. **ACS URL:** The endpoint where users will be redirected after SAML authentication. ACS URL
+1. **ACS URL:** The endpoint where users will be redirected after SAML authentication. ACS URL
 is also referred to as SAML SSO URL.
 
 The following `saml_idp_service_provider` spec is a reference for adding samltest.id to Teleport:

diff --git a/docs/pages/access-controls/sso/github-sso.mdx b/docs/pages/access-controls/sso/github-sso.mdx
@@ -12,9 +12,8 @@ Teleport.
 
 - A GitHub organization with at least one team. 
 
-  In Teleport Community Edition and Teleport Team, this organization must not
-  have external SSO set up, or Teleport will refuse to create the GitHub
-  authentication connector.
+  In Teleport Community Edition, this organization must not have external SSO
+  set up, or Teleport will refuse to create the GitHub authentication connector.
 
   In Teleport Enterprise and Enterprise Cloud, organization can be hosted from
   either GitHub Cloud or GitHub Enterprise Server.

diff --git a/docs/pages/access-controls/sso/okta.mdx b/docs/pages/access-controls/sso/okta.mdx
@@ -16,9 +16,9 @@ Teleport administrators to define policies like:
 
 <Details title="Automated SSO connection with Okta integration" open={false}>
 
-In Teleport Team, Teleport Enterprise Cloud and Self-Hosted Teleport Enterprise,
-Teleport can automatically configure an SSO connector for you when as part of 
-[enrolling the hosted Okta integration](../../).
+In Teleport Enterprise Cloud and Self-Hosted Teleport Enterprise, Teleport can
+automatically configure an SSO connector for you when as part of [enrolling the
+hosted Okta integration](../../).
 
 You can enroll the Okta integration from the Teleport Web UI.
 

diff --git a/docs/pages/agents/deploy-agents-terraform.mdx b/docs/pages/agents/deploy-agents-terraform.mdx
@@ -36,7 +36,7 @@ see how an agent pool works. After you are familiar with the setup, apply the
 lessons from this guide to protect your infrastructure. You can get started with
 a demo cluster using:
 - A demo deployment on a [Linux server](../index.mdx)
-- A [Teleport Team trial](https://goteleport.com/signup)
+- A [Teleport Enterprise Cloud trial](https://goteleport.com/signup)
 
 </Admonition>
 
@@ -45,9 +45,9 @@ a demo cluster using:
 
 - Cloud infrastructure that enables virtual machine instances to connect to the
   Teleport Proxy Service. For example:
-    - An AWS subnet with a public NAT gateway or NAT instance.
-    - Google Cloud NAT
-    - Azure NAT Gateway
+  - An AWS subnet with a public NAT gateway or NAT instance.
+  - Google Cloud NAT
+  - Azure NAT Gateway
 
   In minimum-security demo clusters, you can also configure the VM instances you
   deploy to have public IP addresses.

diff --git a/docs/pages/ai-assist.mdx b/docs/pages/ai-assist.mdx
@@ -28,15 +28,9 @@ Before you get started with Teleport Assist, make sure you have the following:
 - **OpenAI Account**: You will need an active OpenAI account with GPT-4 API
   access as Teleport Assist relies on OpenAI services.
 
-<Notice type="note">
-If you don't have access to OpenAI GPT-4 API, you can still try out Teleport
-Assist by signing up for a
-[Teleport Team plan](https://goteleport.com/pricing/).
-</Notice>
-
 Teleport Assist currently doesn't support Teleport clusters using the etcd backend.
 If your installation is using etcd, you can create a new cluster with
-any other backend or sign up for the Teleport Team plan.
+any other backend.
 
 ## Step 1/3. Generate an OpenAI API key
 

diff --git a/docs/pages/choose-an-edition/introduction.mdx b/docs/pages/choose-an-edition/introduction.mdx
@@ -8,15 +8,6 @@ which edition is most appropriate for your use case.
 
 ## Editions
 
-### Teleport Team
-
-Teleport Team makes it easier for small organizations to get started enabling
-secure access to their infrastructure. It includes a subset of Teleport
-Enterprise Cloud features, and teams can switch to Teleport Enterprise Cloud as
-they scale up.
-
-[Read more about Teleport Team](./teleport-team.mdx).
-
 ### Teleport Enterprise Cloud
 
 Our team at Teleport manages the Auth and Proxy Services, giving you a running

diff --git a/docs/pages/choose-an-edition/teleport-cloud/external-audit-storage.mdx b/docs/pages/choose-an-edition/teleport-cloud/external-audit-storage.mdx
@@ -24,8 +24,7 @@ above.
 ## Prerequisites
 
 1. A Teleport Enterprise Cloud account. If you do not have one, [sign
-   up](https://goteleport.com/signup/) for a Teleport Team account and upgrade
-   to Teleport Enterprise Cloud.
+   up](https://goteleport.com/signup/) for a free trial.
 1. To store and query audit events and session recordings, you need to set up
    the following four components in an AWS account of your choosing. The
    Teleport Web UI walks you through the infrastructure you need to create, but