cloudflare · deadlypants1973 · Jun 5, 2025 · Jun 4, 2025 · windsurf-bot · Jun 4, 2025
@@ -5,6 +5,10 @@ sidebar:
   order: 12
 ---
 
+import { Render } from "~/components";
+
+<Render file="survey" />
+
 This page lists the default account limits for rules, applications, fields, and other features. These limits may be increased on Enterprise accounts. To request a limit increase, contact your account team.
 
 ## Access

@@ -3,10 +3,11 @@ pcx_content_type: navigation
 title: API and Terraform
 sidebar:
   order: 10
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing, Render } from "~/components";
+
+<Render file="survey" />
 
 This section covers a few common use cases with the API and Terraform to manage Cloudflare Zero Trust. For more information, refer to our [API documentation](/api/) and [Terraform reference guide](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs).
 

@@ -10,6 +10,8 @@ learning_center:
 
 import { GlossaryTooltip, Render } from "~/components";
 
+<Render file="survey" />
+
 :::note[Availability]
 Available for all Zero Trust users.
 

@@ -3,9 +3,12 @@ pcx_content_type: concept
 title: Add web applications
 sidebar:
   order: 1
-
 ---
 
+import { Render } from "~/components";
+
+<Render file="survey" />
+
 Cloudflare Access allows you to secure your web applications by acting as an identity aggregator, or proxy. You can use signals from your existing identity providers (IdPs), device posture providers, and [other rules](/cloudflare-one/policies/access/#selectors) to control who can log in to the application.
 
 ![Cloudflare Access verifies a user's identity before granting access to your application.](~/assets/images/cloudflare-one/applications/diagram-saas.jpg)
@@ -15,7 +18,8 @@ You can protect the following types of web applications:
 - [**SaaS applications**](/cloudflare-one/applications/configure-apps/saas-apps/) consist of applications your team relies on that are not hosted by your organization. Examples include Salesforce and Workday. To secure SaaS applications, you must integrate Cloudflare Access with the SaaS application's SSO configuration.
 
 - **Self-hosted applications** consist of internal applications that you host in your own environment. These can be the data center versions of tools like the Atlassian suite or applications created by your own team. Setup requirements for a self-hosted application depend on whether the application is publicly accessible on the Internet or restricted to users on a private network.
-	- [**Public hostname applications**](/cloudflare-one/applications/configure-apps/self-hosted-public-app/) are web applications that have public DNS records. Anyone on the Internet can access the application by entering the URL in their browser and authenticating through Cloudflare Access. Securing access to a public website requires a Cloudflare DNS [full setup](/dns/zone-setups/full-setup/) or [partial CNAME setup](/dns/zone-setups/partial-setup/).
-	- [**Private network applications**](/cloudflare-one/applications/non-http/self-hosted-private-app/) do not have public DNS records, meaning they are not reachable from the public Internet. To connect using a private IP or private hostname, the user's traffic must route through Cloudflare Gateway. The preferred method is to install the WARP client on the user's device, but you could also forward device traffic from a [network location](/magic-wan/) or use an agentless option such as [PAC files](/cloudflare-one/connections/connect-devices/agentless/pac-files/) or [Clientless Web Isolation](/cloudflare-one/policies/browser-isolation/setup/clientless-browser-isolation/).
 
-- [**Cloudflare Dashboard SSO**](/cloudflare-one/applications/configure-apps/dash-sso-apps/) is a special type of SaaS application that manages SSO settings for the Cloudflare dashboard and has limited permissions for administrator edits.
+  - [**Public hostname applications**](/cloudflare-one/applications/configure-apps/self-hosted-public-app/) are web applications that have public DNS records. Anyone on the Internet can access the application by entering the URL in their browser and authenticating through Cloudflare Access. Securing access to a public website requires a Cloudflare DNS [full setup](/dns/zone-setups/full-setup/) or [partial CNAME setup](/dns/zone-setups/partial-setup/).
+  - [**Private network applications**](/cloudflare-one/applications/non-http/self-hosted-private-app/) do not have public DNS records, meaning they are not reachable from the public Internet. To connect using a private IP or private hostname, the user's traffic must route through Cloudflare Gateway. The preferred method is to install the WARP client on the user's device, but you could also forward device traffic from a [network location](/magic-wan/) or use an agentless option such as [PAC files](/cloudflare-one/connections/connect-devices/agentless/pac-files/) or [Clientless Web Isolation](/cloudflare-one/policies/browser-isolation/setup/clientless-browser-isolation/).
+
+- [**Cloudflare Dashboard SSO**](/cloudflare-one/applications/configure-apps/dash-sso-apps/) is a special type of SaaS application that manages SSO settings for the Cloudflare dashboard and has limited permissions for administrator edits.
@@ -3,10 +3,11 @@ pcx_content_type: navigation
 title: Applications
 sidebar:
   order: 6
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing, Render } from "~/components";
+
+<Render file="survey" />
 
 Cloudflare Zero Trust can secure self-hosted and SaaS applications with Zero Trust rules.
 

@@ -5,6 +5,10 @@ sidebar:
   order: 1
 ---
 
+import { Render } from "~/components";
+
+<Render file="survey" />
+
 Cloudflare offers both client-based and clientless ways to grant secure access to non-HTTP applications.
 
 :::note

@@ -7,7 +7,9 @@ head:
 description: Review recent changes to Cloudflare Access.
 ---
 
-import { ProductChangelog } from "~/components";
+import { ProductChangelog, Render } from "~/components";
+
+<Render file="survey" />
 
 {/* <!-- All changelog entries live in src/content/changelogs/access/. */}
 

@@ -7,7 +7,9 @@ head:
 description: Review recent changes to Cloudflare Browser Isolation.
 ---
 
-import { ProductChangelog } from "~/components";
+import { ProductChangelog, Render } from "~/components";
+
+<Render file="survey" />
 
 {/* <!-- All changelog entries live in src/content/changelogs/browser-isolation/. */}
 

@@ -7,7 +7,9 @@ head:
 description: Review recent changes to Cloudflare CASB.
 ---
 
-import { ProductChangelog } from "~/components";
+import { ProductChangelog, Render } from "~/components";
+
+<Render file="survey" />
 
 {/* <!-- All changelog entries live in src/content/changelogs/casb/. */}
 

@@ -7,7 +7,9 @@ head:
 description: Review recent changes to Digital Experience Monitoring.
 ---
 
-import { ProductChangelog } from "~/components";
+import { ProductChangelog, Render } from "~/components";
+
+<Render file="survey" />
 
 {/* <!-- All changelog entries live in src/content/changelogs/dex/. */}
 

@@ -7,7 +7,9 @@ head:
 description: Review recent changes to Cloudflare DLP.
 ---
 
-import { ProductChangelog } from "~/components";
+import { ProductChangelog, Render } from "~/components";
+
+<Render file="survey" />
 
 {/* <!-- All changelog entries live in src/content/changelogs/dlp/. */}
 

@@ -3,7 +3,9 @@ pcx_content_type: changelog
 title: Email Security
 ---
 
-import { ProductChangelog } from "~/components";
+import { ProductChangelog, Render } from "~/components";
+
+<Render file="survey" />
 
 {/* <!-- All changelog entries live in src/content/changelogs/email-security/. */}
 

@@ -7,7 +7,9 @@ head:
 description: Review recent changes to Cloudflare Gateway.
 ---
 
-import { ProductChangelog } from "~/components";
+import { ProductChangelog, Render } from "~/components";
+
+<Render file="survey" />
 
 {/* <!-- All changelog entries live in src/content/changelogs/gateway/. */}
 

@@ -7,7 +7,9 @@ head: []
 description: Review recent changes to Cloudflare One.
 ---
 
-import { ProductChangelog } from "~/components";
+import { ProductChangelog, Render } from "~/components";
+
+<Render file="survey" />
 
 {/* <!-- All changelog entries live in associated src/content/changelogs/. */}
 

@@ -7,7 +7,9 @@ head:
 description: Review recent changes to Cloudflare Zero Trust user risk scoring.
 ---
 
-import { ProductChangelog } from "~/components";
+import { ProductChangelog, Render } from "~/components";
+
+<Render file="survey" />
 
 {/* <!-- All changelog entries live in src/content/changelogs/risk-score/. */}
 

@@ -7,7 +7,9 @@ head:
 description: Review recent changes to Cloudflare Tunnel.
 ---
 
-import { ProductChangelog } from "~/components";
+import { ProductChangelog, Render } from "~/components";
+
+<Render file="survey" />
 
 {/* <!-- All changelog entries live in src/content/changelogs/cloudflare-tunnel/. */}
 

@@ -7,7 +7,9 @@ head:
 description: Review recent changes to the Zero Trust WARP client.
 ---
 
-import { ProductChangelog } from "~/components";
+import { ProductChangelog, Render } from "~/components";
+
+<Render file="survey" />
 
 {/* <!-- All changelog entries live in src/content/warp-releases/. For more details, refer to https://developers.cloudflare.com/style-guide/documentation-content-strategy/content-types/changelog/#yaml-file --> */}
 

@@ -3,10 +3,11 @@ pcx_content_type: navigation
 title: Connect devices
 sidebar:
   order: 4
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing, Render } from "~/components";
+
+<Render file="survey" />
 
 Configure devices to send DNS queries to Cloudflare, or proxy all traffic leaving the device through Cloudflare's network.
 

