Update settings in other tiles

pedrosousa · pedrosousa · commit d17ac10843db · 2025-07-11T17:04:25.000+01:00
diff --git a/src/content/docs/api-shield/management-and-monitoring/developer-portal.mdx b/src/content/docs/api-shield/management-and-monitoring/developer-portal.mdx
@@ -4,10 +4,9 @@ type: overview
 title: Build developer portals
 sidebar:
   order: 5
-
 ---
 
-import { GlossaryTooltip, Tabs, TabItem, Steps } from "~/components"
+import { GlossaryTooltip, Tabs, TabItem, Steps } from "~/components";
 
 Once your <GlossaryTooltip term="API endpoint">endpoints</GlossaryTooltip> are saved, API Shield doubles as an API catalog. API Shield can build an interactive documentation portal with the knowledge it has of your APIs, or you can upload a new OpenAPI schema file to build a documentation portal ad-hoc.
 
@@ -29,23 +28,25 @@ To create a developer portal:
       6. Select **Create pages project** to begin project creation. A new Pages project will be automatically created and your API schema will be automatically uploaded to the project along with other supporting static content.
       7. Select **Deploy site**.
     </Steps>
+
   </TabItem>
   <TabItem label="New dashboard" icon="rocket">
     <Steps>
       1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login), and select your account and domain.
-      2. Go to **Security** > **Settings**
+      2. Go to **Security** > **Settings**.
       3. Filter by **API abuse**.
       4. On **Create a developer portal**, select **Create site**.
-      4. Upload an OpenAPI v3.0 schema file or choose to select an existing schema from API Shield.
+      5. Upload an OpenAPI v3.0 schema file or choose to select an existing schema from API Shield.
           :::note
           If you do not have a schema to upload or to select from a pre-existing schema, export your Endpoint Management schema. For best results, include the learned parameters.
 
           Only <GlossaryTooltip term="API schema">API schemas</GlossaryTooltip> uploaded to Schema validation 2.0 are available when selecting existing schemas.
           :::
-      5. Select **Download project files** to save a local copy of the files that will be uploaded to Cloudflare Pages. Downloading the project files can be helpful if you wish to modify the project in any way and then upload the new version manually to Pages.
-      6. Select **Create pages project** to begin project creation. A new Pages project will be automatically created and your API schema will be automatically uploaded to the project along with other supporting static content.
-      7. Select **Deploy site**.
+      6. Select **Download project files** to save a local copy of the files that will be uploaded to Cloudflare Pages. Downloading the project files can be helpful if you wish to modify the project in any way and then upload the new version manually to Pages.
+      7. Select **Create pages project** to begin project creation. A new Pages project will be automatically created and your API schema will be automatically uploaded to the project along with other supporting static content.
+      8. Select **Deploy site**.
     </Steps>
+
   </TabItem>
 </Tabs>
 
diff --git a/src/content/docs/api-shield/management-and-monitoring/endpoint-labels.mdx b/src/content/docs/api-shield/management-and-monitoring/endpoint-labels.mdx
@@ -109,7 +109,7 @@ Cloudflare will only add authentication labels to endpoints with successful resp
       1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login), and select your account and domain.
       2. Go to **Security** > **Settings**.
       3. Filter by **API abuse**.
-      4. Under **Endpoint labels**, select **Manage label**.
+      4. Under **Endpoint labels**, select **Manage labels**.
       5. Name the label and add an optional label description.
       6. Apply the label to your selected endpoints.
       7. Select **Create label**.
diff --git a/src/content/docs/api-shield/security/jwt-validation/index.mdx b/src/content/docs/api-shield/security/jwt-validation/index.mdx
@@ -36,7 +36,7 @@ A JWT validation configuration consists of creating a token validation configura
       1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login), and select your account and domain.
       2. Go to **Security** > **Settings**.
       3. Filter by **API abuse**.
