fern-api · devalog · Feb 22, 2026 · Feb 22, 2026 · Feb 22, 2026
diff --git a/fern/products/api-def/asyncapi-pages/auth.mdx b/fern/products/api-def/asyncapi-pages/auth.mdx
@@ -141,7 +141,7 @@ components:
 
 ## OAuth2 security scheme
 
-<Markdown src="/snippets/pro-plan.mdx"/>
+<Markdown src="/snippets/team-or-pro-plan.mdx"/>
 
 OAuth2 authentication is supported for AsyncAPI specifications:
 

diff --git a/fern/products/api-def/asyncapi-pages/extensions/audiences.mdx b/fern/products/api-def/asyncapi-pages/extensions/audiences.mdx
@@ -4,7 +4,7 @@ headline: Use audiences to filter your API (AsyncAPI)
 subtitle: Use `x-fern-audiences` to filter to relevant operations, channels and message schemas
 ---
 
-<Markdown src="/snippets/pro-plan.mdx"/>
+<Markdown src="/snippets/team-or-pro-plan.mdx"/>
 
 Audiences are a useful tool for segmenting your event-driven API for different consumers. Common examples of audiences include `public`
 and `beta`.

diff --git a/fern/products/api-def/ferndef-pages/audiences.mdx b/fern/products/api-def/ferndef-pages/audiences.mdx
@@ -3,7 +3,7 @@ title: Audiences in Fern Definition
 subtitle: Use audiences in your Fern Definition to segment your API for different groups of consumers.
 ---
 
-<Markdown src="/snippets/pro-plan.mdx"/>
+<Markdown src="/snippets/team-or-pro-plan.mdx"/>
 
 Audiences are a useful tool for segmenting your API for different consumers. You can configure your Fern Docs to publish documentation specific to an `Audience`. You can use [audiences in your OpenAPI Specification](/learn/api-definitions/openapi/extensions/audiences), too. 
 