@@ -5,6 +5,10 @@ sidebar:
   order: 1
 ---
 
+import { Render } from "~/components";
+
+<Render file="survey" />
+
 Cloudflare Tunnel provides you with a secure way to connect your resources to Cloudflare without a publicly routable IP address. With Tunnel, you do not send traffic to an external IP — instead, a lightweight daemon in your infrastructure (`cloudflared`) creates outbound-only connections to Cloudflare's global network. Cloudflare Tunnel can connect HTTP web servers, [SSH servers](/cloudflare-one/connections/connect-networks/use-cases/ssh/), [remote desktops](/cloudflare-one/connections/connect-networks/use-cases/rdp/), and other protocols safely to Cloudflare. This way, your origins can serve traffic through Cloudflare without being vulnerable to attacks that bypass Cloudflare.
 
 Refer to our [reference architecture](/reference-architecture/architectures/sase/) for details on how to implement Cloudflare Tunnel into your existing infrastructure.
@@ -20,4 +24,4 @@ Cloudflared establishes outbound connections (tunnels) between your resources an
 - Create a tunnel using the [Cloudflare dashboard](/cloudflare-one/connections/connect-networks/get-started/create-remote-tunnel/) or [API](/cloudflare-one/connections/connect-networks/get-started/create-remote-tunnel-api/).
 - Learn more about [`cloudflared`](/cloudflare-one/connections/connect-networks/downloads/), the server-side daemon that connects your infrastructure to Cloudflare.
 - Review useful [Tunnel terms](/cloudflare-one/connections/connect-networks/get-started/tunnel-useful-terms/) to familiarize yourself with the concepts used in Tunnel documentation.