-      4. On **Token configurations**, select **Configure tokens**.
+      4. On **Token configurations**, select **Configure tokens**. If you already have one or more tokens, select **&lt;N> out of &lt;M> configurations used** instead.
       5. Add a name for your configuration.
       6. Choose where Cloudflare can locate the JWT for this configuration on incoming requests, such as a header or cookie and its name.
       7. Copy and paste your JWT issuer's public key(s) (JWKS).
@@ -87,7 +87,7 @@ To automatically keep your JWKS up to date when your identity provider refreshes
 
 :::note
 
-Token configuration rules will automatically apply to new endpoints added to Endpoint Management if those endpoints also match the rule. 
+Token configuration rules will automatically apply to new endpoints added to Endpoint Management if those endpoints also match the rule.
 :::
 
 ## Special cases
diff --git a/src/content/docs/api-shield/security/schema-validation/index.mdx b/src/content/docs/api-shield/security/schema-validation/index.mdx
@@ -142,7 +142,7 @@ To set up a fallthrough action:
          1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login), and select your account and domain.
          2. Go to **Security** > **Settings**.
          3. Filter by **API abuse**.
-         4. Under **Custom fallthrough rules**, select **Create custom fallthrough rule** to create a custom fallthrough rule with the template.
+         4. Under **Custom fallthrough rules**, select **Create custom fallthrough rule** to create a custom fallthrough rule with the template. If you have already created fallthrough rules, select **&lt;N> fallthrough rules** instead.
          5. Give your rule a descriptive name.
          6. Choose one or more hostnames from the dropdown menu and select your action.
          7. Select **Save as draft** to deploy later, or **Deploy** to deploy now.
@@ -208,13 +208,11 @@ To change the default action:
    <TabItem label="New dashboard" icon="rocket">
       <Steps>
          1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login), and select your account and domain.
-         2. Go to **Security** > **Web assets** > **Schema Validation**.
-         3. Select **Schema Validation**.
-         4. Under the default `Log` action, select **Change**.
-         5. Choose a new action from the dropdown menu.
-         6. Observe the current action and accept the change by selecting **Change default action** in the popup window.
+         2. Go to **Security** > **Settings** and filter by **API abuse**.
+         3. Under **Schema validation** > **Configurations**, select the edit icon next to **Default action**.
+         4. Choose a new action from the dropdown menu.
+         5. Select **Save**.
       </Steps>
-      Alternatively, you can modify the global action via **Security** > **Settings** > **Schema Validation**.
    </TabItem>
 </Tabs>
 
@@ -241,11 +239,10 @@ To change the action on an individual endpoint:
    <TabItem label="New dashboard" icon="rocket">
       <Steps>
          1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login), and select your account and domain.
-         2. Go to **Security** > **Web assets** > **Schema Validation**.
-         3. Select **Schema Validation** and filter the selected endpoint.
-         4. Select the ellipses on the endpoint's row.
-         5. Select **Change action**.
-         6. Choose a new action from the dropdown menu and select **Set action**.
+         2. Go to **Security** > **Web assets** > **Schema validation** tab.
+         3. Search for the endpoint to change.
+         4. Select the three dots on the endpoint's row > **Change action**.
+         5. Choose a new action from the drop-down menu and select **Set action**.
       </Steps>
    </TabItem>
 </Tabs>
@@ -268,10 +265,10 @@ To disable Schema Validation without changing actions:
    <TabItem label="New dashboard" icon="rocket">
       <Steps>
          1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login), and select your account and domain.
-         2. Go to **Security** > **Web assets** > **Schema Validation**.
+         2. Go to **Security** > **Web assets** > **Schema validation**.
          3. Select **Schema settings**.
          4. Filter by **API abuse**.
-         5. Turn **Schema Validation** off.
+         5. Turn **Schema validation** off.
       </Steps>
    </TabItem>
 </Tabs>
@@ -293,10 +290,10 @@ Your per-endpoint configurations will be saved when modifying the setting, so th
    <TabItem label="New dashboard" icon="rocket">
       <Steps>
          1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login), and select your account and domain.
