Merge branch 'production' into dario/wrangler-versions-wrong-links

Author: dario-piotrowicz

public/__redirects

@@ -2318,7 +2318,7 @@
 /changelog-next/* /changelog/:splat 301
 /browser-rendering/quick-actions-rest-api/* /browser-rendering/rest-api/:splat 301
 /*/sitemap.xml /sitemap-index.xml 301
-/access/configuring-identity-providers/* /cloudflare-one/identity/idp-integration/:splat 301
+/access/configuring-identity-providers/* /cloudflare-one/integrations/identity-providers/:splat 301
 /api-security/* /api-shield/:splat 301
 /api-shield/products/* /api-shield/security/:splat 301
 /distributed-web/* /web3/:splat 301
@@ -2352,8 +2352,8 @@
 /logs/get-started/enable-destinations/* /logs/logpush/logpush-job/enable-destinations/:splat 301
 /logs/reference/log-fields/* /logs/logpush/logpush-job/datasets/:splat 301
 /speed/optimization/other/* /speed/optimization/ 301
-/cloudflare-one/connections/connect-devices/* /cloudflare-one/team-and-resources/devices 301
-/cloudflare-one/connections/connect-networks/* /cloudflare-one/networks/connectors/cloudflare-tunnel/ 301
+/cloudflare-one/connections/connect-devices/* /cloudflare-one/team-and-resources/devices/:splat 301
+/cloudflare-one/connections/connect-networks/* /cloudflare-one/networks/connectors/cloudflare-tunnel/:splat 301
 
 # AI Crawl Control
 /ai-audit/* /ai-crawl-control/:splat 301
@@ -2383,6 +2383,11 @@
 /cloudflare-one/policies/data-loss-prevention/configuration-guides/* /cloudflare-one/policies/data-loss-prevention/dlp-policies/common-policies/ 301
 /cloudflare-one/policies/data-loss-prevention/datasets/* /cloudflare-one/policies/data-loss-prevention/detection-entries/:splat 301
 
+# Cloudflare One nav revamp
+/cloudflare-one/identity/one-time-pin/ /cloudflare-one/integrations/identity-providers/one-time-pin/ 301
+/cloudflare-one/identity/idp-integration/* /cloudflare-one/integrations/identity-providers/:splat 301
+
+
 # Learning paths
 
 /learning-paths/modules/get-started/onboarding/* /learning-paths/get-started-free/onboarding/:splat 301

src/assets/images/gateway/gateway-dns-scheduled-policies-ui.gif

@@ -8,7 +8,7 @@ date: 2025-10-14
 
 ![Screenshot of new user experience for managing SSO](~/assets/images/changelog/fundamentals/2025-10-14-sso-configuration-ux.png)
 
-During Birthday Week, we announced that [single sign-on (SSO) is available for free](https://blog.cloudflare.com/enterprise-grade-features-for-all/) to everyone who signs in with a custom email domain and maintains a compatible [identity provider](https://developers.cloudflare.com/cloudflare-one/identity/idp-integration/). SSO minimizes user friction around login and provides the strongest security posture available. At the time, this could only be configured using the API.
+During Birthday Week, we announced that [single sign-on (SSO) is available for free](https://blog.cloudflare.com/enterprise-grade-features-for-all/) to everyone who signs in with a custom email domain and maintains a compatible [identity provider](https://developers.cloudflare.com/cloudflare-one/integrations/identity-providers/). SSO minimizes user friction around login and provides the strongest security posture available. At the time, this could only be configured using the API.
 
 Today, we are launching a new user experience which allows users to manage their SSO configuration from within the Cloudflare dashboard. You can access this by going to **Manage account** > **Members** > **Settings**.
 

src/content/changelog/fundamentals/2025-10-14-sso-self-service-ux.mdx

@@ -0,0 +1,20 @@
+---
+title: "Schedule DNS policies from the UI"
+description: "All users can now create and manage scheduled DNS policies directly from the Cloudflare One dashboard."
+products:
+  - gateway
+date: "2025-10-20"
+---
+
+Admins can now create [scheduled DNS policies](/cloudflare-one/policies/gateway/dns-policies/timed-policies/) directly from the Zero Trust dashboard, without using the API. You can configure policies to be active during specific, recurring times, such as blocking social media during business hours or gaming sites on school nights.
+
+- **Preset Schedules**: Use built-in templates for common scenarios like Business Hours, School Days, Weekends, and more.
+- **Custom Schedules**: Define your own schedule with specific days and up to three non-overlapping time ranges per day.
+- **Timezone Control**: Choose to enforce a schedule in a specific timezone (for example, US Eastern) or based on the local time of each user.
+- **Combined with Duration**: Policies can have both a schedule and a duration. If both are set, the duration's expiration takes precedence.
+
+You can see the flow in the demo GIF:
+
+![Schedule DNS policies demo](src/assets/images/gateway/gateway-dns-scheduled-policies-ui.gif)
+
+This update makes time-based DNS policies accessible to all Gateway customers, removing the technical barrier of the API.

src/content/changelog/gateway/2025-10-20-schedule-dns-policies-from-the-ui.mdx

@@ -79,7 +79,7 @@ Remember — [authentication is different from authorization](https://www.cloud
 
 ### (2) Cloudflare Access integration
 
-You can use Cloudflare Access as a Single Sign-On (SSO) provider to authorize users to your MCP server. Users log in using a [configured identity provider](/cloudflare-one/identity/idp-integration/) or a [one-time PIN](/cloudflare-one/identity/one-time-pin/), and they are only granted access if their identity matches your [Access policies](/cloudflare-one/policies/access/).
+You can use Cloudflare Access as a Single Sign-On (SSO) provider to authorize users to your MCP server. Users log in using a [configured identity provider](/cloudflare-one/integrations/identity-providers/) or a [one-time PIN](/cloudflare-one/integrations/identity-providers/one-time-pin/), and they are only granted access if their identity matches your [Access policies](/cloudflare-one/policies/access/).
 
 To deploy an [example MCP server](https://github.com/cloudflare/ai/tree/main/demos/remote-mcp-cf-access) with Cloudflare Access as the OAuth provider, refer to [Secure MCP servers with Access for SaaS](/cloudflare-one/applications/configure-apps/mcp-servers/saas-mcp/).
 

src/content/docs/agents/model-context-protocol/authorization.mdx

@@ -39,9 +39,9 @@ The Cloudflare APO WordPress plugin does not support multisite WordPress install
 
    <DashButton url="/?to=/:account/:zone/speed/optimization" />
 
-3. Go to **Content Optimization**.
-4. For **Automatic Platform Optimization for WordPress**, select **Purchase**.
-5. Enter your payment information and select **Confirm payment**.
+2. Go to **Content Optimization**.
+3. For **Automatic Platform Optimization for WordPress**, select **Purchase**.
+4. Enter your payment information and select **Confirm payment**.
 
 ## Install and activate the Cloudflare WordPress plugin
 

src/content/docs/automatic-platform-optimization/get-started/activate-cf-wp-plugin.mdx

@@ -1,21 +1,23 @@
 ---
-title: Confirm DNS Records
+title: Confirm DNS records
 pcx_content_type: how-to
 sidebar:
   order: 6
 head:
   - tag: title
     content: Confirm DNS records
-
 ---
 
-Before you change your nameserver, confirm your DNS records are displaying correctly.
+import { DashButton } from "~/components";
+
+Before you change your nameservers, confirm your DNS records are displaying correctly.
+
+1. In the Cloudflare dashboard, go to the DNS **Records** page.
+
+   <DashButton url="/?to=/:account/:zone/dns/records" />
 
-1. Open your Cloudflare dashboard and select your account.
-2. Select your domain from the dropdown.
-3. Select the **DNS** > **Records** tile. DNS management for your domain displays.
-4. To add a record, select **Add record.**
-5. To edit an existing record, select **Edit** for the appropriate record.
-6. After making your changes, select **Save**.
+2. To add a record, select **Add record**.
+3. To edit an existing record, select **Edit** for the appropriate record.
+4. After making your changes, select **Save**.
 
 After you confirm your DNS records, [change your nameservers](/automatic-platform-optimization/get-started/change-nameservers/).

src/content/docs/automatic-platform-optimization/get-started/confirm-dns-records.mdx

@@ -21,7 +21,7 @@ You can check whether or not APO is working by verifying APO headers are present
 - `cf-edge-cache` | `cache, platform=wordpress`
   - The `cf-edge-cache` headers confirms the WordPress plugin is installed and enabled.
 
-In a terminal, use the following cURL. The header `'accept: text/html'` is important
+In a terminal, use the following cURL. The header `'accept: text/html'` is important.
 
 ```sh
 curl -svo /dev/null -A "CF" 'https://example.com/' -H 'accept: text/html' 2>&1 | grep 'cf-cache-status\|cf-edge\|cf-apo-via'
@@ -42,4 +42,4 @@ As always, `cf-cache-status` displays if the asset hit the cache or was consider
 
 ## Verify the APO integration and WordPress integration work
 
-Open your WordPress site and publish a change. When the integration is working, the page is cached with `cf-cache-status: HIT` and `cf-apo-via: tcache`
+Open your WordPress site and publish a change. When the integration is working, the page is cached with `cf-cache-status: HIT` and `cf-apo-via: tcache`.

src/content/docs/automatic-platform-optimization/get-started/verify-apo-works.mdx

@@ -50,7 +50,7 @@ There is no fixed limit on the number of requests per browser session. A single
 
 ## Errors & Troubleshooting
 
-### I see `Cannot read properties of undefined (reading 'fetch')` when using Browser Rendering. How do I fix this?
+### `Cannot read properties of undefined (reading 'fetch')`
 
 This error typically occurs because your Puppeteer launch is not receiving the Browser binding. To resolve: Pass your Browser binding into `puppeteer.launch`.
 
@@ -83,8 +83,19 @@ Keep in mind that `page.evaluate` can only return primitive types like strings,
 
 It may be because you increased the height and width of the viewport. To fix this, increase the value of the `deviceScaleFactor` (default is 1).
 
-### I see `Error processing the request: Unable to create new browser: code: 429: message: Browser time limit exceeded for today`. How do I fix it?
+### `Error processing the request: Unable to create new browser: code: 429: message: Browser time limit exceeded for today`
 
 This error indicates you have hit the daily browser-instance limit on the Workers Free plan. [Free-plan accounts are capped at free plan limit is 10 minutes of browser use a day](/browser-rendering/platform/limits/#workers-free) once you exceed those, further creation attempts return a 429 until the next UTC day.
 
 To resolve: [Upgrade to a Workers Paid plan](/workers/platform/pricing/) which allows for more than 10 minutes of usage a day and has higher [limits](/browser-rendering/platform/limits/#workers-paid). If you recently upgraded but still see this error, try redeploying your Worker to ensure your usage is correctly associated with your new plan.
+
+### `422 Unprocessable Entity`
+
+A `422 Unprocessable Entity` error usually means that Browser Rendering wasn’t able to complete an action because of an issue with the site.
+
+This can happen if:
+- The website consumes too much memory during rendering.
+- The page itself crashed or returned an error before the action completed.
+- The request exceeded one of the [timeout limits](/browser-rendering/reference/timeouts/) for page load, element load, or an action.
+
+Most often, this error is caused by a timeout. You can review the different timers and their limits in the [REST API timeouts reference](/browser-rendering/reference/timeouts/).

src/content/docs/browser-rendering/faq.mdx

@@ -6,15 +6,19 @@ sidebar:
   order: 30
 ---
 
-import { Render, Plan } from "~/components";
+import { Render, Plan, DashButton } from "~/components";
 
 <Plan type="workers-all" />
 
 ## Workers Free
 
 Users on the [Workers Free plan](/workers/platform/pricing/) are limited to **10 minutes of browser rendering usage per day**.
 
-To increase this limit, you will need to [upgrade to a Workers Paid plan](/workers/platform/pricing).
+To increase this limit, go to the **Compute (Workers) > Workers plans** page in the Cloudflare dashboard:
+
+    <DashButton url="/?to=/:account/workers/plans" />
+
+[Learn more about Workers Plans](/workers/platform/pricing).
 
 | Feature                                | Limit           |
 | -------------------------------------- | --------------- |
@@ -59,6 +63,10 @@ While the limits above define the maximum number of concurrent browser sessions
 
 If you recently upgraded to the [Workers Paid plan](/workers/platform/pricing/) but still encounter the 10-minute per day limit, redeploy your Worker to ensure your usage is correctly associated with the new plan.
 
+To upgrade, go to the **Compute (Workers) > Workers plans** page in the Cloudflare dashboard:
+
+    <DashButton url="/?to=/:account/workers/plans" />
+
 <Render
   file="manage-concurrency-faq"
   product="browser-rendering"