-- [Troubleshoot](/cloudflare-one/connections/connect-networks/troubleshoot-tunnels/) your Tunnel by reviewing available logs and common errors.
+- [Troubleshoot](/cloudflare-one/connections/connect-networks/troubleshoot-tunnels/) your Tunnel by reviewing available logs and common errors.
@@ -5,15 +5,15 @@ sidebar:
   order: 9
 ---
 
-import { Description } from "~/components"
+import { Description, Render } from "~/components";
+
+<Render file="survey" />
 
 :::caution[Important]
 Refer to [Area 1](/email-security/) if you are looking for the Area 1 documentation.
 :::
 
-<Description>
-Secure your email inbox with Email Security.
-</Description>
+<Description>Secure your email inbox with Email Security.</Description>
 
 Email Security secures your email inbox by integrating with your existing email provider and blocking phishing attacks, malware, [Business Email Compromise](https://www.cloudflare.com/en-gb/learning/email-security/business-email-compromise-bec/) attacks, and vendor email fraud.
 
@@ -38,4 +38,4 @@ Once you have completed the setup process, the Email Security overview will disp
 - A series of recommendations. For example, you may be recommended to learn how to submit emails for reclassification, create policies, or learn how to manage your [impersonation registry](/cloudflare-one/email-security/detection-settings/impersonation-registry/).
 - Email Security metrics (your email security activity from the last 7 days).
 - Recently modified policies, where you will be able to view all modified policies.
-- Education and resources: Links to [implementation guides](/cloudflare-one/implementation-guides/), [Email Security changelogs](/cloudflare-one/changelog/email-security/), and [API documentation](https://developers.cloudflare.com/api/resources/email_security/subresources/investigate/methods/get/).
+- Education and resources: Links to [implementation guides](/cloudflare-one/implementation-guides/), [Email Security changelogs](/cloudflare-one/changelog/email-security/), and [API documentation](https://developers.cloudflare.com/api/resources/email_security/subresources/investigate/methods/get/).
@@ -7,7 +7,9 @@ sidebar:
   order: 16
 ---
 
-import { LinkButton } from "~/components";
+import { LinkButton, Render } from "~/components";
+
+<Render file="survey" />
 
 Review answers to the most commonly asked questions on Cloudflare Zero Trust, as well as a troubleshooting section to help you solve common issues and errors you may come across.
 

@@ -9,6 +9,8 @@ description: Review common troubleshooting scenarios for Cloudflare Zero Trust.
 
 import { GlossaryTooltip, Render } from "~/components";
 
+<Render file="survey" />
+
 [❮ Back to FAQ](/cloudflare-one/faq/)
 
 ## I tried to register the WARP client with my Zero Trust domain but received the following error messages: `Authentication Expired` and `Registration error. Please try again later`.
@@ -324,17 +326,17 @@ You must ensure the host device is included in the WARP tunnel while excluding t
 
 This issue can occur due to a conflict between browser settings and Windows network configuration.
 
-In Chromium-based browsers like Chrome and Edge, the **Anonymize local IPs exposed by WebRTC** flag (`chrome://flags/#enable-webrtc-hide-local-ips-with-mdns` or `edge://flags/#enable-webrtc-hide-local-ips-with-mdns`)  — when set to `Enabled` or left at `Default` — hides local IP addresses by replacing them with mDNS hostnames. Multicast DNS (mDNS) hostnames rely on multicast traffic to be resolved properly on the local network.
+In Chromium-based browsers like Chrome and Edge, the **Anonymize local IPs exposed by WebRTC** flag (`chrome://flags/#enable-webrtc-hide-local-ips-with-mdns` or `edge://flags/#enable-webrtc-hide-local-ips-with-mdns`) — when set to `Enabled` or left at `Default` — hides local IP addresses by replacing them with mDNS hostnames. Multicast DNS (mDNS) hostnames rely on multicast traffic to be resolved properly on the local network.
 
 The [Internet Group Management Protocol (IGMP)](https://www.cloudflare.com/learning/network-layer/what-is-igmp/) allows devices to join a multicasting group. On Windows, `IGMPLevel` determines whether the system participates in multicast group membership. When `IGMPLevel` is set to `0`, multicast support is disabled.
 
 To resolve this error, review the following options:
 
-| `IGMPLevel`        | **Anonymize local IPs exposed by WebRTC** setting         | Result in Clientless Web Isolation           |
-|--------------------|-----------------------------------------------------------|----------------------------------------------|
-| `0` (disabled)     | **Enabled / Default**                                     | ❌ Blank screen                              |
-| `0` (disabled)     | **Disabled**                                              | ✅ Works - browser will use local IP address |
-| `2` (enabled)      | **Enabled / Default**                                     | ✅ Works - mDNS resolves successfully        |
+| `IGMPLevel`    | **Anonymize local IPs exposed by WebRTC** setting | Result in Clientless Web Isolation           |
+| -------------- | ------------------------------------------------- | -------------------------------------------- |
+| `0` (disabled) | **Enabled / Default**                             | ❌ Blank screen                              |
+| `0` (disabled) | **Disabled**                                      | ✅ Works - browser will use local IP address |
+| `2` (enabled)  | **Enabled / Default**                             | ✅ Works - mDNS resolves successfully        |
 
 ## After putting Google Workspace behind Access, I can’t log in. It keeps redirecting between Access and Google without ever completing authentication.
 

@@ -3,10 +3,11 @@ pcx_content_type: reference
 title: Glossary
 sidebar:
   order: 14
-
 ---
 
-import { Glossary } from "~/components"
+import { Glossary, Render } from "~/components";
+
+<Render file="survey" />
 
 Review definitions for Cloudflare Zero Trust terms.