-         2. Go to **Security** > **Web assets** > **Schema Validation**.
+         2. Go to **Security** > **Web assets** > **Schema validation** tab.
          3. Select **Schema settings**.
          4. Filter by **API abuse**.
-         5. View your schemas on **Schema Validation** > **Active schemas**.
+         5. View your schemas on **Schema validation** > **Active schemas**.
       </Steps>
    </TabItem>
 </Tabs>
@@ -320,10 +317,10 @@ To delete currently uploaded or learned schemas:
    <TabItem label="New dashboard" icon="rocket">
       <Steps>
          1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login), and select your account and domain.
-         2. Go to **Security** > **Web assets** > **Schema Validation**.
+         2. Go to **Security** > **Web assets** > **Schema validation** tab.
          3. Select **Schema settings**.
          4. Filter by **API abuse**.
-         5. View your schemas on **Schema Validation** > **Active schemas**.
+         5. View your schemas on **Schema validation** > **Active schemas**.
          6. Select the ellipses to access the menu and download or delete the listed schema.
       </Steps>
    </TabItem>
diff --git a/src/content/docs/bots/additional-configurations/managed-robots-txt.mdx b/src/content/docs/bots/additional-configurations/managed-robots-txt.mdx
@@ -47,24 +47,24 @@ If your website does not have a `robots.txt` file, Cloudflare creates a new file
 
 To implement a `robots.txt` file on your domain:
 
-<Tabs syncKey="dashNewNav"> 
+<Tabs syncKey="dashNewNav">
 	<TabItem label="Old dashboard">
 		<Steps>
 			<Render
 				file="enable-managed-robots-txt"
 				params={{ one: "Bot Fight Mode" }}
 			/>
 		</Steps>
-	</TabItem> 
+	</TabItem>
 	<TabItem label="New dashboard" icon="rocket">
 		<Steps>
 			1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login), and select your account and domain.
 			2. Go to **Security** > **Settings**.
 			3. Filter by **Bot traffic**.
-			4. Go to **Managed robots.txt**. 
-			5. Turn **Managed robots.txt** on.
+			4. Go to **Manage AI bot traffic with robots.txt**.
+			5. Turn **Manage AI bot traffic with robots.txt** on.
 		</Steps>
-	</TabItem> 
+	</TabItem>
 </Tabs>
 
 ## Availability
diff --git a/src/content/docs/bots/get-started/bot-management.mdx b/src/content/docs/bots/get-started/bot-management.mdx
@@ -23,7 +23,7 @@ This Enterprise product provides the most flexibility to customers by:
 
 Bot Management is automatically enabled for Enterprise zones entitled with the add-on.
 
-<Tabs syncKey="dashNewNav"> 
+<Tabs syncKey="dashNewNav">
   <TabItem label="Old dashboard">
       To enable a [Bot Management](https://dash.cloudflare.com/?to=/:account/:zone/security/bots) trial on Enterprise zones without the Bot Management add-on entitled:
     <Steps>
@@ -37,9 +37,9 @@ Bot Management is automatically enabled for Enterprise zones entitled with the a
 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login), and select your account and domain.
 2. Go to **Security** > **Settings**.
 3. Filter by **Bot traffic**.
