preclearance cookies

Author: patriciasantaana

src/content/docs/turnstile/concepts/pre-clearance-support.mdx

@@ -6,46 +6,40 @@ sidebar:
 
 ---
 
-You can integrate Cloudflare challenges on single-page applications (SPAs) by allowing Turnstile to issue a clearance cookie. The clearance level is set upon widget creation or widget modification using the Turnstile API's `clearance_level`. Possible values for the configuration are `no_clearance`, `jschallenge`, `managed`,  or `interactive`. All widgets are set to `no_clearance` by default.
+Pre-clearance in Turnstile allows websites to streamline user experiences by using clearance cookies. These cookies enable visitors to bypass WAF challenges downstream, based on the security clearance level set by the customer. This can be particularly useful for trusted visitors, enhancing usability while maintaining security. 
 
-For Enterprise customers eligible to toggle off domain checks, Cloudflare recommends issuing clearance cookies on widgets where at least one domain is specified.
+You can integrate Cloudflare challenges by allowing Turnstile to issue a pre-clearance cookie. The pre-clearance level is set upon widget creation or widget modification using the Turnstile API's `clearance_level`. Possible values for the configuration are:
+
+- `no_clearance`
+- `jschallenge`
+- `managed`
+- `interactive` 
+
+All widgets are set to `no_clearance` by default.
+
+For Enterprise customers eligible to toggle off domain checks, Cloudflare recommends issuing pre-clearance cookies on widgets where at least one domain is specified.
 
 :::note
 
 Clearance cookies only support zones that are orange-clouded. 
 :::
 
-Refer to the [blog post](https://blog.cloudflare.com/integrating-turnstile-with-the-cloudflare-waf-to-challenge-fetch-requests) for an example of pre-clearance implementation.
-
 ## Pre-clearance level options
 
-- **Interactive**: Interactive Pre-clearance allows a user with a clearance cookie to not be challenged by Interactive, Managed Challenge, or JavaScript Challenge Firewall Rules
-- **Managed**: Managed allows a user with a clearance cookie to not be challenged by Managed Challenge or JavaScript Challenge Firewall Rules
-- **Non-interactive**: Non-interactive allows a user with a clearance cookie to not be challenged by JavaScript Challenge Firewall Rules
+- **Interactive (High)**: Allows a user with a clearance cookie to not be challenged by Interactive, Managed Challenge, or JavaScript Challenge Firewall Rules
+- **Managed (Medium)**: Allows a user with a clearance cookie to not be challenged by Managed Challenge or JavaScript Challenge Firewall Rules
+- **Non-interactive (Low)**: Allows a user with a clearance cookie to not be challenged by JavaScript Challenge Firewall Rules
 
-### Duration
+## Clearance cookie duration
 
 Clearance cookies generated by the Turnstile widget will be valid for the time specified by the zone-level Challenge Passage value. To configure the Challenge Passage setting, refer to the [WAF documentation](/waf/tools/challenge-passage/).
 
-## Enable pre-clearance on a new site
-
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select your account.
-2. Go to **Turnstile** > **Add widget**.
-3. Under **Would you like to opt for pre-clearance for this site?** select **Yes**.
-4. Choose the pre-clearance level from the select box.
-5. Select **Create**.
-
-## Enable pre-clearance on an existing site
-
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select your account.
-2. Go to **Turnstile**.
-3. Go to the existing widget or site and select **Settings**.
-4. Under **Would you like to opt for pre-clearance for this site?** select **Yes**.
-5. Choose the pre-clearance level from the select box.
-6. Select **Update**.
-
 ## Verified bots
 
 If a [verified bot](/bots/concepts/bot/#verified-bots) encounters a page where a Turnstile widget is implemented, the challenge will fail and the verified bot will see a `403` error from the Turnstile endpoint.
 
 However, if a verified bot is excluded from the rule which pre-clearance will grant clearance for, it will pass. Users can create a [WAF custom rule](/waf/custom-rules/) to exclude verified bots.
+
+## Setup
+
+To set up pre-clearance cookies, refer to [Enable pre-clearance cookies](/turnstile/get-started/pre-clearance/). 

src/content/docs/turnstile/get-started/mobile-implementation.mdx

@@ -2,7 +2,7 @@
 title: Mobile implementation
 pcx_content_type: concept
 sidebar:
-  order: 5
+  order: 6
 
 ---
 

src/content/docs/turnstile/get-started/pre-clearance.mdx

@@ -0,0 +1,33 @@
+---
+title: Enable pre-clearance cookies
+pcx_content_type: get-started
+sidebar:
+  order: 3
+  label: Pre-clearance cookies
+
+---
+
+## Prerequisites
+
+To enable pre-clearance, you must ensure that the hostname of the Turnstile widget matches the zone with the WAF rules. During the Turnstile configuration setup in the Cloudflare dashboard, you can see the registered zones. Select the appropriate hostname from this list.
+
+The prerequisite is crucial for pre-clearance to function properly. If set up correctly, visitors who successfully solve Turnstile will receive a cookie with the security clearance level set by the customer. When encountering a WAF challenge on the same zone, they will bypass additional challenges for the configured clearance level and below. 
+
+For more details on managing hostnames, refer to the [Hostname Management documentation](/turnstile/concepts/hostname-management/).
+
+## Enable pre-clearance on a new site
+
+1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select your account.
+2. Go to **Turnstile** > **Add widget**.
+3. Under **Would you like to opt for pre-clearance for this site?** select **Yes**.
+4. Choose the pre-clearance level from the select box.
+5. Select **Create**.
+
+## Enable pre-clearance on an existing site
+
+1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select your account.
+2. Go to **Turnstile**.
+3. Go to the existing widget or site and select **Settings**.
+4. Under **Would you like to opt for pre-clearance for this site?** select **Yes**.
+5. Choose the pre-clearance level from the select box.
+6. Select **Update**.

src/content/docs/turnstile/get-started/supported-browsers.mdx

@@ -3,6 +3,6 @@ pcx_content_type: concept
 title: Supported browsers
 external_link: /waf/reference/cloudflare-challenges/#browser-support
 sidebar:
-  order: 4
+  order: 5
 
 ---

src/content/docs/turnstile/get-started/terraform.mdx

@@ -2,7 +2,7 @@
 pcx_content_type: how-to
 title: Terraform
 sidebar:
-  order: 3
+  order: 4
 ---
 
 :::note[Requirements]