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..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
@@ -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,19 @@ 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 **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**.
+
+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. 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. 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 +132,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 +161,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