From 380527aee46403ee642d510687c6fef9bffe93a8 Mon Sep 17 00:00:00 2001 From: Kate Tungusova Date: Mon, 26 May 2025 15:18:29 +0100 Subject: [PATCH 1/3] [CF1] CWI step 3 expansion --- .../setup/clientless-browser-isolation.mdx | 65 +++++++++++-------- .../browser-isolation/setup/index.mdx | 2 +- 2 files changed, 40 insertions(+), 27 deletions(-) diff --git a/src/content/docs/cloudflare-one/policies/browser-isolation/setup/clientless-browser-isolation.mdx b/src/content/docs/cloudflare-one/policies/browser-isolation/setup/clientless-browser-isolation.mdx index 637041a5133a32..926f1628d6ac77 100644 --- a/src/content/docs/cloudflare-one/policies/browser-isolation/setup/clientless-browser-isolation.mdx +++ b/src/content/docs/cloudflare-one/policies/browser-isolation/setup/clientless-browser-isolation.mdx @@ -3,10 +3,9 @@ pcx_content_type: concept title: Clientless Web Isolation sidebar: order: 5 - --- -import { GlossaryTooltip, Render } from "~/components" +import { GlossaryTooltip, Render } from "~/components"; Clientless Web Isolation allows users to securely browse high risk or sensitive websites in a remote browser without having to install the Cloudflare WARP client on their device. @@ -14,7 +13,21 @@ Clientless Web Isolation allows users to securely browse high risk or sensitive -3. To configure permissions, select **Manage**. You can add authentication methods and [rules](/cloudflare-one/policies/access/) to control who can access the remote browser. +3. To configure permissions, in **Setting** > **Browser Isolation**> select **Manage** next to Permissions. You can add authentication methods and [rules](/cloudflare-one/policies/access/) to control who can access the remote browser. + +4. Under **Policies** > Access Policies > select **Create new policy**. + +5. Name your policy and define who will have access to your isolated application. Refer to the [Access policy documentation](/cloudflare-one/policies/access/#actions) to construct your policy. + +6. Under **Additional settings**, toggle the **Isolate application** on to enable your application to be served in an isolated browser for users matching your policy. + +7. Select **Save**. + +8. Under **Policies** > Access Policies > select **Select existing policies** and select the policy or policies you created in the previous step > select **Confirm**. + +9. At the bottom of the page, select **Save**. + +Your application will now be served in an isolated browser for users matching your policies. ## Filter DNS queries @@ -121,28 +134,28 @@ If you want to isolate a website without Cloudflare WARP installed, you will nee ```html - - Redirecting website to a remote browser - - - - -

- This website is being redirected to a remote browser. Select - here - if you are not automatically redirected. -

- + + Redirecting website to a remote browser + + + + +

+ This website is being redirected to a remote browser. Select + here + if you are not automatically redirected. +

+ ``` @@ -150,4 +163,4 @@ If you want to isolate a website without Cloudflare WARP installed, you will nee Review troubleshooting guidance related to Clientless Web Isolation. -- [Clientless Web Isolation is loading a blank screen on a Windows device](/cloudflare-one/faq/troubleshooting/#clientless-web-isolation-is-loading-with-a-blank-screen-on-a-windows-device) \ No newline at end of file +- [Clientless Web Isolation is loading a blank screen on a Windows device](/cloudflare-one/faq/troubleshooting/#clientless-web-isolation-is-loading-with-a-blank-screen-on-a-windows-device) diff --git a/src/content/docs/cloudflare-one/policies/browser-isolation/setup/index.mdx b/src/content/docs/cloudflare-one/policies/browser-isolation/setup/index.mdx index 5164b8884d7391..1834b9d9438514 100644 --- a/src/content/docs/cloudflare-one/policies/browser-isolation/setup/index.mdx +++ b/src/content/docs/cloudflare-one/policies/browser-isolation/setup/index.mdx @@ -6,7 +6,7 @@ sidebar: label: Get started --- -Browser Isolation is enabled through Secure Web Gateway HTTP policies. By default, no traffic is isolated until you have added an Isolate policy to your HTTP policies. +Browser Isolation is enabled through [Secure Web Gateway HTTP policies](/cloudflare-one/policies/gateway/http-policies/). By default, no traffic is isolated until you have added an Isolate policy to your HTTP policies. ## 1. Connect devices to Cloudflare From c26cd370ee568346984fb7c52352cf43c57fab8d Mon Sep 17 00:00:00 2001 From: Kate Tungusova Date: Fri, 30 May 2025 16:02:33 +0100 Subject: [PATCH 2/3] final edit --- .../setup/clientless-browser-isolation.mdx | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/src/content/docs/cloudflare-one/policies/browser-isolation/setup/clientless-browser-isolation.mdx b/src/content/docs/cloudflare-one/policies/browser-isolation/setup/clientless-browser-isolation.mdx index 926f1628d6ac77..51cec7fb983fab 100644 --- a/src/content/docs/cloudflare-one/policies/browser-isolation/setup/clientless-browser-isolation.mdx +++ b/src/content/docs/cloudflare-one/policies/browser-isolation/setup/clientless-browser-isolation.mdx @@ -19,13 +19,11 @@ Clientless Web Isolation allows users to securely browse high risk or sensitive 5. Name your policy and define who will have access to your isolated application. Refer to the [Access policy documentation](/cloudflare-one/policies/access/#actions) to construct your policy. -6. Under **Additional settings**, toggle the **Isolate application** on to enable your application to be served in an isolated browser for users matching your policy. +6. Select **Save**. -7. Select **Save**. +7. Under **Policies** > Access Policies > select **Select existing policies** and select the policy or policies you created in the previous step > select **Confirm**. -8. Under **Policies** > Access Policies > select **Select existing policies** and select the policy or policies you created in the previous step > select **Confirm**. - -9. At the bottom of the page, select **Save**. +8. At the bottom of the page, select **Save**. Your application will now be served in an isolated browser for users matching your policies. From 9b0ca1c5def617484bd724f30811046143340785 Mon Sep 17 00:00:00 2001 From: Kate Tungusova <70746074+deadlypants1973@users.noreply.github.com> Date: Wed, 4 Jun 2025 17:51:14 +0100 Subject: [PATCH 3/3] Update src/content/docs/cloudflare-one/policies/browser-isolation/setup/clientless-browser-isolation.mdx --- .../browser-isolation/setup/clientless-browser-isolation.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/cloudflare-one/policies/browser-isolation/setup/clientless-browser-isolation.mdx b/src/content/docs/cloudflare-one/policies/browser-isolation/setup/clientless-browser-isolation.mdx index 51cec7fb983fab..1aa99dee05db47 100644 --- a/src/content/docs/cloudflare-one/policies/browser-isolation/setup/clientless-browser-isolation.mdx +++ b/src/content/docs/cloudflare-one/policies/browser-isolation/setup/clientless-browser-isolation.mdx @@ -13,7 +13,7 @@ Clientless Web Isolation allows users to securely browse high risk or sensitive -3. To configure permissions, in **Setting** > **Browser Isolation**> select **Manage** next to Permissions. You can add authentication methods and [rules](/cloudflare-one/policies/access/) to control who can access the remote browser. +3. To configure permissions, in **Settings** > **Browser Isolation** > select **Manage** next to Permissions. You can add authentication methods and [rules](/cloudflare-one/policies/access/) to control who can access the remote browser. 4. Under **Policies** > Access Policies > select **Create new policy**.