-4. Go to **Bot Management**. 
-5. Turn **Bot Management** on.
-6. Choose how your domain should respond to various types of traffic by selecting the associated edit icon.   
+4. Go to **Bot management**.
+5. Turn **Bot management** on.
+6. Choose how your domain should respond to various types of traffic by selecting the associated edit icon.
       - For more details on verified bots, refer to [Verified Bots](/bots/concepts/bot/#verified-bots).
       - For more details on supported file types, refer to [Static resource protection](/bots/additional-configurations/static-resources/).
       - For more details on invisible code injection, refer to [JavaScript detections](/bots/additional-configurations/javascript-detections/).
diff --git a/src/content/docs/cloudflare-challenges/challenge-types/challenge-pages/challenge-passage.mdx b/src/content/docs/cloudflare-challenges/challenge-types/challenge-pages/challenge-passage.mdx
@@ -24,7 +24,7 @@ To update the Challenge Passage (and the value of the `cf_clearance` cookie):
 1. Log into the [Cloudflare dashboard](https://dash.cloudflare.com).
 2. Select your account and domain.
 3. Go to **Security** > **Settings**.
-4. For **Challenge Passage**, set a duration.
+4. For **Challenge passage**, set a timeout duration.
 
 ### Limitations
 
diff --git a/src/content/docs/page-shield/get-started.mdx b/src/content/docs/page-shield/get-started.mdx
@@ -27,7 +27,7 @@ If you do not have access to Page Shield in the Cloudflare dashboard, check if y
 
 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account and domain.
 2. Go to **Security** > **Settings** and filter by **Client side abuse**.
-3. Next to **Continuous script monitoring**, set the toggle to **On**.
+3. Turn on **Continuous script monitoring**.
 
 If you do not have access to resource monitoring in the Cloudflare dashboard, check if your user has one of the [necessary roles](/page-shield/reference/roles-and-permissions/).
 
diff --git a/src/content/docs/security/web-assets.mdx b/src/content/docs/security/web-assets.mdx
@@ -43,7 +43,7 @@ Use **Sequences** to discover how users interact with your API, by tracking the
 
 Once you configure [session identifiers](/api-shield/management-and-monitoring/session-identifiers/), the **Sequences** tab will start grouping and highlighting important user journeys (sequences) across your API.
 
-To configure session identifiers, go to **Security** > **Settings** > **All settings** tab and select **Edit** next to **Session identifiers**.
+To configure session identifiers, go to **Security** > **Settings** and select **Configure session identifiers** next to **Session identifiers**.
 
 For more information on how Cloudflare identifies API sequences and how you can configure API sequence rules, refer to the following resources:
 
diff --git a/src/content/docs/waf/detections/firewall-for-ai.mdx b/src/content/docs/waf/detections/firewall-for-ai.mdx
@@ -32,7 +32,7 @@ Firewall for AI is only available in the new [application security dashboard](/s
 
 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account and domain.
 2. Go to **Security** > **Settings** and filter by **Detections**.
-3. Next to **Firewall for AI**, set the toggle to **On**.
+3. Turn on **Firewall for AI**.
 
 </TabItem> <TabItem label="API">
 
diff --git a/src/content/docs/waf/detections/leaked-credentials/get-started.mdx b/src/content/docs/waf/detections/leaked-credentials/get-started.mdx
@@ -117,7 +117,7 @@ To check for leaked credentials in a way that is not covered by the default conf
 
 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account and domain.
 2. Go to **Security** > **Settings** and filter by **Detections**.
-3. Under **Leaked Credential Detection** > **Configurations**, select the edit icon.
+3. Under **Leaked credential detection** > **Configurations**, select the edit icon.
 4. Select **Add custom username and password location**.
 5. In **Username location** and **Password location** (optional), enter expressions for obtaining the username and the password from the HTTP request. For example, you could use the following expressions:
 
diff --git a/src/content/docs/waf/detections/malicious-uploads/get-started.mdx b/src/content/docs/waf/detections/malicious-uploads/get-started.mdx
@@ -26,7 +26,7 @@ WAF content scanning is available to customers on an Enterprise plan with a paid
 
 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com), and select your account and domain.
 2. Go to **Security** > **Settings** and filter by **Detections**.
-3. Next to **Malicious uploads detection**, set the toggle to **On**.
+3. Turn on **Malicious uploads detection**.
 
 </TabItem> <TabItem label="API">
 
diff --git a/src/content/docs/waf/get-started.mdx b/src/content/docs/waf/get-started.mdx
@@ -37,7 +37,7 @@ The [Cloudflare Managed Ruleset](/waf/managed-rules/reference/cloudflare-managed
 
 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com), and select your account and domain.
 2. Go to **Security** > **Settings** and filter by **Web application exploits**.
-3. Next to **Cloudflare managed ruleset**, set the toggle to **On**.
+3. Turn on **Cloudflare managed ruleset**.
 
 </TabItem> </Tabs>
 
@@ -122,7 +122,7 @@ The Cloudflare OWASP Core Ruleset is prone to false positives and offers only ma
 </TabItem> <TabItem label="New dashboard" icon="rocket">
 
 1. Go to your domain > **Security** > **Settings** and filter by **Web application exploits**.
-2. Next to **OWASP Core**, set the toggle to **On**.<br/>
+2. Turn on **OWASP Core**.<br/>
    This will deploy the Cloudflare OWASP Core Ruleset with the default configuration: paranoia level = _PL1_ and score threshold = _Medium - 40 and higher_.
 
 </TabItem> </Tabs>
diff --git a/src/content/docs/waf/managed-rules/deploy-zone-dashboard.mdx b/src/content/docs/waf/managed-rules/deploy-zone-dashboard.mdx
@@ -35,7 +35,7 @@ This operation deploys the managed ruleset for the current zone, creating a new
 
 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com), and select your account and domain.
 2. Go to **Security** > **Settings** and filter by **Detections**.
-3. Next to the managed ruleset you want to deploy, set the toggle to **On**.
+3. Turn on the managed ruleset you want to deploy.
 
 </TabItem> </Tabs>
 
diff --git a/src/content/docs/waf/managed-rules/reference/sensitive-data-detection.mdx b/src/content/docs/waf/managed-rules/reference/sensitive-data-detection.mdx
@@ -48,7 +48,7 @@ To enable Cloudflare Sensitive Data Detection:
 
 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com), and select your account and domain.
 2. Go to **Security** > **Settings** and filter by **Detections**.