diff --git a/fern/products/api-def/ferndef-pages/auth.mdx b/fern/products/api-def/ferndef-pages/auth.mdx
@@ -178,7 +178,7 @@ client = new Client({
 
 ## OAuth client credentials
 
-<Markdown src="/snippets/pro-plan.mdx"/>
+<Markdown src="/snippets/team-or-pro-plan.mdx"/>
 
 If your API uses OAuth, you can specify an oauth scheme in `api.yml` and define a token retrieval endpoint in a separate `auth.yml` file ([example](https://github.com/fern-api/fern/blob/3137938b70e058f3691ddef34d5c1cc29acc4b80/test-definitions/fern/apis/oauth-client-credentials/definition/api.yml)). 
 

diff --git a/fern/products/api-def/ferndef-pages/endpoints/sse.mdx b/fern/products/api-def/ferndef-pages/endpoints/sse.mdx
@@ -3,7 +3,7 @@ title: Server-sent events and streaming APIs
 subtitle: Use the `response-stream` key to model streaming endpoints
 ---
 
-<Markdown src="/snippets/pro-plan.mdx"/>
+<Markdown src="/snippets/team-or-pro-plan.mdx"/>
 
 Specifying `response-stream` on an endpoints allows you to represent endpoint responses that are streaming. 
 

diff --git a/fern/products/api-def/openapi-pages/endpoints/sse.mdx b/fern/products/api-def/openapi-pages/endpoints/sse.mdx
@@ -39,7 +39,7 @@ components:
 
 ## Server-sent events 
 
-<Markdown src="/snippets/pro-plan.mdx"/>
+<Markdown src="/snippets/team-or-pro-plan.mdx"/>
 
 If your API returns server-sent-events (SSE), with the `data` and `event` keys as seen below
 

diff --git a/fern/products/api-def/openapi-pages/extensions/audiences.mdx b/fern/products/api-def/openapi-pages/extensions/audiences.mdx
@@ -4,7 +4,7 @@ headline: Use audiences to filter your API (OpenAPI)
 subtitle: Learn how to use x-fern-audiences to filter OpenAPI endpoints, schemas, and properties for different API consumers like public and beta users.
 ---
 
-<Markdown src="/snippets/pro-plan.mdx"/>
+<Markdown src="/snippets/team-or-pro-plan.mdx"/>
 
 Fern provides two ways to filter which API elements appear in your SDKs and API Reference docs:
 

diff --git a/fern/products/dashboard/pages/pdf-export.mdx b/fern/products/dashboard/pages/pdf-export.mdx
@@ -3,7 +3,7 @@ title: PDF export
 description: Export your documentation site as a PDF from the Fern Dashboard.
 ---
 
-<Markdown src="/snippets/pro-plan.mdx"/>
+<Markdown src="/snippets/team-plan.mdx"/>
 
 Export your complete documentation site as a PDF directly from the [Fern Dashboard](https://dashboard.buildwithfern.com/). The generated PDF includes a cover page, table of contents with clickable links, and all content pages with headers and footers.
 

diff --git a/fern/products/docs/pages/api-references/audiences.mdx b/fern/products/docs/pages/api-references/audiences.mdx
@@ -3,7 +3,7 @@ title: Audiences
 subtitle: Use audiences to filter the endpoints, schemas, and properties that are displayed in your API Reference.
 ---
 
-<Markdown src="/snippets/pro-plan.mdx"/>
+<Markdown src="/snippets/team-plan.mdx"/>
 
 Audiences are a useful tool for segmenting your API for different consumers. Common examples of audiences include `public` 
 and `beta`. You can configure audiences in both [the OpenAPI Specification](/learn/api-definitions/openapi/extensions/audiences) as well as [the Fern Definition](/learn/api-definition/fern/audiences).

diff --git a/fern/products/docs/pages/ask-fern/api-get-started.mdx b/fern/products/docs/pages/ask-fern/api-get-started.mdx
@@ -3,7 +3,7 @@ title: 'Introduction'
 subtitle: 'Welcome to the Fern API Reference.'
 ---
 
-<Markdown src="/snippets/pro-plan.mdx" />
+<Markdown src="/snippets/team-plan.mdx" />
 
 The Fern AI API allows you to manage your Ask Fern configuration using Fern's public RESTful API. You can use the API to:
 

diff --git a/fern/products/docs/pages/authentication/password.mdx b/fern/products/docs/pages/authentication/password.mdx
@@ -3,7 +3,7 @@ title: Password protection
 subtitle: Protect your documentation site with a shared password for simple access control.
 ---
 
-<Markdown src="/snippets/pro-plan.mdx"/>
+<Markdown src="/snippets/team-plan.mdx"/>
 
 Password protection allows you to restrict access to your documentation site using a shared password. This is useful for pre-release documentation, internal resources, or any content you want to keep private without requiring individual user accounts.
 

diff --git a/fern/products/docs/pages/getting-started/setting-up-your-domain.mdx b/fern/products/docs/pages/getting-started/setting-up-your-domain.mdx
@@ -75,7 +75,7 @@ Once Fern has completed your setup, you'll be able to access your documentation
 
 <Accordion title="Subpath">
 
-<Markdown src="/snippets/pro-plan.mdx"/>
+<Markdown src="/snippets/team-plan.mdx"/>
 
 To host your documentation on a subpath like `mydomain.com/docs`, you need to edit your `docs.yml` configuration and then get provider-specific instructions for setting up the subpath. Common providers include Cloudflare, AWS Route53 and Cloudfront, Netlify, and Vercel.
 

diff --git a/fern/products/docs/pages/integrations/feature-flags.mdx b/fern/products/docs/pages/integrations/feature-flags.mdx
@@ -4,7 +4,7 @@ subtitle: Control documentation visibility with LaunchDarkly
 description: Learn how to use Feature Flags in your Fern documentation
 ---
 
-<Markdown src="/snippets/pro-plan.mdx"/>
+<Markdown src="/snippets/team-plan.mdx"/>
 
 Fern supports conditional rendering of documentation content using feature flags, powered by [LaunchDarkly](https://app.launchdarkly.com/signup) integration. Control visibility of documentation sections based on feature flag states for different release stages or user segments.
 

diff --git a/fern/products/docs/pages/navigation/products.mdx b/fern/products/docs/pages/navigation/products.mdx
@@ -3,7 +3,7 @@ title: Product switching
 subtitle: Learn how to configure product switching in Fern Docs. Set up multiple products with custom navigation, versioning, and styling options.
 ---
 
-<Markdown src="/snippets/pro-plan.mdx"/>
+<Markdown src="/snippets/team-plan.mdx"/>
 
 <Frame>
   <video 

diff --git a/fern/products/docs/pages/navigation/versions.mdx b/fern/products/docs/pages/navigation/versions.mdx
@@ -4,7 +4,7 @@ subtitle: Learn how to add versioning to your Fern documentation. Configure mult
 ---
 
 <Warning>
-  Versioning is available on [all plans](https://buildwithfern.com/pricing#Docs): up to 3 versions on Hobby, 10 versions on Pro, or unlimited on Enterprise. Contact support@buildwithfern.com for more information.
+  Versioning is available on [all plans](https://buildwithfern.com/pricing#Docs): up to 3 versions on Hobby, 10 versions on Team, or unlimited on Enterprise. Contact support@buildwithfern.com for more information.
 </Warning>
 
 <Frame>

diff --git a/fern/snippets/pro-plan.mdx b/fern/snippets/pro-plan.mdx
@@ -1,3 +1,3 @@
 <Warning title="Pro and Enterprise feature">
     This feature is available only for the [Pro and Enterprise plans](https://buildwithfern.com/pricing). To get started, reach out to support@buildwithfern.com.
-</Warning>
+</Warning>
diff --git a/fern/snippets/team-or-pro-plan.mdx b/fern/snippets/team-or-pro-plan.mdx
@@ -0,0 +1,3 @@
+<Warning title="Team, Pro, and Enterprise feature">
+    This feature is available only for the [Team (Docs), Pro (SDKs), and Enterprise plans](https://buildwithfern.com/pricing). To get started, reach out to support@buildwithfern.com.
+</Warning>
diff --git a/fern/snippets/team-plan.mdx b/fern/snippets/team-plan.mdx
@@ -0,0 +1,3 @@
+<Warning title="Team and Enterprise feature">
+    This feature is available only for the [Team and Enterprise plans](https://buildwithfern.com/pricing). To get started, reach out to support@buildwithfern.com.
+</Warning>
-Original file line number
+Diff line change
@@ Expand Up / @@ -3,7 +3,7 @@ title: Product switching @@
     subtitle: Learn how to configure product switching in Fern Docs. Set up multiple products with custom navigation, versioning, and styling options.
     ---
-    <Markdown src="/snippets/pro-plan.mdx"/>
+    <Markdown src="/snippets/team-plan.mdx"/>
     <Frame>
       <video
@@ Expand Down @@