-3. Next to **Sensitive data detection**, set the toggle to **On**.
+3. Turn on **Sensitive data detection**.
 
 To adjust the scope of the managed ruleset or turn off specific rules:
 
diff --git a/src/content/docs/waf/tools/browser-integrity-check.mdx b/src/content/docs/waf/tools/browser-integrity-check.mdx
@@ -21,14 +21,14 @@ To disable BIC globally for your zone:
 1. Log into the [Cloudflare dashboard](https://dash.cloudflare.com).
 2. Select your account and zone.
 3. Go to **Security** > **Settings**.
-4. For **Browser Integrity Check**, switch the toggle to **Off**.
+4. Turn off **Browser Integrity Check**.
 
 </TabItem> <TabItem label="New dashboard" icon="rocket">
 
 1. Log into the [Cloudflare dashboard](https://dash.cloudflare.com).
 2. Select your account and zone.
-3. Go to **Security** > **Settings**.
-4. Next to **Browser integrity check**, switch the toggle to **Off**.
+3. Go to **Security** > **Settings** and filter by **DDoS attacks**.
+4. Turn off **Browser integrity check**.
 
 </TabItem> </Tabs>
 
diff --git a/src/content/docs/waf/tools/replace-insecure-js-libraries.mdx b/src/content/docs/waf/tools/replace-insecure-js-libraries.mdx
@@ -40,7 +40,7 @@ The feature is available in all Cloudflare plans, and is turned on by default on
 
 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account and zone.
 2. Go to **Security** > **Settings**.
-3. For **Replace insecure JavaScript libraries**, set the toggle to **On** or **Off**.
+3. Turn **Replace insecure JavaScript libraries** on or off.
 
 </TabItem> <TabItem label="API">
 
diff --git a/src/content/partials/waf/leaked-credentials-detection-enable.mdx b/src/content/partials/waf/leaked-credentials-detection-enable.mdx
@@ -16,7 +16,7 @@ On Free plans, the leaked credentials detection is enabled by default, and no ac
 
 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com), and select your account and domain.
 2. Go to **Security** > **Settings** and filter by **Detections**.
-3. Next to **Leaked Credential Detection**, set the toggle to **On**.
+3. Turn on **Leaked credential detection**.
 
 </TabItem> <TabItem label="API">
 
