diff --git a/src/components/DashButton.astro b/src/components/DashButton.astro index 11aa0472286..6476c56e5fb 100644 --- a/src/components/DashButton.astro +++ b/src/components/DashButton.astro @@ -40,11 +40,8 @@ if (!route) { */ const name = buttonName ?? route.name; -const baseUrl = zeroTrust - ? "https://one.dash.cloudflare.com" - : "https://dash.cloudflare.com"; -let { href } = new URL(route.deeplink, baseUrl); +let { href } = new URL(route.deeplink, "https://dash.cloudflare.com"); --- **Service credentials** page. +Previously, users had to generate this certificate by using the [Cloudflare API](https://developers.cloudflare.com/api/) directly. With this update, you can now create and manage this certificate in the [Cloudflare One dashboard](https://dash.cloudflare.com/one/) from the **Access controls** > **Service credentials** page. ![Navigate to Access controls and then Service credentials to see where you can generate an SSH CA](~/assets/images/changelog/access/SSH-CA-generation.png) diff --git a/src/content/changelog/access/2026-01-08-Access-audit-log-for-DoH-users.mdx b/src/content/changelog/access/2026-01-08-Access-audit-log-for-DoH-users.mdx index 0cf547400cd..969a29c874a 100644 --- a/src/content/changelog/access/2026-01-08-Access-audit-log-for-DoH-users.mdx +++ b/src/content/changelog/access/2026-01-08-Access-audit-log-for-DoH-users.mdx @@ -8,4 +8,4 @@ products: Cloudflare [admin activity logs](/cloudflare-one/insights/logs/) now capture each time a [DNS over HTTP (DoH) user](/cloudflare-one/networks/resolvers-and-proxies/dns/dns-over-https/) is created. -These logs can be viewed from the [Cloudflare One dashboard](https://one.dash.cloudflare.com/), pulled via the [Cloudflare API](/api/), and exported through [Logpush](/cloudflare-one/insights/logs/logpush/). +These logs can be viewed from the [Cloudflare One dashboard](https://dash.cloudflare.com/one/), pulled via the [Cloudflare API](/api/), and exported through [Logpush](/cloudflare-one/insights/logs/logpush/). diff --git a/src/content/changelog/browser-isolation/2025-05-01-browser-isolation-overview-page.mdx b/src/content/changelog/browser-isolation/2025-05-01-browser-isolation-overview-page.mdx index a8d29952014..2380be7c5d5 100644 --- a/src/content/changelog/browser-isolation/2025-05-01-browser-isolation-overview-page.mdx +++ b/src/content/changelog/browser-isolation/2025-05-01-browser-isolation-overview-page.mdx @@ -15,4 +15,4 @@ This update consolidates previously disparate settings, accelerating deployment, ![Browser Isolation Overview](~/assets/images/changelog/browser-isolation/browser-isolation-overview.png) -To access the new overview, log in to your Cloudflare [Zero Trust dashboard](https://one.dash.cloudflare.com/) and find Browser Isolation in the side navigation bar. +To access the new overview, log in to your Cloudflare [Zero Trust dashboard](https://dash.cloudflare.com/one/) and find Browser Isolation in the side navigation bar. diff --git a/src/content/changelog/cloudflare-one-client/2025-08-29-warp-AI-diag-analyzer.mdx b/src/content/changelog/cloudflare-one-client/2025-08-29-warp-AI-diag-analyzer.mdx index 579b26e89af..0bfa539689f 100644 --- a/src/content/changelog/cloudflare-one-client/2025-08-29-warp-AI-diag-analyzer.mdx +++ b/src/content/changelog/cloudflare-one-client/2025-08-29-warp-AI-diag-analyzer.mdx @@ -4,4 +4,4 @@ description: Cloudflare One WARP Diagnostic AI Analyzer date: 2025-08-29 --- -We're excited to share a new AI feature, the [WARP diagnostic analyzer](https://blog.cloudflare.com/AI-troubleshoot-warp-and-network-connectivity-issues/), to help you troubleshoot and resolve WARP connectivity issues faster. This beta feature is now available in the [Zero Trust dashboard](https://one.dash.cloudflare.com/) to all users. The AI analyzer makes it easier for you to identify the root cause of client connectivity issues by parsing [remote captures](/cloudflare-one/insights/dex/remote-captures/#start-a-remote-capture) of [WARP diagnostic logs](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/troubleshooting/diagnostic-logs/#warp-diag-logs). The WARP diagnostic analyzer provides a summary of impact that may be experienced on the device, lists notable events that may contribute to performance issues, and recommended troubleshooting steps and articles to help you resolve these issues. Refer to [WARP diagnostics analyzer (beta)](/cloudflare-one/insights/dex/remote-captures/#diagnostics-analyzer-beta) to learn more about how to maximize using the WARP diagnostic analyzer to troubleshoot the WARP client. +We're excited to share a new AI feature, the [WARP diagnostic analyzer](https://blog.cloudflare.com/AI-troubleshoot-warp-and-network-connectivity-issues/), to help you troubleshoot and resolve WARP connectivity issues faster. This beta feature is now available in the [Zero Trust dashboard](https://dash.cloudflare.com/one/) to all users. The AI analyzer makes it easier for you to identify the root cause of client connectivity issues by parsing [remote captures](/cloudflare-one/insights/dex/remote-captures/#start-a-remote-capture) of [WARP diagnostic logs](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/troubleshooting/diagnostic-logs/#warp-diag-logs). The WARP diagnostic analyzer provides a summary of impact that may be experienced on the device, lists notable events that may contribute to performance issues, and recommended troubleshooting steps and articles to help you resolve these issues. Refer to [WARP diagnostics analyzer (beta)](/cloudflare-one/insights/dex/remote-captures/#diagnostics-analyzer-beta) to learn more about how to maximize using the WARP diagnostic analyzer to troubleshoot the WARP client. diff --git a/src/content/changelog/cloudflare-one/2025-04-30-zero-trust-dashboard-dark-mode.mdx b/src/content/changelog/cloudflare-one/2025-04-30-zero-trust-dashboard-dark-mode.mdx index 33c6c6c4965..06bb64a4972 100644 --- a/src/content/changelog/cloudflare-one/2025-04-30-zero-trust-dashboard-dark-mode.mdx +++ b/src/content/changelog/cloudflare-one/2025-04-30-zero-trust-dashboard-dark-mode.mdx @@ -6,7 +6,7 @@ date: 2025-04-30 import { Tabs, TabItem } from "~/components"; -The [Cloudflare Zero Trust dashboard](https://one.dash.cloudflare.com/) now supports Cloudflare's native dark mode for all accounts and plan types. +The [Cloudflare Zero Trust dashboard](https://dash.cloudflare.com/one/) now supports Cloudflare's native dark mode for all accounts and plan types. Zero Trust Dashboard will automatically accept your user-level preferences for system settings, so if your Dashboard appearance is set to 'system' or 'dark', the Zero Trust dashboard will enter dark mode whenever the rest of your Cloudflare account does. @@ -16,7 +16,7 @@ Zero Trust Dashboard will automatically accept your user-level preferences for s To update your view preference in the Zero Trust dashboard: -1. Log into the [Zero Trust dashboard](https://one.dash.cloudflare.com/). +1. Log into the [Zero Trust dashboard](https://dash.cloudflare.com/one/). 2. Select your user icon. 3. Select **Dark Mode**. diff --git a/src/content/changelog/cloudflare-one/2025-07-09-onboarding-resources.mdx b/src/content/changelog/cloudflare-one/2025-07-09-onboarding-resources.mdx index a6914ae86e8..9af97d31b67 100644 --- a/src/content/changelog/cloudflare-one/2025-07-09-onboarding-resources.mdx +++ b/src/content/changelog/cloudflare-one/2025-07-09-onboarding-resources.mdx @@ -21,4 +21,4 @@ There are eight brand new onboarding guides in total: Each flow walks the user through the steps to configure the essential elements, and provides a “more details” panel with additional contextual information about what the user will accomplish at the end, along with why the steps they take are important. -Try them out now in the [Zero Trust dashboard](https://one.dash.cloudflare.com/?to=/:account/home)! +Try them out now in the [Zero Trust dashboard](https://dash.cloudflare.com/?to=/:account/one/overview)! diff --git a/src/content/changelog/cloudflare-one/2025-08-27-shadow-it-analytics.mdx b/src/content/changelog/cloudflare-one/2025-08-27-shadow-it-analytics.mdx index e9dd30bde3f..a26368436dd 100644 --- a/src/content/changelog/cloudflare-one/2025-08-27-shadow-it-analytics.mdx +++ b/src/content/changelog/cloudflare-one/2025-08-27-shadow-it-analytics.mdx @@ -14,4 +14,4 @@ You can review these metrics against application type, such as Artificial Intell These application statuses can also be used in Gateway HTTP policies, so you can block, isolate, limit uploads and downloads, and more based on the application status. -Both the analytics and policies are accessible in the Cloudflare [Zero Trust dashboard](https://one.dash.cloudflare.com/), empowering organizations with better visibility and control. +Both the analytics and policies are accessible in the Cloudflare [Zero Trust dashboard](https://dash.cloudflare.com/one/), empowering organizations with better visibility and control. diff --git a/src/content/changelog/cloudflare-one/2025-12-17-shadow-it-domain-analytics.mdx b/src/content/changelog/cloudflare-one/2025-12-17-shadow-it-domain-analytics.mdx index de5d350a10f..29c376e3e7e 100644 --- a/src/content/changelog/cloudflare-one/2025-12-17-shadow-it-domain-analytics.mdx +++ b/src/content/changelog/cloudflare-one/2025-12-17-shadow-it-domain-analytics.mdx @@ -14,4 +14,4 @@ With this update, you can review data transfer metrics at the domain level, rath These metrics can be filtered by all available filters on the dashboard, including user, application, or content category. -Both the analytics and policies are accessible in the Cloudflare [Zero Trust dashboard](https://one.dash.cloudflare.com/), empowering organizations with better visibility and control. +Both the analytics and policies are accessible in the Cloudflare [Zero Trust dashboard](https://dash.cloudflare.com/one/), empowering organizations with better visibility and control. diff --git a/src/content/changelog/cloudflare-one/access-analytics-v2.mdx b/src/content/changelog/cloudflare-one/access-analytics-v2.mdx index 636d58bb197..982a8c1d400 100644 --- a/src/content/changelog/cloudflare-one/access-analytics-v2.mdx +++ b/src/content/changelog/cloudflare-one/access-analytics-v2.mdx @@ -19,4 +19,4 @@ A new Access Analytics dashboard is now available to all Cloudflare One customer ![Access Analytics](~/assets/images/changelog/cloudflare-one/accessanalytics.png) -To access the new overview, log in to your Cloudflare [Zero Trust dashboard](https://one.dash.cloudflare.com/) and find Analytics in the side navigation bar. +To access the new overview, log in to your Cloudflare [Zero Trust dashboard](https://dash.cloudflare.com/one/) and find Analytics in the side navigation bar. diff --git a/src/content/changelog/cloudflare-one/cf1-data-security-analytics-v1.mdx b/src/content/changelog/cloudflare-one/cf1-data-security-analytics-v1.mdx index 456b47c7909..01bd891a475 100644 --- a/src/content/changelog/cloudflare-one/cf1-data-security-analytics-v1.mdx +++ b/src/content/changelog/cloudflare-one/cf1-data-security-analytics-v1.mdx @@ -23,4 +23,4 @@ The new dashboard includes: ![Data Security Analytics](~/assets/images/changelog/cloudflare-one/cf1-data-security-analytics-v1.png) -To access the new dashboard, log in to [Cloudflare One](https://one.dash.cloudflare.com/) and go to **Insights** on the sidebar. +To access the new dashboard, log in to [Cloudflare One](https://dash.cloudflare.com/one/) and go to **Insights** on the sidebar. diff --git a/src/content/changelog/cloudflare-one/dashboards-access-report.mdx b/src/content/changelog/cloudflare-one/dashboards-access-report.mdx index bedfae29995..94a7acdcc17 100644 --- a/src/content/changelog/cloudflare-one/dashboards-access-report.mdx +++ b/src/content/changelog/cloudflare-one/dashboards-access-report.mdx @@ -14,4 +14,4 @@ Additionally, a new exportable access report is available, allowing customers to ![Cloudflare One Analytics Dashboards](~/assets/images/changelog/cloudflare-one/access-report.png) -Both features are accessible in the Cloudflare [Zero Trust dashboard](https://one.dash.cloudflare.com/), empowering organizations with better visibility and control. +Both features are accessible in the Cloudflare [Zero Trust dashboard](https://dash.cloudflare.com/one/), empowering organizations with better visibility and control. diff --git a/src/content/changelog/cloudflare-one/gateway-analytics-v2.mdx b/src/content/changelog/cloudflare-one/gateway-analytics-v2.mdx index 5f1981bccc2..c8d029c350d 100644 --- a/src/content/changelog/cloudflare-one/gateway-analytics-v2.mdx +++ b/src/content/changelog/cloudflare-one/gateway-analytics-v2.mdx @@ -17,4 +17,4 @@ You can now visualize and explore: ![Gateway Analytics](~/assets/images/changelog/cloudflare-one/gateway-analytics.png) -To access the new overview, log in to your Cloudflare [Zero Trust dashboard](https://one.dash.cloudflare.com/) and go to Analytics in the side navigation bar. +To access the new overview, log in to your Cloudflare [Zero Trust dashboard](https://dash.cloudflare.com/one/) and go to Analytics in the side navigation bar. diff --git a/src/content/changelog/cloudflare-one/new-applications-71825.mdx b/src/content/changelog/cloudflare-one/new-applications-71825.mdx index 3732caa8114..3622c4aefca 100644 --- a/src/content/changelog/cloudflare-one/new-applications-71825.mdx +++ b/src/content/changelog/cloudflare-one/new-applications-71825.mdx @@ -7,8 +7,8 @@ product: Gateway 42 new applications have been added for Zero Trust support within the Application Library and Gateway policy enforcement, giving you the ability to investigate or apply inline policies to these applications. -33 of the 42 applications are Artificial Intelligence applications. The others are Human Resources (2 applications), Development (2 applications), Productivity (2 applications), Sales & Marketing, Public Cloud, and Security. +33 of the 42 applications are Artificial Intelligence applications. The others are Human Resources (2 applications), Development (2 applications), Productivity (2 applications), Sales & Marketing, Public Cloud, and Security. -To view all available applications, log in to your Cloudflare [Zero Trust dashboard](https://one.dash.cloudflare.com/), navigate to the **App Library** under **My Team**. +To view all available applications, log in to your Cloudflare [Zero Trust dashboard](https://dash.cloudflare.com/one/), navigate to the **App Library** under **My Team**. For more information on creating Gateway policies, see our [Gateway policy documentation](/cloudflare-one/traffic-policies/). diff --git a/src/content/changelog/email-security-cf1/2025-09-23-invalid-submissions.mdx b/src/content/changelog/email-security-cf1/2025-09-23-invalid-submissions.mdx index ecd78ebb27e..3b3484647dd 100644 --- a/src/content/changelog/email-security-cf1/2025-09-23-invalid-submissions.mdx +++ b/src/content/changelog/email-security-cf1/2025-09-23-invalid-submissions.mdx @@ -8,7 +8,7 @@ Email security relies on your submissions to continuously improve our detection To ensure all customer feedback is actionable, we have launched two new features to manage invalid submissions sent to our team and user [submission aliases](/cloudflare-one/email-security/settings/phish-submissions/submission-addresses/): -- **Email Notifications:** We now automatically notify users by email when they provide an invalid submission, educating them on the correct format. To disable notifications, go to **[Settings](https://one.dash.cloudflare.com/?to=/:account/email-security/settings)** > **Invalid submission emails** and turn the feature off. +- **Email Notifications:** We now automatically notify users by email when they provide an invalid submission, educating them on the correct format. To disable notifications, go to **[Settings](https://dash.cloudflare.com/?to=/:account/one/email-security/settings)** > **Invalid submission emails** and turn the feature off. ![EmailSec-Invalid-Submissions-Toggle](~/assets/images/changelog/email-security/EmailSec-Invalid-Submissions-Toggle.png) diff --git a/src/content/changelog/gateway/2026-03-04-gateway-authorization-proxy-open-beta.mdx b/src/content/changelog/gateway/2026-03-04-gateway-authorization-proxy-open-beta.mdx index 514e857b47b..5c4797c52e6 100644 --- a/src/content/changelog/gateway/2026-03-04-gateway-authorization-proxy-open-beta.mdx +++ b/src/content/changelog/gateway/2026-03-04-gateway-authorization-proxy-open-beta.mdx @@ -21,7 +21,7 @@ This is ideal for environments where you cannot deploy a device client, such as ### Get started -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Networks** > **Resolvers & Proxies** > **Proxy endpoints**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Networks** > **Resolvers & Proxies** > **Proxy endpoints**. 2. [Create an authorization proxy endpoint](/cloudflare-one/networks/resolvers-and-proxies/proxy-endpoints/#authorization-endpoint) and configure Access policies. 3. [Create a hosted PAC file](/cloudflare-one/networks/resolvers-and-proxies/proxy-endpoints/#create-a-hosted-pac-file) or write your own. 4. [Configure browsers](/cloudflare-one/networks/resolvers-and-proxies/proxy-endpoints/#3b-configure-browser-to-use-pac-file) to use the PAC file URL. diff --git a/src/content/changelog/tunnel/2026-02-20-tunnel-core-dashboard.mdx b/src/content/changelog/tunnel/2026-02-20-tunnel-core-dashboard.mdx index 03aae7f4939..a2d1f87188f 100644 --- a/src/content/changelog/tunnel/2026-02-20-tunnel-core-dashboard.mdx +++ b/src/content/changelog/tunnel/2026-02-20-tunnel-core-dashboard.mdx @@ -27,7 +27,7 @@ This new experience provides everything you need to manage Tunnels for [public a - Securing origin servers and [public applications](/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/) with CDN, WAF, Load Balancing, and DDoS protection - Connecting [Workers to private services](/workers-vpc/) via Workers VPC -**Cloudflare One Dashboard**: Navigate to [Zero Trust > Networks > Connectors](https://one.dash.cloudflare.com/?to=/:account/networks/connectors) to manage Tunnels for: +**Cloudflare One Dashboard**: Navigate to [Zero Trust > Networks > Connectors](https://dash.cloudflare.com/?to=/:account/one/networks/connectors) to manage Tunnels for: - Securing your public applications with [Zero Trust access policies](/cloudflare-one/access-controls/applications/http-apps/self-hosted-public-app/) - Connecting users to [private applications](/cloudflare-one/access-controls/applications/non-http/self-hosted-private-app/) diff --git a/src/content/changelog/tunnel/2026-03-20-tunnel-replica-overview-and-multi-log-streaming.mdx b/src/content/changelog/tunnel/2026-03-20-tunnel-replica-overview-and-multi-log-streaming.mdx index 2849122ee7c..811abd2e374 100644 --- a/src/content/changelog/tunnel/2026-03-20-tunnel-replica-overview-and-multi-log-streaming.mdx +++ b/src/content/changelog/tunnel/2026-03-20-tunnel-replica-overview-and-multi-log-streaming.mdx @@ -14,6 +14,6 @@ In the Cloudflare One dashboard, the overview page for a specific Cloudflare Tun Previously, you could only stream logs from one replica at a time. With this update: - **Replicas on the tunnel overview** — All active replicas for the selected tunnel now appear on that tunnel's overview page under **Connectors**. Select any replica to stream its logs. -- **Multi-connector log streaming** — Stream logs from multiple replicas simultaneously, making it easier to correlate events across your infrastructure during debugging or incident response. To try it out, log in to [Cloudflare One](https://one.dash.cloudflare.com/) and go to **Networks** > **Connectors** > **Cloudflare Tunnels**. Select **View logs** next to the tunnel you want to monitor. +- **Multi-connector log streaming** — Stream logs from multiple replicas simultaneously, making it easier to correlate events across your infrastructure during debugging or incident response. To try it out, log in to [Cloudflare One](https://dash.cloudflare.com/one/) and go to **Networks** > **Connectors** > **Cloudflare Tunnels**. Select **View logs** next to the tunnel you want to monitor. For more information, refer to [Tunnel log streams](/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/logs/) and [Deploy replicas](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-availability/deploy-replicas/). diff --git a/src/content/dash-routes/core.json b/src/content/dash-routes/core.json index a22af19066f..f1baa84f682 100644 --- a/src/content/dash-routes/core.json +++ b/src/content/dash-routes/core.json @@ -269,7 +269,7 @@ }, { "name": "Zero Trust", - "deeplink": "https://one.dash.cloudflare.com" + "deeplink": "https://dash.cloudflare.com/one/" }, { "name": "Overview", diff --git a/src/content/dash-routes/zero-trust.json b/src/content/dash-routes/zero-trust.json index 6487f696449..1c9d09d554c 100644 --- a/src/content/dash-routes/zero-trust.json +++ b/src/content/dash-routes/zero-trust.json @@ -1,862 +1,862 @@ [ { - "deeplink": "/?to=/:account/access-controls/settings", + "deeplink": "/?to=/:account/one/access-controls/settings", "name": "Access settings" }, { - "deeplink": "/?to=/:account/access-controls/settings/app-launcher", + "deeplink": "/?to=/:account/one/access-controls/settings/app-launcher", "name": "" }, { - "deeplink": "/?to=/:account/access-controls/targets", + "deeplink": "/?to=/:account/one/access-controls/targets", "name": "Targets" }, { - "deeplink": "/?to=/:account/access/ai-controls", + "deeplink": "/?to=/:account/one/access/ai-controls", "name": "AI controls" }, { - "deeplink": "/?to=/:account/access/ai-controls/mcp-server", + "deeplink": "/?to=/:account/one/access/ai-controls/mcp-server", "name": "AI controls" }, { - "deeplink": "/?to=/:account/access/ai-controls/mcp-server-portal", + "deeplink": "/?to=/:account/one/access/ai-controls/mcp-server-portal", "name": "AI controls" }, { - "deeplink": "/?to=/:account/access/apps", + "deeplink": "/?to=/:account/one/access/apps", "name": "Applications" }, { - "deeplink": "/?to=/:account/access/apps/add", + "deeplink": "/?to=/:account/one/access/apps/add", "name": "" }, { - "deeplink": "/?to=/:account/access/apps/bookmark", + "deeplink": "/?to=/:account/one/access/apps/bookmark", "name": "" }, { - "deeplink": "/?to=/:account/access/apps/edit", + "deeplink": "/?to=/:account/one/access/apps/edit", "name": "" }, { - "deeplink": "/?to=/:account/access/apps/infra", + "deeplink": "/?to=/:account/one/access/apps/infra", "name": "" }, { - "deeplink": "/?to=/:account/access/apps/mcp", + "deeplink": "/?to=/:account/one/access/apps/mcp", "name": "" }, { - "deeplink": "/?to=/:account/access/apps/policy-tester", + "deeplink": "/?to=/:account/one/access/apps/policy-tester", "name": "" }, { - "deeplink": "/?to=/:account/access/apps/private-policy-rules", + "deeplink": "/?to=/:account/one/access/apps/private-policy-rules", "name": "" }, { - "deeplink": "/?to=/:account/access/apps/rules", + "deeplink": "/?to=/:account/one/access/apps/rules", "name": "" }, { - "deeplink": "/?to=/:account/access/apps/saas", + "deeplink": "/?to=/:account/one/access/apps/saas", "name": "" }, { - "deeplink": "/?to=/:account/access/apps/self-hosted", + "deeplink": "/?to=/:account/one/access/apps/self-hosted", "name": "" }, { - "deeplink": "/?to=/:account/access/groups", + "deeplink": "/?to=/:account/one/access/groups", "name": "" }, { - "deeplink": "/?to=/:account/access/groups/add", + "deeplink": "/?to=/:account/one/access/groups/add", "name": "" }, { - "deeplink": "/?to=/:account/access/overview", + "deeplink": "/?to=/:account/one/access/overview", "name": "Access" }, { - "deeplink": "/?to=/:account/access/policies", + "deeplink": "/?to=/:account/one/access/policies", "name": "Policies" }, { - "deeplink": "/?to=/:account/access/policies/add", + "deeplink": "/?to=/:account/one/access/policies/add", "name": "Policies" }, { - "deeplink": "/?to=/:account/access/rule-groups", + "deeplink": "/?to=/:account/one/access/rule-groups", "name": "" }, { - "deeplink": "/?to=/:account/access/rule-groups/add", + "deeplink": "/?to=/:account/one/access/rule-groups/add", "name": "" }, { - "deeplink": "/?to=/:account/access/service-auth", + "deeplink": "/?to=/:account/one/access/service-auth", "name": "Service auth" }, { - "deeplink": "/?to=/:account/access/service-auth/mtls", + "deeplink": "/?to=/:account/one/access/service-auth/mtls", "name": "" }, { - "deeplink": "/?to=/:account/access/service-auth/service-tokens", + "deeplink": "/?to=/:account/one/access/service-auth/service-tokens", "name": "" }, { - "deeplink": "/?to=/:account/access/tags", + "deeplink": "/?to=/:account/one/access/tags", "name": "" }, { - "deeplink": "/?to=/:account/access/tags/add", + "deeplink": "/?to=/:account/one/access/tags/add", "name": "" }, { - "deeplink": "/?to=/:account/access/tunnels", + "deeplink": "/?to=/:account/one/access/tunnels", "name": "Tunnels" }, { - "deeplink": "/?to=/:account/ai-playground", + "deeplink": "/?to=/:account/one/ai-playground", "name": "" }, { - "deeplink": "/?to=/:account/analytics/access/viewall", + "deeplink": "/?to=/:account/one/analytics/access/viewall", "name": "" }, { - "deeplink": "/?to=/:account/analytics/categorieslist", + "deeplink": "/?to=/:account/one/analytics/categorieslist", "name": "" }, { - "deeplink": "/?to=/:account/analytics/dashboards", + "deeplink": "/?to=/:account/one/analytics/dashboards", "name": "Dashboards" }, { - "deeplink": "/?to=/:account/analytics/dashboards/access-event", + "deeplink": "/?to=/:account/one/analytics/dashboards/access-event", "name": "Access event analytics" }, { - "deeplink": "/?to=/:account/analytics/dashboards/access-report", + "deeplink": "/?to=/:account/one/analytics/dashboards/access-report", "name": "Application Access report" }, { - "deeplink": "/?to=/:account/analytics/dashboards/ai-security-report", + "deeplink": "/?to=/:account/one/analytics/dashboards/ai-security-report", "name": "AI security report" }, { - "deeplink": "/?to=/:account/analytics/dashboards/data-security", + "deeplink": "/?to=/:account/one/analytics/dashboards/data-security", "name": "Data security analytics" }, { - "deeplink": "/?to=/:account/analytics/dashboards/dns-query", + "deeplink": "/?to=/:account/one/analytics/dashboards/dns-query", "name": "DNS query analytics" }, { - "deeplink": "/?to=/:account/analytics/dashboards/http-request", + "deeplink": "/?to=/:account/one/analytics/dashboards/http-request", "name": "HTTP request analytics" }, { - "deeplink": "/?to=/:account/analytics/dashboards/network-session", + "deeplink": "/?to=/:account/one/analytics/dashboards/network-session", "name": "Network session analytics" }, { - "deeplink": "/?to=/:account/analytics/dashboards/shadow-it-analytics", + "deeplink": "/?to=/:account/one/analytics/dashboards/shadow-it-analytics", "name": "Shadow IT: SaaS analytics" }, { - "deeplink": "/?to=/:account/analytics/dashboards/shadow-it-private-network", + "deeplink": "/?to=/:account/one/analytics/dashboards/shadow-it-private-network", "name": "Shadow IT: Private Network analytics" }, { - "deeplink": "/?to=/:account/analytics/discovery/privatenetwork", + "deeplink": "/?to=/:account/one/analytics/discovery/privatenetwork", "name": "" }, { - "deeplink": "/?to=/:account/analytics/discovery/shadowit", + "deeplink": "/?to=/:account/one/analytics/discovery/shadowit", "name": "" }, { - "deeplink": "/?to=/:account/analytics/domainlist", + "deeplink": "/?to=/:account/one/analytics/domainlist", "name": "" }, { - "deeplink": "/?to=/:account/analytics/overview", + "deeplink": "/?to=/:account/one/analytics/overview", "name": "Analytics" }, { - "deeplink": "/?to=/:account/browser-isolation/overview", + "deeplink": "/?to=/:account/one/browser-isolation/overview", "name": "Browser isolation" }, { - "deeplink": "/?to=/:account/casb/content", + "deeplink": "/?to=/:account/one/casb/content", "name": "Content Findings" }, { - "deeplink": "/?to=/:account/casb/integration", + "deeplink": "/?to=/:account/one/casb/integration", "name": "" }, { - "deeplink": "/?to=/:account/casb/overview", + "deeplink": "/?to=/:account/one/casb/overview", "name": "CASB" }, { - "deeplink": "/?to=/:account/casb/posture", + "deeplink": "/?to=/:account/one/casb/posture", "name": "" }, { - "deeplink": "/?to=/:account/dex", + "deeplink": "/?to=/:account/one/dex", "name": "DEX" }, { - "deeplink": "/?to=/:account/dex/monitoring", + "deeplink": "/?to=/:account/one/dex/monitoring", "name": "Monitoring" }, { - "deeplink": "/?to=/:account/dex/monitoring/devices-by-colo", + "deeplink": "/?to=/:account/one/dex/monitoring/devices-by-colo", "name": "Connectivity Heat Map" }, { - "deeplink": "/?to=/:account/dex/monitoring/devices-by-colo-list", + "deeplink": "/?to=/:account/one/dex/monitoring/devices-by-colo-list", "name": "Connectivity Heat Map" }, { - "deeplink": "/?to=/:account/dex/monitoring/http-tests", + "deeplink": "/?to=/:account/one/dex/monitoring/http-tests", "name": "HTTP Test Details" }, { - "deeplink": "/?to=/:account/dex/monitoring/remote-captures", + "deeplink": "/?to=/:account/one/dex/monitoring/remote-captures", "name": "Monitoring" }, { - "deeplink": "/?to=/:account/dex/monitoring/tests", + "deeplink": "/?to=/:account/one/dex/monitoring/tests", "name": "Monitoring" }, { - "deeplink": "/?to=/:account/dex/monitoring/traceroute-tests", + "deeplink": "/?to=/:account/one/dex/monitoring/traceroute-tests", "name": "Traceroute test details" }, { - "deeplink": "/?to=/:account/dex/remote-captures", + "deeplink": "/?to=/:account/one/dex/remote-captures", "name": "Remote captures" }, { - "deeplink": "/?to=/:account/dex/remote-captures/create", + "deeplink": "/?to=/:account/one/dex/remote-captures/create", "name": "Start a capture" }, { - "deeplink": "/?to=/:account/dex/remote-captures/warp-diagnostic", + "deeplink": "/?to=/:account/one/dex/remote-captures/warp-diagnostic", "name": "Warp Diagnostic" }, { - "deeplink": "/?to=/:account/dex/rules", + "deeplink": "/?to=/:account/one/dex/rules", "name": "Tests using a DEX rule" }, { - "deeplink": "/?to=/:account/dex/rules/create", + "deeplink": "/?to=/:account/one/dex/rules/create", "name": "Create a DEX rule" }, { - "deeplink": "/?to=/:account/dex/tests", + "deeplink": "/?to=/:account/one/dex/tests", "name": "Tests" }, { - "deeplink": "/?to=/:account/dex/tests/add", + "deeplink": "/?to=/:account/one/dex/tests/add", "name": "" }, { - "deeplink": "/?to=/:account/dex/tests/edit", + "deeplink": "/?to=/:account/one/dex/tests/edit", "name": "" }, { - "deeplink": "/?to=/:account/dlp", + "deeplink": "/?to=/:account/one/dlp", "name": "Data loss prevention" }, { - "deeplink": "/?to=/:account/dlp/detection-entries", + "deeplink": "/?to=/:account/one/dlp/detection-entries", "name": "Detection entries" }, { - "deeplink": "/?to=/:account/dlp/detection-entries/dataset", + "deeplink": "/?to=/:account/one/dlp/detection-entries/dataset", "name": "Edit dataset" }, { - "deeplink": "/?to=/:account/dlp/detection-entries/document", + "deeplink": "/?to=/:account/one/dlp/detection-entries/document", "name": "Edit document" }, { - "deeplink": "/?to=/:account/dlp/detection-entries/prompt-topics", + "deeplink": "/?to=/:account/one/dlp/detection-entries/prompt-topics", "name": "Edit prompt topics" }, { - "deeplink": "/?to=/:account/dlp/overview", + "deeplink": "/?to=/:account/one/dlp/overview", "name": "Overview" }, { - "deeplink": "/?to=/:account/dlp/profiles", + "deeplink": "/?to=/:account/one/dlp/profiles", "name": "" }, { - "deeplink": "/?to=/:account/dlp/profiles/create", + "deeplink": "/?to=/:account/one/dlp/profiles/create", "name": "" }, { - "deeplink": "/?to=/:account/email-security", + "deeplink": "/?to=/:account/one/email-security", "name": "Email Security" }, { - "deeplink": "/?to=/:account/email-security/directories", + "deeplink": "/?to=/:account/one/email-security/directories", "name": "Group Details" }, { - "deeplink": "/?to=/:account/email-security/investigation", + "deeplink": "/?to=/:account/one/email-security/investigation", "name": "Email details" }, { - "deeplink": "/?to=/:account/email-security/investigation/retro-scan", + "deeplink": "/?to=/:account/one/email-security/investigation/retro-scan", "name": "Retro scan email details" }, { - "deeplink": "/?to=/:account/email-security/monitoring", + "deeplink": "/?to=/:account/one/email-security/monitoring", "name": "Monitoring" }, { - "deeplink": "/?to=/:account/email-security/outbound-dlp/rules", + "deeplink": "/?to=/:account/one/email-security/outbound-dlp/rules", "name": "Edit policy" }, { - "deeplink": "/?to=/:account/email-security/overview", + "deeplink": "/?to=/:account/one/email-security/overview", "name": "Overview" }, { - "deeplink": "/?to=/:account/email-security/overview/generate-retro-scan", + "deeplink": "/?to=/:account/one/email-security/overview/generate-retro-scan", "name": "Retro Scan wizard" }, { - "deeplink": "/?to=/:account/email-security/overview/retro-scan-report", + "deeplink": "/?to=/:account/one/email-security/overview/retro-scan-report", "name": "Retro scan overview report" }, { - "deeplink": "/?to=/:account/email-security/overview/setup", + "deeplink": "/?to=/:account/one/email-security/overview/setup", "name": "Email Security set up" }, { - "deeplink": "/?to=/:account/email-security/phishguard", + "deeplink": "/?to=/:account/one/email-security/phishguard", "name": "PhishGuard" }, { - "deeplink": "/?to=/:account/email-security/reclassifications", + "deeplink": "/?to=/:account/one/email-security/reclassifications", "name": "Reclassifications" }, { - "deeplink": "/?to=/:account/email-security/settings", + "deeplink": "/?to=/:account/one/email-security/settings", "name": "Settings" }, { - "deeplink": "/?to=/:account/email-security/settings/domains", + "deeplink": "/?to=/:account/one/email-security/settings/domains", "name": "Domains" }, { - "deeplink": "/?to=/:account/email-security/settings/email-policy", + "deeplink": "/?to=/:account/one/email-security/settings/email-policy", "name": "Email policy" }, { - "deeplink": "/?to=/:account/gateway", + "deeplink": "/?to=/:account/one/gateway", "name": "" }, { - "deeplink": "/?to=/:account/gateway/egress-policies", + "deeplink": "/?to=/:account/one/gateway/egress-policies", "name": "Egress policies" }, { - "deeplink": "/?to=/:account/gateway/locations", + "deeplink": "/?to=/:account/one/gateway/locations", "name": "" }, { - "deeplink": "/?to=/:account/gateway/locations/add", + "deeplink": "/?to=/:account/one/gateway/locations/add", "name": "" }, { - "deeplink": "/?to=/:account/gateway/locations/add-non-authed", + "deeplink": "/?to=/:account/one/gateway/locations/add-non-authed", "name": "" }, { - "deeplink": "/?to=/:account/gateway/overview", + "deeplink": "/?to=/:account/one/gateway/overview", "name": "Gateway" }, { - "deeplink": "/?to=/:account/gateway/policies", + "deeplink": "/?to=/:account/one/gateway/policies", "name": "" }, { - "deeplink": "/?to=/:account/gateway/proxy-endpoints", + "deeplink": "/?to=/:account/one/gateway/proxy-endpoints", "name": "" }, { - "deeplink": "/?to=/:account/gateway/proxy-endpoints/add", + "deeplink": "/?to=/:account/one/gateway/proxy-endpoints/add", "name": "" }, { - "deeplink": "/?to=/:account/gateway/resolver-policies", + "deeplink": "/?to=/:account/one/gateway/resolver-policies", "name": "" }, { - "deeplink": "/?to=/:account/gateway/resolver-policies/add", + "deeplink": "/?to=/:account/one/gateway/resolver-policies/add", "name": "" }, { - "deeplink": "/?to=/:account/get-started", + "deeplink": "/?to=/:account/one/get-started", "name": "" }, { - "deeplink": "/?to=/:account/get-started/dns-filtering", + "deeplink": "/?to=/:account/one/get-started/dns-filtering", "name": "" }, { - "deeplink": "/?to=/:account/get-started/dns-filtering-preface", + "deeplink": "/?to=/:account/one/get-started/dns-filtering-preface", "name": "" }, { - "deeplink": "/?to=/:account/get-started/replace-my-vpn", + "deeplink": "/?to=/:account/one/get-started/replace-my-vpn", "name": "" }, { - "deeplink": "/?to=/:account/get-started/replace-my-vpn/device-to-device", + "deeplink": "/?to=/:account/one/get-started/replace-my-vpn/device-to-device", "name": "" }, { - "deeplink": "/?to=/:account/get-started/replace-my-vpn/device-to-network", + "deeplink": "/?to=/:account/one/get-started/replace-my-vpn/device-to-network", "name": "" }, { - "deeplink": "/?to=/:account/get-started/replace-my-vpn/network-to-network", + "deeplink": "/?to=/:account/one/get-started/replace-my-vpn/network-to-network", "name": "" }, { - "deeplink": "/?to=/:account/get-started/secure-private-apps", + "deeplink": "/?to=/:account/one/get-started/secure-private-apps", "name": "" }, { - "deeplink": "/?to=/:account/get-started/secure-private-apps/clientless-rdp", + "deeplink": "/?to=/:account/one/get-started/secure-private-apps/clientless-rdp", "name": "" }, { - "deeplink": "/?to=/:account/get-started/secure-private-apps/clientless-ssh", + "deeplink": "/?to=/:account/one/get-started/secure-private-apps/clientless-ssh", "name": "" }, { - "deeplink": "/?to=/:account/get-started/secure-private-apps/private-web-app", + "deeplink": "/?to=/:account/one/get-started/secure-private-apps/private-web-app", "name": "" }, { - "deeplink": "/?to=/:account/get-started/secure-web-traffic", + "deeplink": "/?to=/:account/one/get-started/secure-web-traffic", "name": "" }, { - "deeplink": "/?to=/:account/get-started/secure-web-traffic-preface", + "deeplink": "/?to=/:account/one/get-started/secure-web-traffic-preface", "name": "" }, { - "deeplink": "/?to=/:account/home", + "deeplink": "/?to=/:account/one/home", "name": "Zero Trust Home" }, { - "deeplink": "/?to=/:account/home/quick-start", + "deeplink": "/?to=/:account/one/home/quick-start", "name": "" }, { - "deeplink": "/?to=/:account/home/recent-searches/cloudy", + "deeplink": "/?to=/:account/one/home/recent-searches/cloudy", "name": "" }, { - "deeplink": "/?to=/:account/home/recent-searches/index", + "deeplink": "/?to=/:account/one/home/recent-searches/index", "name": "" }, { - "deeplink": "/?to=/:account/home/recent-searches/resources", + "deeplink": "/?to=/:account/one/home/recent-searches/resources", "name": "" }, { - "deeplink": "/?to=/:account/insights", + "deeplink": "/?to=/:account/one/insights", "name": "Insights" }, { - "deeplink": "/?to=/:account/insights/dashboards", + "deeplink": "/?to=/:account/one/insights/dashboards", "name": "Dashboards" }, { - "deeplink": "/?to=/:account/insights/dex", + "deeplink": "/?to=/:account/one/insights/dex", "name": "Digital experience" }, { - "deeplink": "/?to=/:account/insights/dex/rules", + "deeplink": "/?to=/:account/one/insights/dex/rules", "name": "Tests using a DEX rule" }, { - "deeplink": "/?to=/:account/insights/dex/tests", + "deeplink": "/?to=/:account/one/insights/dex/tests", "name": "Traceroute test details" }, { - "deeplink": "/?to=/:account/insights/logs", + "deeplink": "/?to=/:account/one/insights/logs", "name": "Logs" }, { - "deeplink": "/?to=/:account/insights/logs/ssh", + "deeplink": "/?to=/:account/one/insights/logs/ssh", "name": "SSH" }, { - "deeplink": "/?to=/:account/insights/magic-networking/*", + "deeplink": "/?to=/:account/one/insights/magic-networking/*", "name": "" }, { - "deeplink": "/?to=/:account/insights/network-visibility/*", + "deeplink": "/?to=/:account/one/insights/network-visibility/*", "name": "" }, { - "deeplink": "/?to=/:account/insights/network-visibility/network-overview", + "deeplink": "/?to=/:account/one/insights/network-visibility/network-overview", "name": "Network visibility" }, { - "deeplink": "/?to=/:account/insights/network-visibility/wan-connector-health", + "deeplink": "/?to=/:account/one/insights/network-visibility/wan-connector-health", "name": "Network visibility" }, { - "deeplink": "/?to=/:account/insights/overview", + "deeplink": "/?to=/:account/one/insights/overview", "name": "Insights" }, { - "deeplink": "/?to=/:account/integrations", + "deeplink": "/?to=/:account/one/integrations", "name": "Integrations" }, { - "deeplink": "/?to=/:account/integrations/cloud-and-saas", + "deeplink": "/?to=/:account/one/integrations/cloud-and-saas", "name": "" }, { - "deeplink": "/?to=/:account/integrations/cloud-and-saas/compute-accounts", + "deeplink": "/?to=/:account/one/integrations/cloud-and-saas/compute-accounts", "name": "Cloud & SaaS" }, { - "deeplink": "/?to=/:account/integrations/cloud-and-saas/integrations", + "deeplink": "/?to=/:account/one/integrations/cloud-and-saas/integrations", "name": "Cloud & SaaS" }, { - "deeplink": "/?to=/:account/integrations/cloud-and-saas/new", + "deeplink": "/?to=/:account/one/integrations/cloud-and-saas/new", "name": "" }, { - "deeplink": "/?to=/:account/integrations/identity-providers", + "deeplink": "/?to=/:account/one/integrations/identity-providers", "name": "Identity providers" }, { - "deeplink": "/?to=/:account/integrations/identity-providers/add", + "deeplink": "/?to=/:account/one/integrations/identity-providers/add", "name": "" }, { - "deeplink": "/?to=/:account/integrations/identity-providers/edit", + "deeplink": "/?to=/:account/one/integrations/identity-providers/edit", "name": "" }, { - "deeplink": "/?to=/:account/integrations/service-providers", + "deeplink": "/?to=/:account/one/integrations/service-providers", "name": "Service providers" }, { - "deeplink": "/?to=/:account/integrations/service-providers/add", + "deeplink": "/?to=/:account/one/integrations/service-providers/add", "name": "" }, { - "deeplink": "/?to=/:account/integrations/service-providers/edit", + "deeplink": "/?to=/:account/one/integrations/service-providers/edit", "name": "" }, { - "deeplink": "/?to=/:account/logs", + "deeplink": "/?to=/:account/one/logs", "name": "Logs" }, { - "deeplink": "/?to=/:account/logs/access", + "deeplink": "/?to=/:account/one/logs/access", "name": "Access" }, { - "deeplink": "/?to=/:account/logs/admin", + "deeplink": "/?to=/:account/one/logs/admin", "name": "Admin" }, { - "deeplink": "/?to=/:account/logs/gateway", + "deeplink": "/?to=/:account/one/logs/gateway", "name": "Gateway" }, { - "deeplink": "/?to=/:account/logs/logpush", + "deeplink": "/?to=/:account/one/logs/logpush", "name": "Logpush" }, { - "deeplink": "/?to=/:account/logs/posture", + "deeplink": "/?to=/:account/one/logs/posture", "name": "Posture" }, { - "deeplink": "/?to=/:account/logs/scim", + "deeplink": "/?to=/:account/one/logs/scim", "name": "SCIM provisioning" }, { - "deeplink": "/?to=/:account/networks/connectors", + "deeplink": "/?to=/:account/one/networks/connectors", "name": "Connectors" }, { - "deeplink": "/?to=/:account/networks/connectors/wan-connectors", + "deeplink": "/?to=/:account/one/networks/connectors/wan-connectors", "name": "Connectors" }, { - "deeplink": "/?to=/:account/networks/overview", + "deeplink": "/?to=/:account/one/networks/overview", "name": "Networks" }, { - "deeplink": "/?to=/:account/networks/resolvers-proxies", + "deeplink": "/?to=/:account/one/networks/resolvers-proxies", "name": "Resolvers & Proxies" }, { - "deeplink": "/?to=/:account/networks/resolvers-proxies/pac-file", + "deeplink": "/?to=/:account/one/networks/resolvers-proxies/pac-file", "name": "Resolvers & Proxies" }, { - "deeplink": "/?to=/:account/networks/routes", + "deeplink": "/?to=/:account/one/networks/routes", "name": "" }, { - "deeplink": "/?to=/:account/networks/routes/add", + "deeplink": "/?to=/:account/one/networks/routes/add", "name": "" }, { - "deeplink": "/?to=/:account/networks/routes/hostname-routes", + "deeplink": "/?to=/:account/one/networks/routes/hostname-routes", "name": "" }, { - "deeplink": "/?to=/:account/networks/routes/vnet", + "deeplink": "/?to=/:account/one/networks/routes/vnet", "name": "" }, { - "deeplink": "/?to=/:account/networks/targets", + "deeplink": "/?to=/:account/one/networks/targets", "name": "Targets" }, { - "deeplink": "/?to=/:account/networks/tunnels", + "deeplink": "/?to=/:account/one/networks/tunnels", "name": "" }, { - "deeplink": "/?to=/:account/networks/tunnels/add", + "deeplink": "/?to=/:account/one/networks/tunnels/add", "name": "" }, { - "deeplink": "/?to=/:account/networks/tunnels/new", + "deeplink": "/?to=/:account/one/networks/tunnels/new", "name": "" }, { - "deeplink": "/?to=/:account/no-permissions", + "deeplink": "/?to=/:account/one/no-permissions", "name": "" }, { - "deeplink": "/?to=/:account/oauth", + "deeplink": "/?to=/:account/one/oauth", "name": "CASB OAuth" }, { - "deeplink": "/?to=/:account/onboarding", + "deeplink": "/?to=/:account/one/onboarding", "name": "" }, { - "deeplink": "/?to=/:account/onboarding/proxy", + "deeplink": "/?to=/:account/one/onboarding/proxy", "name": "" }, { - "deeplink": "/?to=/:account/onboarding/warp", + "deeplink": "/?to=/:account/one/onboarding/warp", "name": "" }, { - "deeplink": "/?to=/:account/overview", + "deeplink": "/?to=/:account/one/overview", "name": "Overview" }, { - "deeplink": "/?to=/:account/recent-searches", + "deeplink": "/?to=/:account/one/recent-searches", "name": "" }, { - "deeplink": "/?to=/:account/remote-browser-isolation/settings", + "deeplink": "/?to=/:account/one/remote-browser-isolation/settings", "name": "Browser isolation settings" }, { - "deeplink": "/?to=/:account/reusable-components", + "deeplink": "/?to=/:account/one/reusable-components", "name": "Reusable components" }, { - "deeplink": "/?to=/:account/reusable-components/posture-checks", + "deeplink": "/?to=/:account/one/reusable-components/posture-checks", "name": "Posture checks" }, { - "deeplink": "/?to=/:account/reusable-components/posture-checks/service-provider", + "deeplink": "/?to=/:account/one/reusable-components/posture-checks/service-provider", "name": "Posture checks" }, { - "deeplink": "/?to=/:account/risk-score", + "deeplink": "/?to=/:account/one/risk-score", "name": "Risk score" }, { - "deeplink": "/?to=/:account/risk-score/behaviors", + "deeplink": "/?to=/:account/one/risk-score/behaviors", "name": "" }, { - "deeplink": "/?to=/:account/risk-score/scoring", + "deeplink": "/?to=/:account/one/risk-score/scoring", "name": "" }, { - "deeplink": "/?to=/:account/settings", + "deeplink": "/?to=/:account/one/settings", "name": "Settings" }, { - "deeplink": "/?to=/:account/settings/account", + "deeplink": "/?to=/:account/one/settings/account", "name": "" }, { - "deeplink": "/?to=/:account/settings/account/payment", + "deeplink": "/?to=/:account/one/settings/account/payment", "name": "" }, { - "deeplink": "/?to=/:account/settings/account/plan", + "deeplink": "/?to=/:account/one/settings/account/plan", "name": "" }, { - "deeplink": "/?to=/:account/settings/authentication", + "deeplink": "/?to=/:account/one/settings/authentication", "name": "" }, { - "deeplink": "/?to=/:account/settings/authentication/app-launcher", + "deeplink": "/?to=/:account/one/settings/authentication/app-launcher", "name": "" }, { - "deeplink": "/?to=/:account/settings/browser", + "deeplink": "/?to=/:account/one/settings/browser", "name": "" }, { - "deeplink": "/?to=/:account/settings/browser/permissions", + "deeplink": "/?to=/:account/one/settings/browser/permissions", "name": "" }, { - "deeplink": "/?to=/:account/settings/custom_pages", + "deeplink": "/?to=/:account/one/settings/custom_pages", "name": "" }, { - "deeplink": "/?to=/:account/settings/custom_pages/block_page", + "deeplink": "/?to=/:account/one/settings/custom_pages/block_page", "name": "" }, { - "deeplink": "/?to=/:account/settings/custom_pages/custom_app_launcher", + "deeplink": "/?to=/:account/one/settings/custom_pages/custom_app_launcher", "name": "" }, { - "deeplink": "/?to=/:account/settings/custom_pages/custom_block", + "deeplink": "/?to=/:account/one/settings/custom_pages/custom_block", "name": "" }, { - "deeplink": "/?to=/:account/settings/custom_pages/custom_login", + "deeplink": "/?to=/:account/one/settings/custom_pages/custom_login", "name": "" }, { - "deeplink": "/?to=/:account/settings/custom_pages/page_templates", + "deeplink": "/?to=/:account/one/settings/custom_pages/page_templates", "name": "" }, { - "deeplink": "/?to=/:account/settings/devices", + "deeplink": "/?to=/:account/one/settings/devices", "name": "" }, { - "deeplink": "/?to=/:account/settings/devices/device-posture", + "deeplink": "/?to=/:account/one/settings/devices/device-posture", "name": "" }, { - "deeplink": "/?to=/:account/settings/devices/edit", + "deeplink": "/?to=/:account/one/settings/devices/edit", "name": "" }, { - "deeplink": "/?to=/:account/settings/devices/profile-settings", + "deeplink": "/?to=/:account/one/settings/devices/profile-settings", "name": "" }, { - "deeplink": "/?to=/:account/settings/network", + "deeplink": "/?to=/:account/one/settings/network", "name": "" }, { - "deeplink": "/?to=/:account/settings/resources", + "deeplink": "/?to=/:account/one/settings/resources", "name": "" }, { - "deeplink": "/?to=/:account/settings/resources/certificates", + "deeplink": "/?to=/:account/one/settings/resources/certificates", "name": "" }, { - "deeplink": "/?to=/:account/settings/saas_integrations", + "deeplink": "/?to=/:account/one/settings/saas_integrations", "name": "" }, { - "deeplink": "/?to=/:account/settings/saas_integrations/new", + "deeplink": "/?to=/:account/one/settings/saas_integrations/new", "name": "" }, { - "deeplink": "/?to=/:account/team", + "deeplink": "/?to=/:account/one/team", "name": "My team" }, { - "deeplink": "/?to=/:account/team-resources", + "deeplink": "/?to=/:account/one/team-resources", "name": "Team & Resources" }, { - "deeplink": "/?to=/:account/team-resources/application-library", + "deeplink": "/?to=/:account/one/team-resources/application-library", "name": "" }, { - "deeplink": "/?to=/:account/team-resources/devices", + "deeplink": "/?to=/:account/one/team-resources/devices", "name": "Traceroute Test Results" }, { - "deeplink": "/?to=/:account/team-resources/devices/device-profiles", + "deeplink": "/?to=/:account/one/team-resources/devices/device-profiles", "name": "Device Profiles" }, { - "deeplink": "/?to=/:account/team-resources/devices/managed-networks", + "deeplink": "/?to=/:account/one/team-resources/devices/managed-networks", "name": "Managed Networks" }, { - "deeplink": "/?to=/:account/team-resources/users", + "deeplink": "/?to=/:account/one/team-resources/users", "name": "" }, { - "deeplink": "/?to=/:account/team-resources/users/risk-score", + "deeplink": "/?to=/:account/one/team-resources/users/risk-score", "name": "Users" }, { - "deeplink": "/?to=/:account/team/application-library", + "deeplink": "/?to=/:account/one/team/application-library", "name": "" }, { - "deeplink": "/?to=/:account/team/devices", + "deeplink": "/?to=/:account/one/team/devices", "name": "Traceroute Test Results" }, { - "deeplink": "/?to=/:account/team/lists", + "deeplink": "/?to=/:account/one/team/lists", "name": "" }, { - "deeplink": "/?to=/:account/team/lists/addCSV", + "deeplink": "/?to=/:account/one/team/lists/addCSV", "name": "" }, { - "deeplink": "/?to=/:account/team/lists/addManual", + "deeplink": "/?to=/:account/one/team/lists/addManual", "name": "" }, { - "deeplink": "/?to=/:account/team/users", + "deeplink": "/?to=/:account/one/team/users", "name": "" }, { - "deeplink": "/?to=/:account/traffic-policies/traffic-settings", + "deeplink": "/?to=/:account/one/traffic-policies/traffic-settings", "name": "Traffic settings" }, { diff --git a/src/content/docs/ai-search/configuration/data-source/website.mdx b/src/content/docs/ai-search/configuration/data-source/website.mdx index f53bc35633b..bc1dc18ea20 100644 --- a/src/content/docs/ai-search/configuration/data-source/website.mdx +++ b/src/content/docs/ai-search/configuration/data-source/website.mdx @@ -103,7 +103,7 @@ Service tokens bypass user authentication, so ensure your Access policies are co -1. In [Cloudflare One](https://one.dash.cloudflare.com/), [create a service token](/cloudflare-one/access-controls/service-credentials/service-tokens/#create-a-service-token). Once the Client ID and Client Secret are generated, save them for the next steps. For example they can look like: +1. In [Cloudflare One](https://dash.cloudflare.com/one/), [create a service token](/cloudflare-one/access-controls/service-credentials/service-tokens/#create-a-service-token). Once the Client ID and Client Secret are generated, save them for the next steps. For example they can look like: ``` CF-Access-Client-Id: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.access diff --git a/src/content/docs/billing/understand/preview-services.mdx b/src/content/docs/billing/understand/preview-services.mdx index 0be6d9d6118..f4fffa590d3 100644 --- a/src/content/docs/billing/understand/preview-services.mdx +++ b/src/content/docs/billing/understand/preview-services.mdx @@ -32,7 +32,7 @@ To enable a preview service, use the **Dashboard link** in the following table. | Waiting Room | [Waiting Room dashboard](https://dash.cloudflare.com/?to=/:account/:zone/traffic/waiting-rooms) | [Waiting Room docs](/waiting-room/) | [Waiting Room community](https://community.cloudflare.com/) | | Web3 | [Web3 dashboard](https://dash.cloudflare.com/?to=/:account/:zone/web3) | [Web3 docs](/web3/) | [Web3 discord](https://discord.cloudflare.com) | | Workers | [Workers dashboard](https://dash.cloudflare.com/?to=/:account/workers) | [Workers docs](/workers/) | [Workers discord](https://discord.com/invite/cloudflaredev) | -| Zero Trust | [Zero Trust dashboard](https://one.dash.cloudflare.com/) | [Zero Trust docs](/cloudflare-one/) | [Zero Trust community](https://community.cloudflare.com/c/security/access/51) | +| Zero Trust | [Zero Trust dashboard](https://dash.cloudflare.com/one/) | [Zero Trust docs](/cloudflare-one/) | [Zero Trust community](https://community.cloudflare.com/c/security/access/51) | ## Recommendations diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/enforce-mtls.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/enforce-mtls.mdx index 6d746ea5b2a..a9d71a7388d 100644 --- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/enforce-mtls.mdx +++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/enforce-mtls.mdx @@ -30,7 +30,7 @@ However, if you want to update the Minimum TLS settings for all wildcard hostnam ## Enable mTLS -Once you have [added a custom hostname](/cloudflare-for-platforms/cloudflare-for-saas/start/getting-started/), you can enable mTLS by using Cloudflare Access. Go to [Cloudflare Zero Trust](https://one.dash.cloudflare.com/) and [add mTLS authentication](/cloudflare-one/access-controls/service-credentials/mutual-tls-authentication/) with a few clicks. +Once you have [added a custom hostname](/cloudflare-for-platforms/cloudflare-for-saas/start/getting-started/), you can enable mTLS by using Cloudflare Access. Go to [Cloudflare Zero Trust](https://dash.cloudflare.com/one/) and [add mTLS authentication](/cloudflare-one/access-controls/service-credentials/mutual-tls-authentication/) with a few clicks. :::note Currently, you cannot add mTLS policies for custom hostnames using [API Shield](/api-shield/security/mtls/). diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/secure-with-access.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/secure-with-access.mdx index 18e2ce54be8..c905f9a0697 100644 --- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/secure-with-access.mdx +++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/secure-with-access.mdx @@ -21,7 +21,7 @@ Cloudflare Access provides visibility and control over who has access to your [c ## Setup -1. At your SaaS provider account, select [Zero Trust](https://one.dash.cloudflare.com). +1. At your SaaS provider account, select [Zero Trust](https://dash.cloudflare.com/one/). 2. Go to **Access** > **Applications**. 3. Select **Add an application** and, for type of application, select **Self-hosted**. 4. Enter a name for your Access application and, in **Session Duration**, choose how often the user's [application token](/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/application-token/) should expire. diff --git a/src/content/docs/cloudflare-network-firewall/how-to/add-policies.mdx b/src/content/docs/cloudflare-network-firewall/how-to/add-policies.mdx index d7ded01b595..24d1f4b4b7a 100644 --- a/src/content/docs/cloudflare-network-firewall/how-to/add-policies.mdx +++ b/src/content/docs/cloudflare-network-firewall/how-to/add-policies.mdx @@ -12,7 +12,7 @@ By default, you can create a maximum of 200 policies. We recommend you create li ## Add a policy -1. In the [Cloudflare One](https://one.dash.cloudflare.com) dashboard, go to **Firewall policies** > **Custom policies**. +1. In the [Cloudflare One](https://dash.cloudflare.com/one/) dashboard, go to **Firewall policies** > **Custom policies**. 2. Select **Add a policy**. 3. Fill out the information for your new policy. All existing policies apply to IPv4. You can use a managed [IP list](https://www.cloudflare.com/en-gb/ips/) when populating the **Value**. 4. When you are done, select **Add new policy**. @@ -27,7 +27,7 @@ To disable an existing policy, from the **Custom policies** tab, set the **Enabl ## Update a policy -1. In the [Cloudflare One](https://one.dash.cloudflare.com) dashboard, go to **Firewall policies** > **Custom policies**. +1. In the [Cloudflare One](https://dash.cloudflare.com/one/) dashboard, go to **Firewall policies** > **Custom policies**. 2. Locate the policy you want to edit and select the three dots > **Edit**. 3. Update the policy with your changes and select **Save**. diff --git a/src/content/docs/cloudflare-one/access-controls/access-settings/session-management.mdx b/src/content/docs/cloudflare-one/access-controls/access-settings/session-management.mdx index 6cbbd1c4b46..d8d303147df 100644 --- a/src/content/docs/cloudflare-one/access-controls/access-settings/session-management.mdx +++ b/src/content/docs/cloudflare-one/access-controls/access-settings/session-management.mdx @@ -45,7 +45,7 @@ The global session duration determines how often Cloudflare Access prompts the u To set the global session duration: -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Access controls** > **Access settings**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Access controls** > **Access settings**. 2. Under **Set your global session duration**, select **Edit**, 3. Select the desired timeout duration from the dropdown menu. 4. Select **Save**. @@ -60,7 +60,7 @@ By default, the policy session duration is equal to the [application session dur To set the policy session duration: -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Access controls** > **Policies**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Access controls** > **Policies**. 2. Choose a policy and select **Configure**. 3. Select a **Session Duration** from the dropdown menu. 4. Save the policy. @@ -73,7 +73,7 @@ The application session duration is the default [policy session duration](#polic To set the application session duration: -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Access controls** > **Applications**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Access controls** > **Applications**. 2. Choose an application and select **Configure**. 3. Select a **Session Duration** from the dropdown menu. 4. Save the application. @@ -139,7 +139,7 @@ Access provides two options for revoking user sessions: per-application and per- To immediately terminate all active sessions for a specific application: -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Access controls** > **Applications**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Access controls** > **Applications**. 2. Locate the application for which you would like to revoke active sessions and select **Configure**. @@ -155,7 +155,7 @@ If you want to permanently revoke a user's access: 1. Disable their account in your identity provider so that they cannot authenticate. -2. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Team & Resources** > **Users**. +2. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Team & Resources** > **Users**. 3. Select the checkbox next to the user you want to revoke. diff --git a/src/content/docs/cloudflare-one/access-controls/ai-controls/mcp-portals.mdx b/src/content/docs/cloudflare-one/access-controls/ai-controls/mcp-portals.mdx index 0c74844e880..54879d9faed 100644 --- a/src/content/docs/cloudflare-one/access-controls/ai-controls/mcp-portals.mdx +++ b/src/content/docs/cloudflare-one/access-controls/ai-controls/mcp-portals.mdx @@ -387,7 +387,7 @@ When an admin adds a new upstream MCP server to a portal, the portal automatical Portal logs allow you to monitor user activity through an MCP server portal. You can view logs on a per-portal or per-server basis. -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Access controls** > **AI controls**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Access controls** > **AI controls**. 2. Find the portal or server that you want to view logs for, then select the three dots > **Edit**. 3. Select **Logs**. diff --git a/src/content/docs/cloudflare-one/access-controls/ai-controls/secure-mcp-servers.mdx b/src/content/docs/cloudflare-one/access-controls/ai-controls/secure-mcp-servers.mdx index cd3df46bb33..29cd505b32a 100644 --- a/src/content/docs/cloudflare-one/access-controls/ai-controls/secure-mcp-servers.mdx +++ b/src/content/docs/cloudflare-one/access-controls/ai-controls/secure-mcp-servers.mdx @@ -102,7 +102,7 @@ The Worker will be deployed to your `*.workers.dev` subdomain at `mcp-access-sel -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Access controls** > **Applications**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Access controls** > **Applications**. 2. Select **Add an application**. 3. Select **Self-hosted**. 4. Enter a name for your application (for example, `MCP server`). @@ -305,7 +305,7 @@ The Worker will be deployed to your `*.workers.dev` subdomain at `mcp-server-cf- -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Access controls** > **Applications**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Access controls** > **Applications**. 2. Select **Add an application**. 3. Select **SaaS**. 4. In **Application**, enter a custom name (for example, `MCP server`) and select the textbox that appears below. diff --git a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/cors.mdx b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/cors.mdx index 3d1f89edddd..a9d2a4d94f4 100644 --- a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/cors.mdx +++ b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/cors.mdx @@ -55,7 +55,7 @@ There are three ways you can resolve this error: You can configure Cloudflare to send OPTIONS requests directly to your origin server. To bypass Access for OPTIONS requests: -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Access controls** > **Applications**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Access controls** > **Applications**. 2. Locate the origin that will be receiving OPTIONS requests and select **Configure**. 3. Go to **Advanced settings** > **Cross-Origin Resource Sharing (CORS) settings**. 4. Turn on **Bypass options requests to origin**. This will remove all existing CORS settings for this application. @@ -68,7 +68,7 @@ You can configure Cloudflare to respond to the OPTIONS request on your behalf. T To configure how Cloudflare responds to preflight requests: -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Access controls** > **Applications**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Access controls** > **Applications**. 2. Locate the origin that will be receiving OPTIONS requests and select **Configure**. @@ -135,7 +135,7 @@ Follow [these instructions](/cloudflare-one/access-controls/service-credentials/ ### 2. Add a Service Auth policy -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Access controls** > **Applications**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Access controls** > **Applications**. 2. Find your `api.mysite.com` application and select **Configure**. diff --git a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/index.mdx b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/index.mdx index bc4e2aa1106..93df38287d8 100644 --- a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/index.mdx +++ b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/index.mdx @@ -84,7 +84,7 @@ Cloudflare Access provides optional security settings that can be added to the b To enable these settings: -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Access controls** > **Applications**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Access controls** > **Applications**. 2. Locate the application you would like to configure and select **Configure**. diff --git a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/validating-json.mdx b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/validating-json.mdx index d6fa92c2882..84fc28fde6a 100644 --- a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/validating-json.mdx +++ b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/validating-json.mdx @@ -101,7 +101,7 @@ Cloudflare Access assigns a unique AUD tag to each application. The `aud` claim To get the AUD tag: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Access controls** > **Applications**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Access controls** > **Applications**. 2. Select **Configure** for your application. 3. From the **Additional settings** tab, copy the **Application Audience (AUD) Tag**. diff --git a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/adobe-sign-saas.mdx b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/adobe-sign-saas.mdx index 6100efc1ff1..c2013ee0e82 100644 --- a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/adobe-sign-saas.mdx +++ b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/adobe-sign-saas.mdx @@ -21,7 +21,7 @@ This guide covers how to configure [Adobe Acrobat Sign](https://helpx.adobe.com/ ## 1. Add a SaaS application to Cloudflare One -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Access controls** > **Applications**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Access controls** > **Applications**. 2. Select **Add an application** > **SaaS**. 3. For **Application**, enter `Adobe Sign` and select the corresponding textbox that appears. 4. For the authentication protocol, select **SAML**. diff --git a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/area-1.mdx b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/area-1.mdx index ee949a3b838..d3e6e8d14c7 100644 --- a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/area-1.mdx +++ b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/area-1.mdx @@ -25,7 +25,7 @@ import { Render } from "~/components"; ## 1. Add Area 1 to Cloudflare One -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Access controls** > **Applications**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Access controls** > **Applications**. 2. Select **Add an application**. diff --git a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/asana-saas.mdx b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/asana-saas.mdx index 39a82fac912..fa343aa81cb 100644 --- a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/asana-saas.mdx +++ b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/asana-saas.mdx @@ -20,7 +20,7 @@ This guide covers how to configure [Asana](https://help.asana.com/hc/en-us/artic ## 1. Add a SaaS application to Cloudflare One -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Access controls** > **Applications**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Access controls** > **Applications**. 2. Select **Add an application** > **SaaS** > **Select**. 3. For **Application**, select _Asana_. 4. For the authentication protocol, select **SAML**. diff --git a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/atlassian-saas.mdx b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/atlassian-saas.mdx index 9266ae118a3..cd1f394d9b1 100644 --- a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/atlassian-saas.mdx +++ b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/atlassian-saas.mdx @@ -22,7 +22,7 @@ This guide covers how to configure [Atlassian Cloud](https://support.atlassian.c ## 1. Add a SaaS application to Cloudflare One -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Access controls** > **Applications**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Access controls** > **Applications**. 2. Select **Add an application** > **SaaS**. 3. For **Application**, select _Atlassian_. 4. For the authentication protocol, select **SAML**. diff --git a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/aws-sso-saas.mdx b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/aws-sso-saas.mdx index 69e817fab38..b437c7b29f3 100644 --- a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/aws-sso-saas.mdx +++ b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/aws-sso-saas.mdx @@ -30,7 +30,7 @@ Next, we will obtain **Identity provider metadata** from Cloudflare One. ## 2. Add a SaaS application to Cloudflare One -1. In a separate tab or window, open [Cloudflare One](https://one.dash.cloudflare.com) and go to **Access controls** > **Applications**. +1. In a separate tab or window, open [Cloudflare One](https://dash.cloudflare.com/one/) and go to **Access controls** > **Applications**. 2. Select **Add an application** > **SaaS**. 3. For **Application**, select _Amazon AWS_. 4. For the authentication protocol, select **SAML**. diff --git a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/braintree-saas.mdx b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/braintree-saas.mdx index 9c28c4c02f2..56bfed3bf1c 100644 --- a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/braintree-saas.mdx +++ b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/braintree-saas.mdx @@ -20,7 +20,7 @@ This guide covers how to configure [Braintree](https://developer.paypal.com/brai ## 1. Add a SaaS application to Cloudflare One -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Access controls** > **Applications**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Access controls** > **Applications**. 2. Select **Add an application** > **SaaS** > **Select**. 3. For **Application**, enter `Braintree` and select the textbox that appears below. 4. For the authentication protocol, select **SAML**. @@ -48,7 +48,7 @@ This guide covers how to configure [Braintree](https://developer.paypal.com/brai ## 3. Finish adding a SaaS application to Cloudflare One -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Access controls** > **Applications**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Access controls** > **Applications**. 2. Select **Braintree** > **Edit** > **Overview**. 3. Replace the temporary values for **Entity ID** and **Assertion Consumer Service URL** with the link provided in the successful SSO configuration email from Braintree support. You will use the same link for both values. 4. Select **Save Application**. diff --git a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/coupa-saas.mdx b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/coupa-saas.mdx index 1f760f297f1..867e966bcd6 100644 --- a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/coupa-saas.mdx +++ b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/coupa-saas.mdx @@ -20,7 +20,7 @@ This guide covers how to configure [Coupa](https://compass.coupa.com/en-us/produ ## 1. Add a SaaS application to Cloudflare One -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Access controls** > **Applications**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Access controls** > **Applications**. 2. Select **Add an application** > **SaaS** > **Select**. 3. For **Application**, enter `Coupa` and select the corresponding textbox that appears. 4. For the authentication protocol, select **SAML**. diff --git a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/digicert-saas.mdx b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/digicert-saas.mdx index 042a92cc5e5..040a6f48815 100644 --- a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/digicert-saas.mdx +++ b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/digicert-saas.mdx @@ -21,7 +21,7 @@ This guide covers how to configure [Digicert](https://docs.digicert.com/en/certc ## 1. Add a SaaS application to Cloudflare One -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Access controls** > **Applications**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Access controls** > **Applications**. 2. Select **Add an application** > **SaaS** > **Select**. 3. For **Application**, enter `Digicert` and select the corresponding textbox that appears. 4. For the authentication protocol, select **SAML**. diff --git a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/docusign-access.mdx b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/docusign-access.mdx index 4280485165b..54ea8fe4970 100644 --- a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/docusign-access.mdx +++ b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/docusign-access.mdx @@ -21,7 +21,7 @@ This guide covers how to configure [Docusign](https://support.docusign.com/s/doc ## 1. Create the Access for SaaS application -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Access controls** > **Applications**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Access controls** > **Applications**. 2. Select **Add an Application**. diff --git a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/dropbox-saas.mdx b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/dropbox-saas.mdx index 3bcc06ea12d..5f021bb8333 100644 --- a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/dropbox-saas.mdx +++ b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/dropbox-saas.mdx @@ -20,7 +20,7 @@ This guide covers how to configure [Dropbox](https://help.dropbox.com/security/s ## 1. Add a SaaS application to Cloudflare One -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Access controls** > **Applications**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Access controls** > **Applications**. 2. Select **Add an application** > **SaaS** > **Select**. 3. For **Application**, select `Dropbox`. 4. For the authentication protocol, select **SAML**. diff --git a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/generic-oidc-saas.mdx b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/generic-oidc-saas.mdx index 8d30c6034b5..49c0e1b4672 100644 --- a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/generic-oidc-saas.mdx +++ b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/generic-oidc-saas.mdx @@ -27,7 +27,7 @@ Some SaaS applications provide the Redirect URL after you [configure the SSO pro ## 2. Add your application to Access -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Access controls** > **Applications**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Access controls** > **Applications**. 2. Select **Add an application**. diff --git a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/generic-saml-saas.mdx b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/generic-saml-saas.mdx index dfd148e05e0..50b1c50741e 100644 --- a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/generic-saml-saas.mdx +++ b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/generic-saml-saas.mdx @@ -28,7 +28,7 @@ Obtain the following URLs from your SaaS application account: ## 2. Add your application to Access -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Access controls** > **Applications**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Access controls** > **Applications**. 2. Select **Add an application**. diff --git a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/github-saas.mdx b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/github-saas.mdx index d3ee3c6e1f6..e55df1c36c2 100644 --- a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/github-saas.mdx +++ b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/github-saas.mdx @@ -21,7 +21,7 @@ This guide covers how to configure [GitHub Enterprise Cloud](https://docs.github ## 1. Add a SaaS application to Cloudflare One -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Access controls** > **Applications**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Access controls** > **Applications**. 2. Select **Add an application** > **SaaS** > **Select**. 3. For **Application**, select _GitHub_. 4. For the authentication protocol, select **SAML**. diff --git a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/google-cloud-saas.mdx b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/google-cloud-saas.mdx index c1146fdf306..2ed296e7000 100644 --- a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/google-cloud-saas.mdx +++ b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/google-cloud-saas.mdx @@ -32,7 +32,7 @@ When configuring Google Cloud with Access, the following limitations apply: ## 1. Add a SaaS application to Cloudflare One -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Access controls** > **Applications**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Access controls** > **Applications**. 2. Select **Add an application** > **SaaS** > **Select**. 3. For **Application**, select _Google Cloud_. 4. For the authentication protocol, select **SAML**. diff --git a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/google-workspace-saas.mdx b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/google-workspace-saas.mdx index c443961bb3a..cc6b5125558 100644 --- a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/google-workspace-saas.mdx +++ b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/google-workspace-saas.mdx @@ -28,7 +28,7 @@ The integration of Access as a single sign-on provider for your Google Workspace ## 1. Create an application in Cloudflare One -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Access controls** > **Applications**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Access controls** > **Applications**. 2. Select **Add an application**. diff --git a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/grafana-cloud-saas-oidc.mdx b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/grafana-cloud-saas-oidc.mdx index ad28a4dedf2..c33fb17830e 100644 --- a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/grafana-cloud-saas-oidc.mdx +++ b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/grafana-cloud-saas-oidc.mdx @@ -20,7 +20,7 @@ This guide covers how to configure [Grafana Cloud](https://grafana.com/docs/graf ## 1. Add a SaaS application to Cloudflare One -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Access controls** > **Applications**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Access controls** > **Applications**. 2. Select **Add an application**. 3. Select **SaaS**. 4. For **Application**, enter `Grafana Cloud` and select the corresponding textbox that appears. diff --git a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/grafana-saas-oidc.mdx b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/grafana-saas-oidc.mdx index 912a388042c..b8d45e53d77 100644 --- a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/grafana-saas-oidc.mdx +++ b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/grafana-saas-oidc.mdx @@ -24,7 +24,7 @@ You can also configure OIDC SSO for Grafana using a [configuration file](https:/ ## 1. Add a SaaS application to Cloudflare One -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Access controls** > **Applications**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Access controls** > **Applications**. 2. Select **Add an application**. 3. Select **SaaS**. 4. For **Application**, select _Grafana_. diff --git a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/greenhouse-saas.mdx b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/greenhouse-saas.mdx index 77af3a39055..69395b2f2b0 100644 --- a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/greenhouse-saas.mdx +++ b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/greenhouse-saas.mdx @@ -20,7 +20,7 @@ This guide covers how to configure [Greenhouse Recruiting](https://support.green ## 1. Add a SaaS application to Cloudflare One -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Access controls** > **Applications**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Access controls** > **Applications**. 2. Select **Add an application** > **SaaS**. 3. For **Application**, enter `Greenhouse` and select the corresponding textbox that appears. 4. For the authentication protocol, select **SAML**. diff --git a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/ironclad-saas.mdx b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/ironclad-saas.mdx index 9b3bf12e39c..dceece76020 100644 --- a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/ironclad-saas.mdx +++ b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/ironclad-saas.mdx @@ -20,7 +20,7 @@ This guide covers how to configure [Ironclad](https://support.ironcladapp.com/hc ## 1. Add a SaaS application to Cloudflare One -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Access controls** > **Applications**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Access controls** > **Applications**. 2. Select **Add an application** > **SaaS**. 3. For **Application**, enter `Ironclad` and select the corresponding textbox that appears. 4. For the authentication protocol, select **SAML**. diff --git a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/jamf-pro-saas.mdx b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/jamf-pro-saas.mdx index feeb899e5eb..bd2d3bc8b95 100644 --- a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/jamf-pro-saas.mdx +++ b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/jamf-pro-saas.mdx @@ -27,7 +27,7 @@ This guide covers how to configure [Jamf Pro](https://learn.jamf.com/en-US/bundl ## 2. Add a SaaS application to Cloudflare One -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Access controls** > **Applications**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Access controls** > **Applications**. 2. Select **Add an application** > **SaaS**. 3. For **Application**, enter `Jamf` or `Jamf Pro` and select the corresponding textbox that appears. 4. For the authentication protocol, select **SAML**. diff --git a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/miro-saas.mdx b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/miro-saas.mdx index e368d5c6b62..262b871a18e 100644 --- a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/miro-saas.mdx +++ b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/miro-saas.mdx @@ -23,7 +23,7 @@ This guide covers how to configure [Miro](https://help.miro.com/hc/articles/3600 ## 1. Add a SaaS application to Cloudflare One -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Access controls** > **Applications**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Access controls** > **Applications**. 2. Select **Add an application** > **SaaS**. 3. For **Application**, enter `Miro` and select the corresponding textbox that appears. 4. For the authentication protocol, select **SAML**. diff --git a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/pagerduty-saml-saas.mdx b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/pagerduty-saml-saas.mdx index 9fe0497f8eb..22e84c90db8 100644 --- a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/pagerduty-saml-saas.mdx +++ b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/pagerduty-saml-saas.mdx @@ -20,7 +20,7 @@ This guide covers how to configure [PagerDuty](https://support.pagerduty.com/doc ## 1. Add a SaaS application to Cloudflare One -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Access controls** > **Applications**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Access controls** > **Applications**. 2. Select **Add an application** > **SaaS**. 3. For **Application**, select _PagerDuty_. 4. For the authentication protocol, select **SAML**. diff --git a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/pingboard-saas.mdx b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/pingboard-saas.mdx index e9ee03ce3c2..511c16ffe5e 100644 --- a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/pingboard-saas.mdx +++ b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/pingboard-saas.mdx @@ -20,7 +20,7 @@ This guide covers how to configure [Pingboard](https://support.pingboard.com/hc/ ## 1. Add a SaaS application to Cloudflare One -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Access controls** > **Applications**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Access controls** > **Applications**. 2. Select **Add an application** > **SaaS** > **Select**. 3. For **Application**, enter `Pingboard` and select the corresponding textbox that appears. 4. For the authentication protocol, select **SAML**. diff --git a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/salesforce-saas-oidc.mdx b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/salesforce-saas-oidc.mdx index 074712dcc88..8e08f87ea50 100644 --- a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/salesforce-saas-oidc.mdx +++ b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/salesforce-saas-oidc.mdx @@ -22,7 +22,7 @@ This guide covers how to configure [Salesforce](https://help.salesforce.com/s/ar ## 1. Add a SaaS application to Cloudflare One -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Access controls** > **Applications**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Access controls** > **Applications**. 2. Select **Add an application** > **SaaS**. 3. For **Application**, select _Salesforce_. 4. For the authentication protocol, select **OIDC**. diff --git a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/salesforce-saas-saml.mdx b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/salesforce-saas-saml.mdx index dc50acad8a9..91ed64c0b36 100644 --- a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/salesforce-saas-saml.mdx +++ b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/salesforce-saas-saml.mdx @@ -23,7 +23,7 @@ This guide covers how to configure [Salesforce](https://help.salesforce.com/s/ar ## 1. Add a SaaS application to Cloudflare One -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Access controls** > **Applications**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Access controls** > **Applications**. 2. Select **Add an application** > **SaaS**. 3. For **Application**, select _Salesforce_. 4. For the authentication protocol, select **SAML**. diff --git a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/servicenow-saas-oidc.mdx b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/servicenow-saas-oidc.mdx index 1c0a7adfe05..25fe4ab4c6f 100644 --- a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/servicenow-saas-oidc.mdx +++ b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/servicenow-saas-oidc.mdx @@ -20,7 +20,7 @@ This guide covers how to configure [ServiceNow](https://docs.servicenow.com/bund ## 1. Add a SaaS application to Cloudflare One -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Access controls** > **Applications**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Access controls** > **Applications**. 2. Select **Add an application** > **SaaS**. 3. For **Application**, enter `ServiceNow` and select the corresponding textbox that appears. 4. For the authentication protocol, select **OIDC**. diff --git a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/servicenow-saas-saml.mdx b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/servicenow-saas-saml.mdx index 766c4ad291a..9d275e44b8d 100644 --- a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/servicenow-saas-saml.mdx +++ b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/servicenow-saas-saml.mdx @@ -21,7 +21,7 @@ This guide covers how to configure [ServiceNow](https://docs.servicenow.com/bund ## 1. Add a SaaS application to Cloudflare One -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Access controls** > **Applications**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Access controls** > **Applications**. 2. Select **Add an application** > **SaaS** > **Select**. 3. For **Application**, enter `ServiceNow` and select the corresponding textbox that appears. 4. For the authentication protocol, select **SAML**. diff --git a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/slack-saas.mdx b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/slack-saas.mdx index cec0561218a..ab3c267efeb 100644 --- a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/slack-saas.mdx +++ b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/slack-saas.mdx @@ -23,7 +23,7 @@ This guide covers how to configure [Slack](https://slack.com/help/articles/20377 ## 1. Add a SaaS application to Cloudflare One -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Access controls** > **Applications**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Access controls** > **Applications**. 2. Select **Add an application** > **SaaS**. 3. For **Application**, select _Slack_. 4. For the authentication protocol, select **SAML**. diff --git a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/smartsheet-saas.mdx b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/smartsheet-saas.mdx index d16b00d85bd..8dccaf1322e 100644 --- a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/smartsheet-saas.mdx +++ b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/smartsheet-saas.mdx @@ -25,7 +25,7 @@ In Smartsheet, SSO is configured for a domain. If you have multiple plans using ## 1. Add a SaaS application to Cloudflare One -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Access controls** > **Applications**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Access controls** > **Applications**. 2. Select **Add an application** > **SaaS** > **Select**. 3. For **Application**, enter `Smartsheet` and select the corresponding textbox that appears. 4. For the authentication protocol, select **SAML**. diff --git a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/sparkpost-saas.mdx b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/sparkpost-saas.mdx index 8456f023060..b28b1328d56 100644 --- a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/sparkpost-saas.mdx +++ b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/sparkpost-saas.mdx @@ -20,7 +20,7 @@ This guide covers how to configure [SparkPost or SparkPost EU](https://support.s ## 1. Add a SaaS application to Cloudflare One -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Access controls** > **Applications**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Access controls** > **Applications**. 2. Select **Add an application** > **SaaS** > **Select**. 3. For **Application**, enter `SparkPost` and select the corresponding textbox that appears. 4. For the authentication protocol, select **SAML**. diff --git a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/tableau-saml-saas.mdx b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/tableau-saml-saas.mdx index d08ea6de149..1127d49c9d0 100644 --- a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/tableau-saml-saas.mdx +++ b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/tableau-saml-saas.mdx @@ -20,7 +20,7 @@ This guide covers how to configure [Tableau Cloud](https://help.tableau.com/curr ## 1. Add a SaaS application to Cloudflare One -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Access controls** > **Applications**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Access controls** > **Applications**. 2. Select **Add an application** > **SaaS**. 3. For **Application**, select _Tableau_. 4. For the authentication protocol, select **SAML**. diff --git a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/workday-saas.mdx b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/workday-saas.mdx index 4abbaa08afc..01de77e275d 100644 --- a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/workday-saas.mdx +++ b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/workday-saas.mdx @@ -20,7 +20,7 @@ This guide covers how to configure [Workday](https://doc.workday.com/admin-guide ## 1. Add a SaaS application to Cloudflare One -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Access controls** > **Applications**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Access controls** > **Applications**. 2. Select **Add an application** > **SaaS** > **Select**. 3. For **Application**, enter `Workday` and select the corresponding textbox that appears. 4. For the authentication protocol, select **SAML**. diff --git a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/zendesk-sso-saas.mdx b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/zendesk-sso-saas.mdx index 405883138b6..ffd02afc373 100644 --- a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/zendesk-sso-saas.mdx +++ b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/zendesk-sso-saas.mdx @@ -22,7 +22,7 @@ This guide covers how to configure [Zendesk](https://support.zendesk.com/hc/en-u 1. Go to your Zendesk administrator dashboard, typically available at `.zendesk.com/admin/security/sso`. -2. In a separate tab or window, open [Cloudflare One](https://one.dash.cloudflare.com), select your account, and go to **Access controls** > **Applications**. +2. In a separate tab or window, open [Cloudflare One](https://dash.cloudflare.com/one/), select your account, and go to **Access controls** > **Applications**. 3. Select **Add an application**, then choose _SaaS_. diff --git a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/zoom-saas.mdx b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/zoom-saas.mdx index c60227a74ba..f5a021f10ee 100644 --- a/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/zoom-saas.mdx +++ b/src/content/docs/cloudflare-one/access-controls/applications/http-apps/saas-apps/zoom-saas.mdx @@ -22,7 +22,7 @@ This guide covers how to configure [Zoom](https://support.zoom.com/hc/en/article ## 1. Add a SaaS application to Cloudflare One -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Access controls** > **Applications**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Access controls** > **Applications**. 2. Select **Add an application** > **SaaS** > **Select**. 3. For **Application**, select _Zoom_. 4. For the authentication protocol, select **SAML**. diff --git a/src/content/docs/cloudflare-one/access-controls/applications/non-http/browser-rendering.mdx b/src/content/docs/cloudflare-one/access-controls/applications/non-http/browser-rendering.mdx index 4c2a82b72cc..74ceeb26c12 100644 --- a/src/content/docs/cloudflare-one/access-controls/applications/non-http/browser-rendering.mdx +++ b/src/content/docs/cloudflare-one/access-controls/applications/non-http/browser-rendering.mdx @@ -28,7 +28,7 @@ Cloudflare can render SSH, VNC, and RDP applications in a browser without the ne To turn on browser rendering for an SSH or VNC application: -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Access controls** > **Applications**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Access controls** > **Applications**. 2. Locate the SSH or VNC application you created when [connecting the server to Cloudflare](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/ssh/). Select **Configure**. 3. In **Browser rendering settings**, set **Browser rendering** to _SSH_ or _VNC_. diff --git a/src/content/docs/cloudflare-one/access-controls/applications/non-http/cloudflared-authentication/automatic-cloudflared-authentication.mdx b/src/content/docs/cloudflare-one/access-controls/applications/non-http/cloudflared-authentication/automatic-cloudflared-authentication.mdx index e01e0c6bc05..0addf4e853f 100644 --- a/src/content/docs/cloudflare-one/access-controls/applications/non-http/cloudflared-authentication/automatic-cloudflared-authentication.mdx +++ b/src/content/docs/cloudflare-one/access-controls/applications/non-http/cloudflared-authentication/automatic-cloudflared-authentication.mdx @@ -18,7 +18,7 @@ Automatic `cloudflared` authentication allows users to skip this login page if t To enable automatic `cloudflared` authentication: -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Access controls** > **Applications**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Access controls** > **Applications**. 2. Locate your application and select **Configure**. 3. Go to **Basic information** > **Browser rendering settings**. 4. Turn on **Allow automatic Cloudflared authentication**. diff --git a/src/content/docs/cloudflare-one/access-controls/applications/non-http/legacy-private-network-app.mdx b/src/content/docs/cloudflare-one/access-controls/applications/non-http/legacy-private-network-app.mdx index 278b0a9563e..824eda613fd 100644 --- a/src/content/docs/cloudflare-one/access-controls/applications/non-http/legacy-private-network-app.mdx +++ b/src/content/docs/cloudflare-one/access-controls/applications/non-http/legacy-private-network-app.mdx @@ -19,7 +19,7 @@ You can configure a **Private Network** application to manage access to specific To create a private network application: -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Access controls** > **Applications** > **Add an application**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Access controls** > **Applications** > **Add an application**. 2. Select **Private Network**. diff --git a/src/content/docs/cloudflare-one/access-controls/applications/non-http/short-lived-certificates-legacy.mdx b/src/content/docs/cloudflare-one/access-controls/applications/non-http/short-lived-certificates-legacy.mdx index 0546c98896b..9ccb308b15d 100644 --- a/src/content/docs/cloudflare-one/access-controls/applications/non-http/short-lived-certificates-legacy.mdx +++ b/src/content/docs/cloudflare-one/access-controls/applications/non-http/short-lived-certificates-legacy.mdx @@ -44,7 +44,7 @@ Cloudflare Access will take the identity from a token and, using short-lived cer ## 3. Generate a short-lived certificate public key -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Access controls** > **Service credentials** > **SSH**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Access controls** > **Service credentials** > **SSH**. 2. Select **Add a certificate**. diff --git a/src/content/docs/cloudflare-one/access-controls/policies/external-evaluation.mdx b/src/content/docs/cloudflare-one/access-controls/policies/external-evaluation.mdx index 6f3798376ac..31c25dfc92d 100644 --- a/src/content/docs/cloudflare-one/access-controls/policies/external-evaluation.mdx +++ b/src/content/docs/cloudflare-one/access-controls/policies/external-evaluation.mdx @@ -120,7 +120,7 @@ Other key formats (such as DSA) are not supported at this time. ### 4. Create an External Evaluation rule -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Access controls** > **Policies**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Access controls** > **Policies**. 2. Edit an existing policy or select **Add a policy**. diff --git a/src/content/docs/cloudflare-one/access-controls/policies/require-purpose-justification.mdx b/src/content/docs/cloudflare-one/access-controls/policies/require-purpose-justification.mdx index 1819430a232..37f45fd8b45 100644 --- a/src/content/docs/cloudflare-one/access-controls/policies/require-purpose-justification.mdx +++ b/src/content/docs/cloudflare-one/access-controls/policies/require-purpose-justification.mdx @@ -18,7 +18,7 @@ The purpose justification screen will show for any new sessions of an applicatio Configuring a purpose justification screen is done as part of configuring an Access policy. -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Access controls** > **Applications**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Access controls** > **Applications**. 2. Choose an application and select **Configure**. 3. Go to **Policies**. 4. Choose an **Allow** policy and select **Configure**. diff --git a/src/content/docs/cloudflare-one/access-controls/policies/temporary-auth.mdx b/src/content/docs/cloudflare-one/access-controls/policies/temporary-auth.mdx index efd3eb1bad8..0c60ec8c3d7 100644 --- a/src/content/docs/cloudflare-one/access-controls/policies/temporary-auth.mdx +++ b/src/content/docs/cloudflare-one/access-controls/policies/temporary-auth.mdx @@ -14,7 +14,7 @@ With Cloudflare Access, you can require that users obtain approval before they c ## Set up temporary authentication -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Access controls** > **Applications**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Access controls** > **Applications**. 2. Choose a **Self-hosted** or **SaaS** application and select **Configure**. 3. Choose an **Allow** policy and select **Configure**. 4. Under **Additional settings**, turn on [**Purpose justification**](/cloudflare-one/access-controls/policies/require-purpose-justification/). diff --git a/src/content/docs/cloudflare-one/access-controls/service-credentials/service-tokens.mdx b/src/content/docs/cloudflare-one/access-controls/service-credentials/service-tokens.mdx index 1a1e6371c18..a488a95ca8a 100644 --- a/src/content/docs/cloudflare-one/access-controls/service-credentials/service-tokens.mdx +++ b/src/content/docs/cloudflare-one/access-controls/service-credentials/service-tokens.mdx @@ -104,7 +104,7 @@ Service tokens expire according to the token duration you selected when you crea To renew the service token: -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Access controls** > **Service credentials** > **Service Tokens**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Access controls** > **Service credentials** > **Service Tokens**. 2. Locate the token you want to renew. 3. To extend the token's lifetime by one year, select **Refresh**. 4. To extend the token's lifetime by more than a year: @@ -116,7 +116,7 @@ To renew the service token: If you need to revoke access before the token expires, simply delete the token. -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Access controls** > **Service credentials** > **Service Tokens**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Access controls** > **Service credentials** > **Service Tokens**. 2. **Delete** the token you need to revoke. Services that rely on a deleted service token can no longer reach your application. diff --git a/src/content/docs/cloudflare-one/api-terraform.mdx b/src/content/docs/cloudflare-one/api-terraform.mdx index 941275a8ff6..7b1aa7ac7e3 100644 --- a/src/content/docs/cloudflare-one/api-terraform.mdx +++ b/src/content/docs/cloudflare-one/api-terraform.mdx @@ -25,7 +25,7 @@ Super Administrators can lock all settings as read-only in the Cloudflare One da To enable read-only mode: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Settings** > **Admin controls**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Settings** > **Admin controls**. 2. Enable **Set dashboard to read-only**. All users, regardless of [user permissions](/cloudflare-one/roles-permissions/), will be prevented from making configuration changes through the UI. diff --git a/src/content/docs/cloudflare-one/cloud-and-saas-findings/manage-findings.mdx b/src/content/docs/cloudflare-one/cloud-and-saas-findings/manage-findings.mdx index badb208bcb3..5db153bb7e9 100644 --- a/src/content/docs/cloudflare-one/cloud-and-saas-findings/manage-findings.mdx +++ b/src/content/docs/cloudflare-one/cloud-and-saas-findings/manage-findings.mdx @@ -28,7 +28,7 @@ Posture findings include misconfigurations, unauthorized user activity, and othe To view details about the posture findings that CASB found: -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Cloud & SaaS findings** > **Posture Findings**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Cloud & SaaS findings** > **Posture Findings**. 2. Choose **SaaS** or **Cloud**. 3. To view details about a finding, select the finding's name @@ -51,7 +51,7 @@ Cloudflare CASB labels each finding with one of the following severity levels: You can change the severity level for a finding at any time in case the default assignment does not suit your environment: -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Cloud & SaaS findings** > **Posture Findings**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Cloud & SaaS findings** > **Posture Findings**. 2. Locate the finding you want to modify and select **Manage**. 3. In the severity level drop-down menu, choose your desired setting (_Critical_, _High_, _Medium_, or _Low_). @@ -63,7 +63,7 @@ Content findings include instances of potential data exposure as identified by [ To view details about the content findings that CASB found: -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Cloud & SaaS findings** > **Content Findings**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Cloud & SaaS findings** > **Content Findings**. 2. Choose **SaaS** or **Cloud**. 3. To view details about a finding, select the finding's name. @@ -77,7 +77,7 @@ File findings for some integrations (such as [Microsoft 365](/cloudflare-one/int -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Cloud & SaaS findings** > **Posture Findings**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Cloud & SaaS findings** > **Posture Findings**. 2. Choose **SaaS** or **Cloud**. 3. Locate the individual finding, then select **Manage**. 4. In **Active Instances**, select the file name. @@ -87,7 +87,7 @@ File findings for some integrations (such as [Microsoft 365](/cloudflare-one/int -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Cloud & SaaS findings** > **Content Findings**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Cloud & SaaS findings** > **Content Findings**. 2. Choose **SaaS** or **Cloud**. 3. Select the file name of the detected asset. 4. In **Sharing details**, select the linked file instance. @@ -103,7 +103,7 @@ After reviewing your findings, you may decide that certain posture findings are ### Ignore a finding -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Cloud & SaaS findings** > **Posture Findings**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Cloud & SaaS findings** > **Posture Findings**. 2. Locate the active finding you want to hide. 3. In the three-dot menu, select **Move to ignore**. @@ -111,7 +111,7 @@ The finding's status will change from **Active** to **Ignored**. CASB will conti ### Hide an instance of a finding -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Cloud & SaaS findings** > **Posture Findings**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Cloud & SaaS findings** > **Posture Findings**. 2. Choose the active finding you want to hide, then select **Manage**. 3. In **Active**, find the instance you want to hide. 4. In the three-dot menu, select **Move to hidden**. @@ -124,7 +124,7 @@ After you configure one or more [CASB webhooks](/cloudflare-one/integrations/clo CASB webhooks currently support posture finding instances only. -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Cloud & SaaS findings** > **Posture Findings**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Cloud & SaaS findings** > **Posture Findings**. 2. Choose **SaaS** or **Cloud**. 3. Choose the finding you want to review, then select **Manage**. 4. In **Active Instances**, select an instance. @@ -144,7 +144,7 @@ In addition to detecting and surfacing misconfigurations or issues with SaaS and Before you can remediate findings, [add a new integration](/cloudflare-one/integrations/cloud-and-saas/) and choose _Read-Write mode_ during setup. Alternatively, you can update an existing integration: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Cloud & SaaS findings** > **Integrations**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Cloud & SaaS findings** > **Integrations**. 2. Choose your integration, then select **Configure**. 3. In **Integration permissions**, choose _Read-Write mode_. 4. Select **Update integration**. CASB will redirect you to your Microsoft 365 configuration. @@ -156,7 +156,7 @@ CASB can now remediate supported findings directly. To remediate a supported finding: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Cloud & SaaS findings** > **Posture Findings**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Cloud & SaaS findings** > **Posture Findings**. 2. Choose a supported finding type, then select **Manage**. 3. In **Active Instances**, select an instance. 4. In **Remediation details**, choose a remediation action to take. @@ -201,7 +201,7 @@ Ensure that you have [enabled HTTP filtering](/cloudflare-one/traffic-policies/g To create a Gateway policy directly from a CASB finding: -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Cloud & SaaS findings** > **Posture Findings** or **Cloud & SaaS findings** > **Content Findings**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Cloud & SaaS findings** > **Posture Findings** or **Cloud & SaaS findings** > **Content Findings**. 2. Choose **SaaS** or **Cloud**. 3. Choose the finding you want to modify, then select **Manage**. 4. Find the instance you want to block and select its three-dot menu. diff --git a/src/content/docs/cloudflare-one/cloud-and-saas-findings/troubleshoot-casb.mdx b/src/content/docs/cloudflare-one/cloud-and-saas-findings/troubleshoot-casb.mdx index d77ec045a80..1d2e4d799ff 100644 --- a/src/content/docs/cloudflare-one/cloud-and-saas-findings/troubleshoot-casb.mdx +++ b/src/content/docs/cloudflare-one/cloud-and-saas-findings/troubleshoot-casb.mdx @@ -48,7 +48,7 @@ CASB integrations do not provide real-time updates. Scans are performed periodic To trigger a new scan: -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Cloud & SaaS findings** > **Integrations**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Cloud & SaaS findings** > **Integrations**. 2. Find your integration and select **Configure**. 3. Turn off **Scan for findings**. 4. After a few minutes, turn on **Scan for findings** again. diff --git a/src/content/docs/cloudflare-one/email-security/directories/index.mdx b/src/content/docs/cloudflare-one/email-security/directories/index.mdx index ff393a60390..3ea464d88da 100644 --- a/src/content/docs/cloudflare-one/email-security/directories/index.mdx +++ b/src/content/docs/cloudflare-one/email-security/directories/index.mdx @@ -12,7 +12,7 @@ Directories are folders to store user data. Email security allows you to manage To add a directory: -1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/) > **Email security**. +1. Log in to [Cloudflare One](https://dash.cloudflare.com/one/) > **Email security**. 2. Select **Directories**. 3. Select **Add a directory** > **Connect an integration**. 4. Select either **Google Workspace CASB + EMAIL** or **Microsoft CASB+EMAIL**. diff --git a/src/content/docs/cloudflare-one/email-security/directories/manage-es-directories.mdx b/src/content/docs/cloudflare-one/email-security/directories/manage-es-directories.mdx index b346156557c..73d1d2aa1f0 100644 --- a/src/content/docs/cloudflare-one/email-security/directories/manage-es-directories.mdx +++ b/src/content/docs/cloudflare-one/email-security/directories/manage-es-directories.mdx @@ -16,7 +16,7 @@ The Email security directory contains registered users only. A registered user i To modify or delete users in the Email security directory: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Email security** > **Directories**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Email security** > **Directories**. 2. Select **Email security Directory**. ## Add a user diff --git a/src/content/docs/cloudflare-one/email-security/directories/manage-integrated-directories/index.mdx b/src/content/docs/cloudflare-one/email-security/directories/manage-integrated-directories/index.mdx index 7e744fd378b..ac3d27f01b5 100644 --- a/src/content/docs/cloudflare-one/email-security/directories/manage-integrated-directories/index.mdx +++ b/src/content/docs/cloudflare-one/email-security/directories/manage-integrated-directories/index.mdx @@ -12,7 +12,7 @@ sidebar: To manage an integrated directory: -1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/). +1. Log in to [Cloudflare One](https://dash.cloudflare.com/one/). 2. Select **Email security**. 3. Select **Directories**. 4. Under **Directory name**, select your directory. diff --git a/src/content/docs/cloudflare-one/email-security/directories/manage-integrated-directories/manage-groups-directory.mdx b/src/content/docs/cloudflare-one/email-security/directories/manage-integrated-directories/manage-groups-directory.mdx index 12046078cac..528554850a0 100644 --- a/src/content/docs/cloudflare-one/email-security/directories/manage-integrated-directories/manage-groups-directory.mdx +++ b/src/content/docs/cloudflare-one/email-security/directories/manage-integrated-directories/manage-groups-directory.mdx @@ -12,7 +12,7 @@ Email security allows you to view and manage your groups directory and their [im To manage a group directory: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Email security** > **Directories**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Email security** > **Directories**. 2. Locate your directory, select the three dots > **View details**. 3. Select **Groups**. diff --git a/src/content/docs/cloudflare-one/email-security/directories/manage-integrated-directories/manage-users-directory.mdx b/src/content/docs/cloudflare-one/email-security/directories/manage-integrated-directories/manage-users-directory.mdx index 639a67496e4..7f8c0add2ee 100644 --- a/src/content/docs/cloudflare-one/email-security/directories/manage-integrated-directories/manage-users-directory.mdx +++ b/src/content/docs/cloudflare-one/email-security/directories/manage-integrated-directories/manage-users-directory.mdx @@ -12,7 +12,7 @@ Email security allows you to view and manage the [impersonation registry](/cloud To manage users directory: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Email security** > **Directories**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Email security** > **Directories**. 2. Locate your directory, select the three dots > **View details**. 3. Select **Users**. diff --git a/src/content/docs/cloudflare-one/email-security/index.mdx b/src/content/docs/cloudflare-one/email-security/index.mdx index ba5fbeb75d6..983265b8fb3 100644 --- a/src/content/docs/cloudflare-one/email-security/index.mdx +++ b/src/content/docs/cloudflare-one/email-security/index.mdx @@ -39,7 +39,7 @@ The Email security overview provides you with: To access the Email security overview: -1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/). +1. Log in to [Cloudflare One](https://dash.cloudflare.com/one/). 2. Go to **Email security** > **Overview**. --- diff --git a/src/content/docs/cloudflare-one/email-security/investigation/search-email.mdx b/src/content/docs/cloudflare-one/email-security/investigation/search-email.mdx index 014c621a7fc..32963263c7b 100644 --- a/src/content/docs/cloudflare-one/email-security/investigation/search-email.mdx +++ b/src/content/docs/cloudflare-one/email-security/investigation/search-email.mdx @@ -16,7 +16,7 @@ Email security allows you to use popular, regular, and advanced screening criter To screen through your email traffic: -1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/). +1. Log in to [Cloudflare One](https://dash.cloudflare.com/one/). 2. Select **Email security**. 3. Select **Investigation**, then **Run new screen**. 4. Choose between **Popular**, **Regular**, and **Advanced** screen methods. Refer to the explanation below to learn what each method does. @@ -81,7 +81,7 @@ Moving messages allows you to move messages to a specific folder. You can move u To move messages: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Email security**, and select **Investigation**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Email security**, and select **Investigation**. 2. On the Investigation page, select all the messages you want to move. 3. Select the **Action** dropdown, then select **Move**. 4. Select among one of the following folders: @@ -100,7 +100,7 @@ Each detection has an Email Detection Fingerprint (EDF) hash that Email security To find similar detection results: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Email security**, and select **Investigation**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Email security**, and select **Investigation**. 2. On the Investigation page, under **Your matching messages**, search for the **Similar emails** column. 3. Select the number of similar emails. Selecting the number will show you a list of similar emails. @@ -110,7 +110,7 @@ With Email security, you can export messages to a CSV file. To export messages: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Email security**, and select **Investigation**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Email security**, and select **Investigation**. 2. On the Investigation page, under **Your matching messages**, select **Export to CSV**. 3. Select **Export messages** on the pop-up message. You can export up to 500 messages from the dashboard. To export up to 1,000 matching messages, use the [API](/api/resources/email_security/subresources/investigate/methods/get/). @@ -122,7 +122,7 @@ Email security allows you to review the status and actions of each email. To view status and actions for each email: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Email security**, and select **Investigation**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Email security**, and select **Investigation**. 2. On the Investigation page, select the three dots. 3. Selecting the three dots will show you the following options: @@ -166,9 +166,9 @@ Email security displays the following details: #### Cloudy summaries -The Cloudflare dashboard uses [Cloudy](/fundamentals/reference/cloudy-ai-agent/) to explain why an email was classified as unwanted. +The Cloudflare dashboard uses [Cloudy](/fundamentals/reference/cloudy-ai-agent/) to explain why an email was classified as unwanted. -Cloudy analyzes the underlying detection code and generates a description of the specific detection logic that led to an email final disposition. Each summary provides a rating option that allows you to provide feedback to the Email security team. Cloudy summaries are only available for emails with a final [disposition](/cloudflare-one/email-security/reference/dispositions-and-attributes/#available-values). +Cloudy analyzes the underlying detection code and generates a description of the specific detection logic that led to an email final disposition. Each summary provides a rating option that allows you to provide feedback to the Email security team. Cloudy summaries are only available for emails with a final [disposition](/cloudflare-one/email-security/reference/dispositions-and-attributes/#available-values). **View all signatures** allows you to view all the detections that triggered on the email, including detections that did not determine the final disposition. @@ -182,7 +182,7 @@ Browser Isolation eliminates any risk of your device being compromised by openin To open links in Security Center: -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Email security** > **Investigation**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Email security** > **Investigation**. 2. Locate the message you want to open links for, select the three dots, then select **View details**. 3. Under **Details**, go to **Links identified**. 4. Locate the link you want to open, and select **Open in Security Center**. @@ -192,7 +192,7 @@ To open links in Security Center: To open links in Browser Isolation: -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Email security** > **Investigation**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Email security** > **Investigation**. 2. Locate the message you want to open links for, select the three dots, then select **View details**. 3. Under **Details**, go to **Links identified**. 4. Locate the link you want to open, and select **Open in Browser Isolation**. @@ -208,7 +208,7 @@ If you purchased Gateway and [Browser Isolation](/cloudflare-one/remote-browser- To open and investigate a link in an external tool: -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Email security** > **Investigation**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Email security** > **Investigation**. 2. Locate the message you want to open links for, select the three dots, then select **View details**. 3. Under **Details**, go to **Links identified**. 4. Locate the link you want to open, and select **Copy URL**. @@ -220,7 +220,7 @@ You may encounter a `400 Bad Request` error after turning Clientless Web Isolati If you encounter this error: -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Settings** > **Resources**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Settings** > **Resources**. 2. Select **Generate certificate**. 3. Choose the **Expiration** (5 years is recommended), then select **Generate certificate**. Your certificate is now generated, and the dashboard will display its Deployment Status as INACTIVE. 4. Select the three dots, and then select **Activate** to activate your certificate. diff --git a/src/content/docs/cloudflare-one/email-security/monitoring/download-report.mdx b/src/content/docs/cloudflare-one/email-security/monitoring/download-report.mdx index f1a29cdbe29..1966e95bfe1 100644 --- a/src/content/docs/cloudflare-one/email-security/monitoring/download-report.mdx +++ b/src/content/docs/cloudflare-one/email-security/monitoring/download-report.mdx @@ -18,7 +18,7 @@ Email security allows you to download three types of reports: A disposition report shows you all the email messages based on the type of disposition you selected. -1. In [Cloudflare One](https://one.dash.cloudflare.com/), select **Email security**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), select **Email security**. 2. Select **Monitoring** > **Download report**. 3. In **Report type**, select **Email disposition report**. 4. Under **Email disposition report**, select the **Date Range** (required), and the **Disposition**. @@ -30,7 +30,7 @@ Refer to [Dispositions and attributes](/cloudflare-one/email-security/reference/ Retro scan scans the last 14 days of your emails, and gives you a report on bulk, spam, spoof, suspicious and malicious emails. -1. In [Cloudflare One](https://one.dash.cloudflare.com/), select **Email security**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), select **Email security**. 2. Select **Monitoring** > **Download report**. 3. In **Report type**, select **Retro Scan report**. 4. Select **View report** to view a report of your last 14 days of emails. @@ -49,7 +49,7 @@ The reports contains: To download a security report: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), select **Email security**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), select **Email security**. 2. Select **Monitoring** > **Download report**. 3. In **Report type**, select **Security report** and the **Date range**. 4. Select **Generate report**. diff --git a/src/content/docs/cloudflare-one/email-security/monitoring/index.mdx b/src/content/docs/cloudflare-one/email-security/monitoring/index.mdx index ea58b10a9fd..a8c81446cfc 100644 --- a/src/content/docs/cloudflare-one/email-security/monitoring/index.mdx +++ b/src/content/docs/cloudflare-one/email-security/monitoring/index.mdx @@ -18,7 +18,7 @@ With Email security, you can enable logs to send detection data to an endpoint o To monitor your inbox: -1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/). +1. Log in to [Cloudflare One](https://dash.cloudflare.com/one/). 2. Select **Email security**. 3. Under **Email security**, select **Monitoring**. diff --git a/src/content/docs/cloudflare-one/email-security/phishguard.mdx b/src/content/docs/cloudflare-one/email-security/phishguard.mdx index 7509b89fc68..d0103208434 100644 --- a/src/content/docs/cloudflare-one/email-security/phishguard.mdx +++ b/src/content/docs/cloudflare-one/email-security/phishguard.mdx @@ -28,7 +28,7 @@ Additionally, PhishGuard analysts: To use PhishGuard: -1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/). +1. Log in to [Cloudflare One](https://dash.cloudflare.com/one/). 2. Select **Email security**. 3. Select **PhishGuard**. diff --git a/src/content/docs/cloudflare-one/email-security/retro-scan.mdx b/src/content/docs/cloudflare-one/email-security/retro-scan.mdx index 4b91685fbaa..37d7b43c541 100644 --- a/src/content/docs/cloudflare-one/email-security/retro-scan.mdx +++ b/src/content/docs/cloudflare-one/email-security/retro-scan.mdx @@ -18,7 +18,7 @@ Retro Scan is only available for Microsoft 365 accounts. To start a free scan: -1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/). +1. Log in to [Cloudflare One](https://dash.cloudflare.com/one/). 2. Select **Email security** > **Overview**. 3. Select **Start a free scan** > **Generate report**. 4. Enable your [Microsoft integration](/cloudflare-one/email-security/setup/post-delivery-deployment/api/m365-api/#enable-microsoft-integration). Once you have enabled your Microsoft integration, you will be redirected to a page where you will add your domains and specify your current email security system. diff --git a/src/content/docs/cloudflare-one/email-security/settings/auto-moves.mdx b/src/content/docs/cloudflare-one/email-security/settings/auto-moves.mdx index 04516541176..2c8c4f06dc2 100644 --- a/src/content/docs/cloudflare-one/email-security/settings/auto-moves.mdx +++ b/src/content/docs/cloudflare-one/email-security/settings/auto-moves.mdx @@ -14,7 +14,7 @@ Use auto-moves to enforce email security policy without relying on end users to To configure auto-move events: -1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/). +1. Log in to [Cloudflare One](https://dash.cloudflare.com/one/). 2. Select **Email security**. 3. Select **Settings**. 4. Select **Moves**. diff --git a/src/content/docs/cloudflare-one/email-security/settings/detection-settings/additional-detections.mdx b/src/content/docs/cloudflare-one/email-security/settings/detection-settings/additional-detections.mdx index 419a402e04f..837d247abcc 100644 --- a/src/content/docs/cloudflare-one/email-security/settings/detection-settings/additional-detections.mdx +++ b/src/content/docs/cloudflare-one/email-security/settings/detection-settings/additional-detections.mdx @@ -17,7 +17,7 @@ Email security allows you to configure the following additional detections: To configure additional detections: -1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/). +1. Log in to [Cloudflare One](https://dash.cloudflare.com/one/). 2. Select **Email security**. 3. Select **Settings**. 4. On the **Settings** page, go to **Detection settings** > **Additional detections**, and select **Edit**. diff --git a/src/content/docs/cloudflare-one/email-security/settings/detection-settings/allow-policies.mdx b/src/content/docs/cloudflare-one/email-security/settings/detection-settings/allow-policies.mdx index d12d8110a67..cd2aa8b73ec 100644 --- a/src/content/docs/cloudflare-one/email-security/settings/detection-settings/allow-policies.mdx +++ b/src/content/docs/cloudflare-one/email-security/settings/detection-settings/allow-policies.mdx @@ -220,7 +220,7 @@ Below you can find a list of known services you can add when configuring an Acce To configure allow policies: -1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/). +1. Log in to [Cloudflare One](https://dash.cloudflare.com/one/). 2. Select **Email security**. 3. Select **Settings**, then go to **Detection settings** > **Allow policies**. 4. On the **Detection settings** page, select **Add a policy**. diff --git a/src/content/docs/cloudflare-one/email-security/settings/detection-settings/blocked-senders.mdx b/src/content/docs/cloudflare-one/email-security/settings/detection-settings/blocked-senders.mdx index 1aa39217251..6f02caa227a 100644 --- a/src/content/docs/cloudflare-one/email-security/settings/detection-settings/blocked-senders.mdx +++ b/src/content/docs/cloudflare-one/email-security/settings/detection-settings/blocked-senders.mdx @@ -20,7 +20,7 @@ Sometimes, the same email, IP address or domain always sends malicious emails to To configure blocked senders: -1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/). +1. Log in to [Cloudflare One](https://dash.cloudflare.com/one/). 2. Select **Email security**. 3. Select **Settings**, go to **Detection settings** > **Blocked senders**. 4. On the **Detection settings** page, select **Add a sender**. diff --git a/src/content/docs/cloudflare-one/email-security/settings/detection-settings/configure-link-actions.mdx b/src/content/docs/cloudflare-one/email-security/settings/detection-settings/configure-link-actions.mdx index 8b057faa60a..c8fa739e486 100644 --- a/src/content/docs/cloudflare-one/email-security/settings/detection-settings/configure-link-actions.mdx +++ b/src/content/docs/cloudflare-one/email-security/settings/detection-settings/configure-link-actions.mdx @@ -16,7 +16,7 @@ You can only configure link actions if you deploy Email security via [MX/Inline] To configure link actions: -1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/). +1. Log in to [Cloudflare One](https://dash.cloudflare.com/one/). 2. Select **Email security**. 3. Select **Settings**, then go to **Detection settings** > **Link actions** > **View**. diff --git a/src/content/docs/cloudflare-one/email-security/settings/detection-settings/configure-text-add-ons.mdx b/src/content/docs/cloudflare-one/email-security/settings/detection-settings/configure-text-add-ons.mdx index a41eb64e5d9..8d1ec93ce19 100644 --- a/src/content/docs/cloudflare-one/email-security/settings/detection-settings/configure-text-add-ons.mdx +++ b/src/content/docs/cloudflare-one/email-security/settings/detection-settings/configure-text-add-ons.mdx @@ -22,7 +22,7 @@ If you currently do not have text add-ons enabled, configuring text add-ons will To configure a subject prefix: -1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/). +1. Log in to [Cloudflare One](https://dash.cloudflare.com/one/). 2. Select **Email security**. 3. Select **Settings**, then go to **Detection settings** > **Text add-ons** > **View**. 4. Select **Configure** > **Subject prefix**. diff --git a/src/content/docs/cloudflare-one/email-security/settings/detection-settings/impersonation-registry.mdx b/src/content/docs/cloudflare-one/email-security/settings/detection-settings/impersonation-registry.mdx index 5627bf13803..6ce2f26283d 100644 --- a/src/content/docs/cloudflare-one/email-security/settings/detection-settings/impersonation-registry.mdx +++ b/src/content/docs/cloudflare-one/email-security/settings/detection-settings/impersonation-registry.mdx @@ -19,7 +19,7 @@ For easier tracking, the Email security team recommends syncing and structuring To add a user to the impersonation registry: -1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/). +1. Log in to [Cloudflare One](https://dash.cloudflare.com/one/). 2. Select **Email security**. 3. Select **Settings** > **Impersonation registry**. 4. Select **Add a user**. diff --git a/src/content/docs/cloudflare-one/email-security/settings/detection-settings/trusted-domains.mdx b/src/content/docs/cloudflare-one/email-security/settings/detection-settings/trusted-domains.mdx index bed68554ed1..384851b0f94 100644 --- a/src/content/docs/cloudflare-one/email-security/settings/detection-settings/trusted-domains.mdx +++ b/src/content/docs/cloudflare-one/email-security/settings/detection-settings/trusted-domains.mdx @@ -26,7 +26,7 @@ Suspicious domain age means that after 7 days (this number corresponds to the Ma To view whether a domain is malicious or suspicious: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Investigation**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Investigation**. 2. Run a screen. For example, select **Run screen** for **Malicious emails**, then select **Run screen**. 3. Under **Your matching messages**, if any message displays **Domain Age** under **Threat types**, that means that the domain age is too low, and therefore the disposition assigned is Malicious. If the domain is legitimate, you can add it as a trusted domain: - Go to **Settings** > **Trusted Domains**. @@ -36,7 +36,7 @@ To view whether a domain is malicious or suspicious: To configure a trusted domain: -1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/). +1. Log in to [Cloudflare One](https://dash.cloudflare.com/one/). 2. Select **Email security**. 3. Select **Settings**, go to **Detection settings** > **Trusted domains**. 4. On the **Detection settings** page, select **Add a domain**. diff --git a/src/content/docs/cloudflare-one/email-security/settings/phish-submissions/index.mdx b/src/content/docs/cloudflare-one/email-security/settings/phish-submissions/index.mdx index b7a8e1e860f..e457a8ac555 100644 --- a/src/content/docs/cloudflare-one/email-security/settings/phish-submissions/index.mdx +++ b/src/content/docs/cloudflare-one/email-security/settings/phish-submissions/index.mdx @@ -22,7 +22,7 @@ There are three routes you can use to report an email as a phish: ## Reclassify an email -1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/). +1. Log in to [Cloudflare One](https://dash.cloudflare.com/one/). 2. Select **Email security** > **Investigation**. 3. On the **Investigation** page, under **Your matching messages**, select the message you want to reclassify. Select the three dots, then select **Submit for review**. By selecting **Submit for review**, you are requesting a new disposition for the message. 4. Select the new disposition, then select **Save**. diff --git a/src/content/docs/cloudflare-one/email-security/settings/phish-submissions/phishnet-365.mdx b/src/content/docs/cloudflare-one/email-security/settings/phish-submissions/phishnet-365.mdx index 03b7792d24a..786812517d1 100644 --- a/src/content/docs/cloudflare-one/email-security/settings/phish-submissions/phishnet-365.mdx +++ b/src/content/docs/cloudflare-one/email-security/settings/phish-submissions/phishnet-365.mdx @@ -16,7 +16,7 @@ PhishNet is an add-in button that helps users to submit directly to Email securi To set up PhishNet Microsoft 365: -1. Get the customized manifest URL from [Cloudflare One](https://one.dash.cloudflare.com/?to=/:account/email-security/settings/email-policy/phish-submission?tab=phish-submission). +1. Get the customized manifest URL from [Cloudflare One](https://dash.cloudflare.com/?to=/:account/one/email-security/settings/email-policy/phish-submission). 2. Log in to the [Microsoft admin panel](https://admin.microsoft.com/). 3. Go to **Microsoft 365 admin center** > **Settings** > **Integrated Apps**. 4. Select **Upload custom apps**. diff --git a/src/content/docs/cloudflare-one/email-security/settings/phish-submissions/submission-addresses.mdx b/src/content/docs/cloudflare-one/email-security/settings/phish-submissions/submission-addresses.mdx index 9e049608ac6..e6207c7e3ac 100644 --- a/src/content/docs/cloudflare-one/email-security/settings/phish-submissions/submission-addresses.mdx +++ b/src/content/docs/cloudflare-one/email-security/settings/phish-submissions/submission-addresses.mdx @@ -10,7 +10,7 @@ sidebar: To view the destination addresses of user and team submissions: -1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/). +1. Log in to [Cloudflare One](https://dash.cloudflare.com/one/). 2. Select **Email security**. 3. Select **Settings**. 4. Go to **Phish submission** > **Submission addresses** > **View**. diff --git a/src/content/docs/cloudflare-one/email-security/setup/manage-domains.mdx b/src/content/docs/cloudflare-one/email-security/setup/manage-domains.mdx index 5c704f3a770..f813165cff8 100644 --- a/src/content/docs/cloudflare-one/email-security/setup/manage-domains.mdx +++ b/src/content/docs/cloudflare-one/email-security/setup/manage-domains.mdx @@ -13,7 +13,7 @@ Once you have deployed your domain, Email security allows you to add, filter and To protect a new domain: -1. Log in to [Cloudflare One](https://one.dash.cloudflare.com) > Email security. +1. Log in to [Cloudflare One](https://dash.cloudflare.com/one/) > Email security. 2. Select **Settings**, go to **Domains** and select **View**. 3. Select **Add a domain**. @@ -21,7 +21,7 @@ To protect a new domain: To filter your domains: -1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/) > **Email security**. +1. Log in to [Cloudflare One](https://dash.cloudflare.com/one/) > **Email security**. 2. Go to **Settings** > **Domain management** > **Domains**, then select **View**. 3. Select **Show filters** > **Configured method**. Choose among the following filters: - **MS Graph API**: To view domains connected via MS Graph API. - **BCC/Journaling**: To view domains connected via BCC/Journaling. - **MX/Inline**: To view domains connected via MX/Inline. - **Retro Scan**: To view domains scanned by Retro Scan. 4. Select **Apply filters**. @@ -30,7 +30,7 @@ To filter your domains: To edit your domains: -1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/) > **Email security**. +1. Log in to [Cloudflare One](https://dash.cloudflare.com/one/) > **Email security**. 2. Go to **Settings** > **Domain management** > **Domains**, then select **View**. 3. On the **Domains** page, locate your domain, select the three dots > **Edit**. 4. If you did not manually add your domain, you will only be able to edit **Hops**. If you manually added your domain, you will be able to edit **Domain name** and **Hops**. @@ -40,7 +40,7 @@ To edit your domains: To stop scanning domains: -1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/) > **Email security**. +1. Log in to [Cloudflare One](https://dash.cloudflare.com/one/) > **Email security**. 2. Go to **Settings** > **Domain management** > **Domains**, then select **View**. 3. On the **Domains** page, locate your domain, select the three dots > **Stop scanning**. 4. Select **Stop scanning** again to stop Cloudflare from scanning your domain. \ No newline at end of file diff --git a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/api/m365-api.mdx b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/api/m365-api.mdx index fdd6e5cc02d..c855ffd0e45 100644 --- a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/api/m365-api.mdx +++ b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/api/m365-api.mdx @@ -25,7 +25,7 @@ To use Email security, you will need to have: ## Enable Email security via the dashboard -1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/) and select **Email security**.. +1. Log in to [Cloudflare One](https://dash.cloudflare.com/one/) and select **Email security**.. 2. Select **Overview**. Select one of the following options depending on your use case: - If you have not purchased Email security, select **Contact sales**. @@ -68,7 +68,7 @@ Your domains are now connected successfully. To connect new domains: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), select **Email security**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), select **Email security**. 2. Select **Settings** > **Domain management** > **Domains**, then select **View**. 3. Select **Add a domain**. 4. Select a method for connecting your mail environment to Email security: @@ -82,7 +82,7 @@ To connect new domains: If you want to prevent Cloudflare from scanning a domain: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), select **Email security**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), select **Email security**. 2. Go to **Settings** > **Domain management** > **Domains**, then select **View**. 3. On the **Domain management** page, select the domain you do not want to be scanned. 4. Select the three dots > **Stop scanning**. @@ -91,7 +91,7 @@ If you want to prevent Cloudflare from scanning a domain: To view the integration for each connected domain: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), select **Email security**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), select **Email security**. 2. Go to **Settings** > **Domain management** > **Domains**, then select **View**. 3. Select a domain. 4. Select the three dots > **View integration**. diff --git a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/add-bcc-rules.mdx b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/add-bcc-rules.mdx index a18a3bcf4d6..08c21e647fa 100644 --- a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/add-bcc-rules.mdx +++ b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/add-bcc-rules.mdx @@ -32,7 +32,7 @@ To add BCC rules: - Ensure that **Envelope recipient** > **Change envelope recipient** is unselected, so that emails will not be dropped as an unintended consequence. You will select this option at a later stage. - Go to **Also deliver to**, select **Add more recipients** > **ADD** > Choose **Advanced**: - Under **Envelope recipient**, select **Change envelope recipient** > **Replace recipient** > Enter the service address. This is the service address you copied and pasted in step 5 when [connecting your domains](/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/connect-domains/). - If you did not copy and paste the service address: - In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Email security**. - Go to **Settings** and locate your domain under **Your domains**. - Select the three dots > **View domain** > **Service address**. Copy and paste the service address. + If you did not copy and paste the service address: - In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Email security**. - Go to **Settings** and locate your domain under **Your domains**. - Select the three dots > **View domain** > **Service address**. Copy and paste the service address. - Under **Spam and delivery options**, ensure **Suppress bounces from this recipient** is not enabled. - Under **Headers**, select **Add X-Gm-Spam and X-Gm-Phishy headers**. - Select **SAVE**. @@ -41,6 +41,6 @@ To add BCC rules: To verify that BCC rules have been configured successfully: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Email security** > **Settings**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Email security** > **Settings**. 2. Select **Domains** > **View**. 3. Locate your domain. Under Status, the dashboard should display **Active**. This means that the BCC rules have been configured successfully, and your mail flow is being detected. diff --git a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/connect-domains.mdx b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/connect-domains.mdx index 0d6916e81d6..25365b8d35b 100644 --- a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/connect-domains.mdx +++ b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/connect-domains.mdx @@ -31,7 +31,7 @@ Under **Source**, the dashboard will display **Google integration**, along with To add additional domains: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Email security** > **Settings**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Email security** > **Settings**. 2. Select **Connect an integration** > **BCC/Journaling** > **Integrate with Google** > **Authorize**. 3. **Connect domains**: Select the domains you want to add, then select **Next**. 4. (Optional) Select **Add manual domains**: Enter additional domains manually, then select **Next**. diff --git a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/enable-auto-moves.mdx b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/enable-auto-moves.mdx index a31864db847..69eebdb20f9 100644 --- a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/enable-auto-moves.mdx +++ b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/enable-auto-moves.mdx @@ -10,7 +10,7 @@ sidebar: If you do not have an integration: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Email security**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Email security**. 2. Go to **Settings** > **Domain management** > **Domains** > select **View**. 3. Locate your domain, select the three dots > Select **Associate an integration**. 4. Select **Connect an integration**. You will then be redirected to the **Add an integration** page. diff --git a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/enable-gmail-integration.mdx b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/enable-gmail-integration.mdx index 0264b89bc62..c7e7c1982ea 100644 --- a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/enable-gmail-integration.mdx +++ b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/enable-gmail-integration.mdx @@ -25,7 +25,7 @@ To use Email security, you will need to have: ## Enable Gmail BCC integration: -1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/). +1. Log in to [Cloudflare One](https://dash.cloudflare.com/one/). 2. Select **Email security**. 3. Select **Overview**. Select one of the following options: @@ -62,7 +62,7 @@ On the [Google Cloud Console](https://console.cloud.google.com/welcome/new): ### 3. Upload JSON Key -On the [Cloudflare One dashboard](https://one.dash.cloudflare.com/), upload the `.json` file downloaded on step 3. +On the [Cloudflare One dashboard](https://dash.cloudflare.com/one/), upload the `.json` file downloaded on step 3. ### 4. Enable Necessary Google Workspace APIs in GCP @@ -99,7 +99,7 @@ Enter the email associated with the Google Workspace Administrator account. Your To verify that the integration has been successful: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Integrations**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Integrations**. 2. Under **Your integrations**, locate your integration, and ensure that the integration displays **CASB+EMAIL** under **Type**. :::note diff --git a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/m365-journaling.mdx b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/m365-journaling.mdx index 8ff736556bd..a0b80a4f03b 100644 --- a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/m365-journaling.mdx +++ b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/m365-journaling.mdx @@ -20,7 +20,7 @@ The following diagram shows how this works: To enable Microsoft 365 journaling deployment: -1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/) > **Email security**. +1. Log in to [Cloudflare One](https://dash.cloudflare.com/one/) > **Email security**. 2. Select **Overview**. If you have not purchased Email security, select **Contact Sales**. Otherwise, select **Set up** > **BCC/Journaling**. 3. Select **Integrate with MS** > **Authorize**. 4. Continue with [Integrate with Microsoft 365](/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/m365-journaling/#1-integrate-with-microsoft-365) to connect your Microsoft integration. @@ -91,7 +91,7 @@ Once saved, the rule is automatically active. However, it may take a few minutes To verift that your domain has been added successfully and that your emails are being scanned: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), select **Email security**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), select **Email security**. 2. Go to **Settings** > **Domain management** > **Domains**, then select **View**. 3. Under **Your domains**, locate your domain, and verify that **Status** is set to **Active**. The **Configured method** should be **BCC/Journaling**. diff --git a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/manual-add.mdx b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/manual-add.mdx index 4c636aa1972..7aeddb5a8e4 100644 --- a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/manual-add.mdx +++ b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/manual-add.mdx @@ -25,7 +25,7 @@ To use Email security, you will need to have: ## Manually add domains -1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/) > **Email security**. +1. Log in to [Cloudflare One](https://dash.cloudflare.com/one/) > **Email security**. 2. Select **Overview**. If you have not purchased Email security, select **Contact Sales**. Otherwise, select **Set up** > **BCC/Journaling**. 3. Select **Manual add**. @@ -66,7 +66,7 @@ To enable auto-move events, you will have to associate an integration. To associate an integration: -1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/) > **Email security**. +1. Log in to [Cloudflare One](https://dash.cloudflare.com/one/) > **Email security**. 2. Go to **Settings** > **Domain management** > **Domains** > Select **View**. 3. On the **Domain management** page, locate your domain, select the three dots, then select **Associate an integration**. 4. Select **Connect an integration**. Follow the steps to [enable the Microsoft 365 integration](/cloudflare-one/email-security/setup/post-delivery-deployment/api/m365-api/#enable-microsoft-integration). diff --git a/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/mx-inline-deployment-setup.mdx b/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/mx-inline-deployment-setup.mdx index ccf3b139b35..60150a34a5a 100644 --- a/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/mx-inline-deployment-setup.mdx +++ b/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/mx-inline-deployment-setup.mdx @@ -21,7 +21,7 @@ To use Email security, you will need to have: ## Initiate MX/Inline configuration -1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/). +1. Log in to [Cloudflare One](https://dash.cloudflare.com/one/). 2. Select **Email security**. 3. Select **Overview**. Select one of the following options: @@ -42,7 +42,7 @@ MX/Inline does not require an integration for protection to be effective. Howeve To associate an integration: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Integrations** > **Cloud & SaaS Integrations** > **Integrations** +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Integrations** > **Cloud & SaaS Integrations** > **Integrations** 2. Select **Connect an integration**. 3. Select an application: Choose between **Google Workspace CASB + EMAIL**, or **Microsoft CASB + EMAIL**. - Refer to [Enable Gmail BCC integration](/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/enable-gmail-integration/#1-create-a-service-account-in-your-gcp-project) if you select **Google Workspace CASB + EMAIL**. diff --git a/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/partner-domain-tls.mdx b/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/partner-domain-tls.mdx index d33970c1736..0d7dfb4020e 100644 --- a/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/partner-domain-tls.mdx +++ b/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/partner-domain-tls.mdx @@ -18,7 +18,7 @@ To enforce TLS across all emails, you will need to enforce TLS requirements when To set up a partner domain: -1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/) and select **Email security**. +1. Log in to [Cloudflare One](https://dash.cloudflare.com/one/) and select **Email security**. 2. Select **Settings** > **Partner domain TLS** > **View**. 3. Select **Add a domain**. 4. Enter a valid domain name. You can also exclude subdomains by selecting **Add exclude**. diff --git a/src/content/docs/cloudflare-one/email-security/submissions/index.mdx b/src/content/docs/cloudflare-one/email-security/submissions/index.mdx index 14e7f12e83a..2509ab1862b 100644 --- a/src/content/docs/cloudflare-one/email-security/submissions/index.mdx +++ b/src/content/docs/cloudflare-one/email-security/submissions/index.mdx @@ -14,7 +14,7 @@ Submitting messages allows you to choose the disposition of your messages if the To submit a message for review: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Email security** and select **Investigation**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Email security** and select **Investigation**. 2. On the **Investigation** page, under **Your matching messages**, select the message you want to reclassify. 3. Select the three dots, then select **Submit for review**. 4. Under **New disposition**, select among the following: @@ -47,7 +47,7 @@ Once you have submitted your messages, you can access those on **Submissions**. To view submissions: -1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/). +1. Log in to [Cloudflare One](https://dash.cloudflare.com/one/). 2. Select **Email security** > **Submissions**. 3. Choose from the following submission types: - [**Team submissions**](/cloudflare-one/email-security/submissions/team-submissions/): View emails your security team submitted for submissions. diff --git a/src/content/docs/cloudflare-one/email-security/submissions/invalid-submissions.mdx b/src/content/docs/cloudflare-one/email-security/submissions/invalid-submissions.mdx index aff37d96e27..24b608aad02 100644 --- a/src/content/docs/cloudflare-one/email-security/submissions/invalid-submissions.mdx +++ b/src/content/docs/cloudflare-one/email-security/submissions/invalid-submissions.mdx @@ -22,7 +22,7 @@ To ensure your submission is valid: To view invalid submissions: -1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/). +1. Log in to [Cloudflare One](https://dash.cloudflare.com/one/). 2. Select **Email security** > **Submissions**. 3. Select **Invalid submissions**. @@ -34,6 +34,6 @@ You can filter based on **Date Range** and **Submitted by** (which will list ema To enable Invalid submission email notifications: -1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/). +1. Log in to [Cloudflare One](https://dash.cloudflare.com/one/). 2. Select **Email security** > **Settings**. 3. Go to **Invalid submission emails** and turn on **Invalid submission email notifications**. \ No newline at end of file diff --git a/src/content/docs/cloudflare-one/email-security/submissions/team-submissions.mdx b/src/content/docs/cloudflare-one/email-security/submissions/team-submissions.mdx index 0520ccc6a30..52aa915003b 100644 --- a/src/content/docs/cloudflare-one/email-security/submissions/team-submissions.mdx +++ b/src/content/docs/cloudflare-one/email-security/submissions/team-submissions.mdx @@ -14,7 +14,7 @@ Team submissions are the emails your security team submitted for submission. All To view team submissions: -1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/). +1. Log in to [Cloudflare One](https://dash.cloudflare.com/one/). 2. Select **Email security** > **Submissions**. 3. Select **Team submissions**. diff --git a/src/content/docs/cloudflare-one/email-security/submissions/user-submissions.mdx b/src/content/docs/cloudflare-one/email-security/submissions/user-submissions.mdx index 157f7404a08..ace52e518d0 100644 --- a/src/content/docs/cloudflare-one/email-security/submissions/user-submissions.mdx +++ b/src/content/docs/cloudflare-one/email-security/submissions/user-submissions.mdx @@ -20,7 +20,7 @@ Any email that is reported as [phish](/cloudflare-one/email-security/settings/ph To view user submissions: -1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/). +1. Log in to [Cloudflare One](https://dash.cloudflare.com/one/). 2. Select **Email security** > **Submissions**. 3. Select **User submissions**. diff --git a/src/content/docs/cloudflare-one/faq/getting-started-faq.mdx b/src/content/docs/cloudflare-one/faq/getting-started-faq.mdx index 5458f590e84..93c0b2d9dbb 100644 --- a/src/content/docs/cloudflare-one/faq/getting-started-faq.mdx +++ b/src/content/docs/cloudflare-one/faq/getting-started-faq.mdx @@ -14,11 +14,11 @@ description: Review FAQs about getting started with Cloudflare Zero Trust. ## How do I sign up for Cloudflare Zero Trust? -You can sign up today at [this link](https://one.dash.cloudflare.com). Follow the onboarding steps, choose a team name and a payment plan, and start protecting your network in just a few minutes. +You can sign up today at [this link](https://dash.cloudflare.com/one/). Follow the onboarding steps, choose a team name and a payment plan, and start protecting your network in just a few minutes. ## What is a team domain/team name? -Your team domain is a unique subdomain assigned to your Cloudflare account, for example, `.cloudflareaccess.com`. [Setting up a team domain](/cloudflare-one/setup/#2-create-a-zero-trust-organization) is an essential step in your Zero Trust configuration. This is where your users will find the apps you have secured behind Cloudflare Zero Trust — displayed in the [App Launcher](/cloudflare-one/access-controls/access-settings/app-launcher/) — and will be able to make login requests to them. The customizable portion of your team domain is called **team name**. You can view your team name and team domain in [Cloudflare One](https://one.dash.cloudflare.com/) under **Settings**. +Your team domain is a unique subdomain assigned to your Cloudflare account, for example, `.cloudflareaccess.com`. [Setting up a team domain](/cloudflare-one/setup/#2-create-a-zero-trust-organization) is an essential step in your Zero Trust configuration. This is where your users will find the apps you have secured behind Cloudflare Zero Trust — displayed in the [App Launcher](/cloudflare-one/access-controls/access-settings/app-launcher/) — and will be able to make login requests to them. The customizable portion of your team domain is called **team name**. You can view your team name and team domain in [Cloudflare One](https://dash.cloudflare.com/one/) under **Settings**. | team name | team domain | | ---------------- | --------------------------------------- | @@ -52,7 +52,7 @@ After changing your team name, you will need to check your Block page, Login pag To verify that your team name change is successfully rendering on the Block page, Login page and App Launcher: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Custom pages** > **Team name and domain**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Custom pages** > **Team name and domain**. 2. Find the **Account Gateway block page** and **Access login page** sections, then select **Manage** next to the page you would like to review first. 3. Review that the value in **Your Organization's name** matches your new team name. 4. If the desired name is not already displayed, change the value to your desired team name and select **Save**. @@ -62,7 +62,7 @@ The App Launcher will display the same team name set on the Access login page, s ## How do I change my subscription plan? -To make changes to your subscription, visit the Billing section under **Settings** in [Cloudflare One](https://one.dash.cloudflare.com/). You can change or cancel your subscription at any time. Just remember - if you downgrade your plan during a billing cycle, your downgraded pricing will apply in the next billing cycle. If you upgrade during a billing cycle, you will be billed for the upgraded plan at the moment you select it. +To make changes to your subscription, visit the Billing section under **Settings** in [Cloudflare One](https://dash.cloudflare.com/one/). You can change or cancel your subscription at any time. Just remember - if you downgrade your plan during a billing cycle, your downgraded pricing will apply in the next billing cycle. If you upgrade during a billing cycle, you will be billed for the upgraded plan at the moment you select it. ## How are active seats measured? diff --git a/src/content/docs/cloudflare-one/index.mdx b/src/content/docs/cloudflare-one/index.mdx index 95a23a9ad7e..17360f6271a 100644 --- a/src/content/docs/cloudflare-one/index.mdx +++ b/src/content/docs/cloudflare-one/index.mdx @@ -50,7 +50,7 @@ Refer to our [SASE reference architecture](/reference-architecture/architectures Get started - + Cloudflare One dashboard diff --git a/src/content/docs/cloudflare-one/insights/analytics-overview.mdx b/src/content/docs/cloudflare-one/insights/analytics-overview.mdx index 94280945992..5c88dafe786 100644 --- a/src/content/docs/cloudflare-one/insights/analytics-overview.mdx +++ b/src/content/docs/cloudflare-one/insights/analytics-overview.mdx @@ -14,7 +14,7 @@ import { Render } from "~/components"; The Cloudflare One Analytics overview provides a dashboard that reports on how Cloudflare One is protecting your organization and networks. Use this page to monitor usage and potential security concerns within your organization. -To view the Analytics overview, log in to [Cloudflare One](https://one.dash.cloudflare.com) and go to **Overview**. +To view the Analytics overview, log in to [Cloudflare One](https://dash.cloudflare.com/one/) and go to **Overview**. The Analytics overview includes reports and insights across the following products and categories: diff --git a/src/content/docs/cloudflare-one/insights/dex/ip-visibility.mdx b/src/content/docs/cloudflare-one/insights/dex/ip-visibility.mdx index 5d32a72c03c..4bedabe5b47 100644 --- a/src/content/docs/cloudflare-one/insights/dex/ip-visibility.mdx +++ b/src/content/docs/cloudflare-one/insights/dex/ip-visibility.mdx @@ -55,7 +55,7 @@ IP information helps IT administrators troubleshoot network issues and identify To view IP information for a user device: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Team & Resources** > **Devices** > **Your devices**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Team & Resources** > **Devices** > **Your devices**. 2. Select a device, then select **View details**. 3. Go to **IP details**. 4. Review the IP details for your selected device's most recent session. @@ -64,7 +64,7 @@ To view IP information for a user device: DEX's IP visibility allows you to review an event log of a device's IP history for the last seven days. To view a device's IP history: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Team & Resources** > **Devices** > **Your devices**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Team & Resources** > **Devices** > **Your devices**. 2. Select a device > **View details** > go to **IP details**. 3. Select **View all ISPs**. diff --git a/src/content/docs/cloudflare-one/insights/dex/monitoring.mdx b/src/content/docs/cloudflare-one/insights/dex/monitoring.mdx index 056e13ea2ec..4a0dc50e98a 100644 --- a/src/content/docs/cloudflare-one/insights/dex/monitoring.mdx +++ b/src/content/docs/cloudflare-one/insights/dex/monitoring.mdx @@ -20,7 +20,7 @@ A fleet is a collection of user devices. All devices in a fleet have the Cloudfl To view fleet status: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Insights** > **Digital experience**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Insights** > **Digital experience**. 2. Review the information under **Live analytics**. ### View metrics @@ -62,7 +62,7 @@ Review network and device performance for a device enrolled in your fleet. To view a device's network and device performance metrics: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Team & Resources** > **Devices** > **Your devices**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Team & Resources** > **Devices** > **Your devices**. 2. Select a device > **View details**. 3. Select the **DEX** tab. 4. In **Device Monitoring**, scroll down to **Network performance** and **Device Performance**. diff --git a/src/content/docs/cloudflare-one/insights/dex/rules.mdx b/src/content/docs/cloudflare-one/insights/dex/rules.mdx index 0823f895e22..2902d31baef 100644 --- a/src/content/docs/cloudflare-one/insights/dex/rules.mdx +++ b/src/content/docs/cloudflare-one/insights/dex/rules.mdx @@ -20,7 +20,7 @@ Use DEX rules to scope a test to a specific group within your fleet for more pre To create a rule: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Insights** > **Digital experience**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Insights** > **Digital experience**. 2. Select the **Rules** tab. 3. Select **Add a rule**. 4. Give your rule a name and build your desired expressions. @@ -50,7 +50,7 @@ After you have created a rule, you can add it to a test. If you do not add a rul To add a rule to a test: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Insights** > **Digital experience**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Insights** > **Digital experience**. 2. Select the **Tests** tab. 3. Choose an existing test and select **Edit**, or select **Add a test** to make a new test. 4. Under **Select DEX rules**, select the rule you would like to apply. @@ -63,7 +63,7 @@ To add a rule to a test: To view which tests a rule is being applied to: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Insights** > **Digital experience**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Insights** > **Digital experience**. 2. Select the **Rules** tab. 3. Choose a rule and select **Edit**. 4. Select the **DEX tests** tab and review the list of tests that include your selected rule. @@ -74,7 +74,7 @@ You can create a new test from the [DEX test dashboard as described above](/clou To create a new test using a rule from DEX rules: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Insights** > **Digital experience**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Insights** > **Digital experience**. 2. Select the **Rules** tab. 3. Select a rule and select **Edit**. 4. Select the **DEX tests** tab. diff --git a/src/content/docs/cloudflare-one/insights/dex/tests/traceroute.mdx b/src/content/docs/cloudflare-one/insights/dex/tests/traceroute.mdx index 5b34e06f307..19b1e47b97b 100644 --- a/src/content/docs/cloudflare-one/insights/dex/tests/traceroute.mdx +++ b/src/content/docs/cloudflare-one/insights/dex/tests/traceroute.mdx @@ -37,7 +37,7 @@ A traceroute test measures the network path of an IP packet from an end-user dev To set up a traceroute test for an application: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Insights** > **Digital experience**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Insights** > **Digital experience**. 2. Select the **Tests** tab. 3. Select **Add a Test**. 4. Fill in the following fields: diff --git a/src/content/docs/cloudflare-one/insights/dex/tests/view-results.mdx b/src/content/docs/cloudflare-one/insights/dex/tests/view-results.mdx index 49384d7583f..0bfb994bb63 100644 --- a/src/content/docs/cloudflare-one/insights/dex/tests/view-results.mdx +++ b/src/content/docs/cloudflare-one/insights/dex/tests/view-results.mdx @@ -21,7 +21,7 @@ Use the results of a Digital Experience Monitoring (DEX) test to monitor availab To view an overview of test results for all devices: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Insights** > **Digital experience**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Insights** > **Digital experience**. 2. Select the **Tests** tab. 3. Select a test to view detailed results. @@ -29,7 +29,7 @@ To view an overview of test results for all devices: To view analytics on a per-device level: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Team & Resources** > **Devices** > **Your devices**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Team & Resources** > **Devices** > **Your devices**. 2. Select the device you want to view, and then select **View details**. 3. Select the **Tests** tab. 4. Select a test to view detailed results. diff --git a/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/access-authentication-logs.mdx b/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/access-authentication-logs.mdx index 6b1482a360b..a5cfa9bebb7 100644 --- a/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/access-authentication-logs.mdx +++ b/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/access-authentication-logs.mdx @@ -38,7 +38,7 @@ Authentication logs do not capture the user's actions during a self-hosted or Sa To view logs for identity-based authentication events: -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Insights** > **Logs**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Insights** > **Logs**. 2. Select **Access authentication logs**. :::note[Log viewer (beta)] diff --git a/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/admin-activity-logs.mdx b/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/admin-activity-logs.mdx index 33c342dcf54..d5d2caed8e4 100644 --- a/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/admin-activity-logs.mdx +++ b/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/admin-activity-logs.mdx @@ -12,7 +12,7 @@ tags: Admin activity logs record configuration changes made by members of your Cloudflare account. Use these logs to monitor when a member creates, updates, or deletes configurations in your Zero Trust organization. -To view admin activity logs, log in to [Cloudflare One](https://one.dash.cloudflare.com/) and go to **Insights** > **Logs** > **Admin activity logs**. +To view admin activity logs, log in to [Cloudflare One](https://dash.cloudflare.com/one/) and go to **Insights** > **Logs** > **Admin activity logs**. ## Explanation of the fields diff --git a/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/gateway-logs/index.mdx b/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/gateway-logs/index.mdx index 1bcf8ff3cce..290521c5476 100644 --- a/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/gateway-logs/index.mdx +++ b/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/gateway-logs/index.mdx @@ -28,7 +28,7 @@ Gateway logs will only show the public IP address for the **Source IP** field. P To view Gateway activity logs: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Insights** > **Logs**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Insights** > **Logs**. 2. Choose a type of Gateway log: - **DNS query logs** - **Network logs** @@ -45,7 +45,7 @@ To view Gateway activity logs: ## Selective logging -By default, Gateway logs all events, including DNS queries and HTTP requests that are allowed and not a risk. You can choose to disable logs or only log blocked requests. To customize what type of events are recorded, log in to [Cloudflare One](https://one.dash.cloudflare.com/) and go to **Traffic policies** > **Traffic settings**. Under **Traffic logging** > **Log traffic activity**, indicate your DNS, Network, and HTTP log preferences. +By default, Gateway logs all events, including DNS queries and HTTP requests that are allowed and not a risk. You can choose to disable logs or only log blocked requests. To customize what type of events are recorded, log in to [Cloudflare One](https://dash.cloudflare.com/one/) and go to **Traffic policies** > **Traffic settings**. Under **Traffic logging** > **Log traffic activity**, indicate your DNS, Network, and HTTP log preferences. These settings will only apply to logs displayed in Cloudflare One. Logpush data is unaffected. @@ -299,7 +299,7 @@ Enhanced file detection is an optional feature to extract more file information To turn on enhanced file detection: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Traffic policies** > **Traffic settings**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Traffic policies** > **Traffic settings**. 2. In **Proxy and inspection settings**, turn on **Inspect HTTPS requests with TLS decryption**. 3. In **Policy settings**, turn on **Allow enhanced file detection**. diff --git a/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/gateway-logs/manage-pii.mdx b/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/gateway-logs/manage-pii.mdx index 7189b47d05f..9fdfd307465 100644 --- a/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/gateway-logs/manage-pii.mdx +++ b/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/gateway-logs/manage-pii.mdx @@ -32,5 +32,5 @@ Turning on the setting to exclude PII means Cloudflare Gateway will log activity To turn on the setting to exclude PII: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Traffic policies** > **Traffic settings**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Traffic policies** > **Traffic settings**. 2. In **Traffic logging**, turn on **Exclude personally identifiable information (PII) from logs**. diff --git a/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/index.mdx b/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/index.mdx index 742ed2d2b4b..11662f0c519 100644 --- a/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/index.mdx +++ b/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/index.mdx @@ -13,7 +13,7 @@ head: import { DirectoryListing } from "~/components"; -The following logs are available in the [Cloudflare One dashboard](https://one.dash.cloudflare.com/). +The following logs are available in the [Cloudflare One dashboard](https://dash.cloudflare.com/one/). diff --git a/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/posture-logs.mdx b/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/posture-logs.mdx index ee69dfdf58e..3f36a973ba2 100644 --- a/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/posture-logs.mdx +++ b/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/posture-logs.mdx @@ -12,7 +12,7 @@ tags: Posture logs show the [device posture check](/cloudflare-one/reusable-components/posture-checks/) results reported by the Cloudflare One Client. -To view device posture logs, log in to [Cloudflare One](https://one.dash.cloudflare.com/) and go to **Insights** > **Logs** > **Posture logs**. Logs will only display if you have configured [device posture checks](/cloudflare-one/reusable-components/posture-checks/) for your Zero Trust organization. +To view device posture logs, log in to [Cloudflare One](https://dash.cloudflare.com/one/) and go to **Insights** > **Logs** > **Posture logs**. Logs will only display if you have configured [device posture checks](/cloudflare-one/reusable-components/posture-checks/) for your Zero Trust organization. Enterprise users can generate more detailed logs with [Logpush](/cloudflare-one/insights/logs/logpush/). diff --git a/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/scim-logs.mdx b/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/scim-logs.mdx index 3df56f6e3fa..2803de171ee 100644 --- a/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/scim-logs.mdx +++ b/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/scim-logs.mdx @@ -16,7 +16,7 @@ SCIM activity logs allow administrators to audit how [SCIM provisioning](/cloudf ## View SCIM logs -For an overview of SCIM events across all users, log in to [Cloudflare One](https://one.dash.cloudflare.com/) and go to **Insights** > **Logs** > **SCIM provisioning logs**. This page lists the inbound SCIM requests from all identity providers configured with SCIM. You can select an individual request to view more details about the SCIM operation. +For an overview of SCIM events across all users, log in to [Cloudflare One](https://dash.cloudflare.com/one/) and go to **Insights** > **Logs** > **SCIM provisioning logs**. This page lists the inbound SCIM requests from all identity providers configured with SCIM. You can select an individual request to view more details about the SCIM operation. To investigate how SCIM events impacted a specific user, go to their [User Registry identity](/cloudflare-one/team-and-resources/users/users/). diff --git a/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/ssh-command-logs.mdx b/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/ssh-command-logs.mdx index acfeeae3e33..b7da7930ff5 100644 --- a/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/ssh-command-logs.mdx +++ b/src/content/docs/cloudflare-one/insights/logs/dashboard-logs/ssh-command-logs.mdx @@ -13,7 +13,7 @@ tags: SSH command logs record the commands that users run on infrastructure targets protected by [Access for Infrastructure](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/ssh/ssh-infrastructure-access/). Use these logs to audit user activity on your SSH servers. -To view SSH command logs, log in to [Cloudflare One](https://one.dash.cloudflare.com/) and go to **Insights** > **Logs** > **SSH command logs**. +To view SSH command logs, log in to [Cloudflare One](https://dash.cloudflare.com/one/) and go to **Insights** > **Logs** > **SSH command logs**. ## Prerequisites @@ -26,7 +26,7 @@ To generate SSH command logs, you must: SSH command logs displayed in the dashboard are encrypted using a public key you provide. To view the contents of the logs: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Insights** > **Logs** > **SSH command logs**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Insights** > **Logs** > **SSH command logs**. 2. Filter the logs using the name of your SSH application. 3. Select the SSH session for which you want to export command logs. 4. In the side panel, scroll down to **SSH logs** and select **Download**. diff --git a/src/content/docs/cloudflare-one/insights/logs/logpush/index.mdx b/src/content/docs/cloudflare-one/insights/logs/logpush/index.mdx index 5ad8f1fabd7..41fbd2f38d0 100644 --- a/src/content/docs/cloudflare-one/insights/logs/logpush/index.mdx +++ b/src/content/docs/cloudflare-one/insights/logs/logpush/index.mdx @@ -20,7 +20,7 @@ With Cloudflare's [Logpush](/logs/logpush/) service, you can configure the autom To configure Logpush for Zero Trust logs: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Insights** > **Logs**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Insights** > **Logs**. 2. Select **Manage Logpush**. 3. In Logpush, select **Create a Logpush job**. 4. Choose a [Logpush destination](/logs/logpush/logpush-job/enable-destinations/). diff --git a/src/content/docs/cloudflare-one/insights/network-visibility/diagnostics/buckets.mdx b/src/content/docs/cloudflare-one/insights/network-visibility/diagnostics/buckets.mdx index f17068f82df..301c112c59a 100644 --- a/src/content/docs/cloudflare-one/insights/network-visibility/diagnostics/buckets.mdx +++ b/src/content/docs/cloudflare-one/insights/network-visibility/diagnostics/buckets.mdx @@ -22,7 +22,7 @@ Learn how to set up a bucket for use with full packet captures. -1. In the [Cloudflare One](https://one.dash.cloudflare.com) dashboard, go to **Network visibility** > **Diagnostics**. +1. In the [Cloudflare One](https://dash.cloudflare.com/one/) dashboard, go to **Network visibility** > **Diagnostics**. 2. Select the **Buckets** tab > **Add a bucket**. 3. Select a bucket service and select **Next**. 4. Enter the information related to your bucket for your service provider. diff --git a/src/content/docs/cloudflare-one/insights/network-visibility/diagnostics/packet-captures.mdx b/src/content/docs/cloudflare-one/insights/network-visibility/diagnostics/packet-captures.mdx index 9867135ba2a..080b670c528 100644 --- a/src/content/docs/cloudflare-one/insights/network-visibility/diagnostics/packet-captures.mdx +++ b/src/content/docs/cloudflare-one/insights/network-visibility/diagnostics/packet-captures.mdx @@ -230,7 +230,7 @@ After your request finishes processing, you can download your packet captures. -1. In the [Cloudflare One](https://one.dash.cloudflare.com) dashboard, go to **Network visibility** > **Diagnostics**. +1. In the [Cloudflare One](https://dash.cloudflare.com/one/) dashboard, go to **Network visibility** > **Diagnostics**. 2. In **Packet captures**, select **Start a capture**. 3. Locate your packet capture you want to download, and select **Download**. diff --git a/src/content/docs/cloudflare-one/integrations/cloud-and-saas/aws-s3.mdx b/src/content/docs/cloudflare-one/integrations/cloud-and-saas/aws-s3.mdx index b7f683bba09..92836ee1aa3 100644 --- a/src/content/docs/cloudflare-one/integrations/cloud-and-saas/aws-s3.mdx +++ b/src/content/docs/cloudflare-one/integrations/cloud-and-saas/aws-s3.mdx @@ -52,7 +52,7 @@ You can only connect one computer account to an integration. To remove a compute Once your AWS compute account has successfully connected to your CASB integration, you can configure where and how to scan for sensitive data: -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Integrations** > **Cloud & SaaS integrations**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Integrations** > **Cloud & SaaS integrations**. 2. Find and select your AWS integration. 3. Select **Create new configuration**. 4. In **Resources**, choose the buckets you want to scan. Select **Continue**. diff --git a/src/content/docs/cloudflare-one/integrations/cloud-and-saas/findings/index.mdx b/src/content/docs/cloudflare-one/integrations/cloud-and-saas/findings/index.mdx index 81e60cf4679..bb2483f7687 100644 --- a/src/content/docs/cloudflare-one/integrations/cloud-and-saas/findings/index.mdx +++ b/src/content/docs/cloudflare-one/integrations/cloud-and-saas/findings/index.mdx @@ -26,7 +26,7 @@ Posture findings include misconfigurations, unauthorized user activity, and othe To view details about the posture findings that CASB found: -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Cloud & SaaS findings** > **Posture Findings**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Cloud & SaaS findings** > **Posture Findings**. 2. Choose **SaaS** or **Cloud**. 3. To view details about a finding, select the finding's name @@ -49,7 +49,7 @@ Cloudflare CASB labels each finding with one of the following severity levels: You can change the severity level for a finding at any time in case the default assignment does not suit your environment: -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Cloud & SaaS findings** > **Posture Findings**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Cloud & SaaS findings** > **Posture Findings**. 2. Locate the finding you want to modify and select **Manage**. 3. In the severity level drop-down menu, choose your desired setting (_Critical_, _High_, _Medium_, or _Low_). @@ -61,7 +61,7 @@ Content findings include instances of potential data exposure as identified by [ To view details about the content findings that CASB found: -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Cloud & SaaS findings** > **Content Findings**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Cloud & SaaS findings** > **Content Findings**. 2. Choose **SaaS** or **Cloud**. 3. To view details about a finding, select the finding's name. @@ -75,7 +75,7 @@ File findings for some integrations (such as [Microsoft 365](/cloudflare-one/int -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Cloud & SaaS findings** > **Posture Findings**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Cloud & SaaS findings** > **Posture Findings**. 2. Choose **SaaS** or **Cloud**. 3. Locate the individual finding, then select **Manage**. 4. In **Active Instances**, select the file name. @@ -85,7 +85,7 @@ File findings for some integrations (such as [Microsoft 365](/cloudflare-one/int -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Cloud & SaaS findings** > **Content Findings**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Cloud & SaaS findings** > **Content Findings**. 2. Choose **SaaS** or **Cloud**. 3. Select the file name of the detected asset. 4. In **Sharing details**, select the linked file instance. @@ -98,7 +98,7 @@ After reviewing your findings, you may decide that certain posture findings are ### Ignore a finding -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Cloud & SaaS findings** > **Posture Findings**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Cloud & SaaS findings** > **Posture Findings**. 2. Locate the active finding you want to hide. 3. In the three-dot menu, select **Move to ignore**. @@ -106,7 +106,7 @@ The finding's status will change from **Active** to **Ignored**. CASB will conti ### Hide an instance of a finding -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Cloud & SaaS findings** > **Posture Findings**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Cloud & SaaS findings** > **Posture Findings**. 2. Choose the active finding you want to hide, then select **Manage**. 3. In **Active**, find the instance you want to hide. 4. In the three-dot menu, select **Move to hidden**. @@ -119,7 +119,7 @@ After you configure one or more [CASB webhooks](/cloudflare-one/integrations/clo CASB webhooks currently support posture finding instances only. -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Cloud & SaaS findings** > **Posture Findings**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Cloud & SaaS findings** > **Posture Findings**. 2. Choose **SaaS** or **Cloud**. 3. Choose the finding you want to review, then select **Manage**. 4. In **Active Instances**, select an instance. @@ -139,7 +139,7 @@ In addition to detecting and surfacing misconfigurations or issues with SaaS and Before you can remediate findings, [add a new integration](/cloudflare-one/integrations/cloud-and-saas/) and choose _Read-Write mode_ during setup. Alternatively, you can update an existing integration: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Cloud & SaaS findings** > **Integrations**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Cloud & SaaS findings** > **Integrations**. 2. Choose your integration, then select **Configure**. 3. In **Integration permissions**, choose _Read-Write mode_. 4. Select **Update integration**. CASB will redirect you to your Microsoft 365 configuration. @@ -151,7 +151,7 @@ CASB can now remediate supported findings directly. To remediate a supported finding: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Cloud & SaaS findings** > **Posture Findings**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Cloud & SaaS findings** > **Posture Findings**. 2. Choose a supported finding type, then select **Manage**. 3. In **Active Instances**, select an instance. 4. In **Remediation details**, choose a remediation action to take. @@ -196,7 +196,7 @@ Ensure that you have [enabled HTTP filtering](/cloudflare-one/traffic-policies/g To create a Gateway policy directly from a CASB finding: -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Cloud & SaaS findings** > **Posture Findings** or **Cloud & SaaS findings** > **Content Findings**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Cloud & SaaS findings** > **Posture Findings** or **Cloud & SaaS findings** > **Content Findings**. 2. Choose **SaaS** or **Cloud**. 3. Choose the finding you want to modify, then select **Manage**. 4. Find the instance you want to block and select its three-dot menu. diff --git a/src/content/docs/cloudflare-one/integrations/cloud-and-saas/gcp-cloud-storage.mdx b/src/content/docs/cloudflare-one/integrations/cloud-and-saas/gcp-cloud-storage.mdx index 5775f2fec20..8f43dca032d 100644 --- a/src/content/docs/cloudflare-one/integrations/cloud-and-saas/gcp-cloud-storage.mdx +++ b/src/content/docs/cloudflare-one/integrations/cloud-and-saas/gcp-cloud-storage.mdx @@ -44,7 +44,7 @@ You can connect a GCP compute account to your CASB integration to perform [Data To connect a compute account to your GCP integration: -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Integrations** > **Cloud & SaaS integrations**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Integrations** > **Cloud & SaaS integrations**. 2. Find and select your GCP integration. 3. Select **Open connection instructions**. 4. Follow the instructions provided to connect a new compute account. @@ -56,7 +56,7 @@ You can only connect one compute account to an integration. To remove a compute Once your GCP compute account has successfully connected to your CASB integration, you can configure where and how to scan for sensitive data: -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Integrations** > **Cloud & SaaS integrations**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Integrations** > **Cloud & SaaS integrations**. 2. Find and select your GCP integration. 3. Select **Create new configuration**. 4. In **Resources**, choose the buckets you want to scan. Select **Continue**. diff --git a/src/content/docs/cloudflare-one/integrations/cloud-and-saas/troubleshooting/casb.mdx b/src/content/docs/cloudflare-one/integrations/cloud-and-saas/troubleshooting/casb.mdx index 812a1a4c392..ee6ba4910a8 100644 --- a/src/content/docs/cloudflare-one/integrations/cloud-and-saas/troubleshooting/casb.mdx +++ b/src/content/docs/cloudflare-one/integrations/cloud-and-saas/troubleshooting/casb.mdx @@ -51,7 +51,7 @@ CASB integrations do not provide real-time updates. Scans are performed periodic To trigger a new scan: -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Cloud & SaaS findings** > **Integrations**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Cloud & SaaS findings** > **Integrations**. 2. Find your integration and select **Configure**. 3. Turn off **Scan for findings**. 4. After a few minutes, turn on **Scan for findings** again. diff --git a/src/content/docs/cloudflare-one/integrations/cloud-and-saas/troubleshooting/troubleshoot-compute-accounts.mdx b/src/content/docs/cloudflare-one/integrations/cloud-and-saas/troubleshooting/troubleshoot-compute-accounts.mdx index 91f83026123..8a4dee7b55a 100644 --- a/src/content/docs/cloudflare-one/integrations/cloud-and-saas/troubleshooting/troubleshoot-compute-accounts.mdx +++ b/src/content/docs/cloudflare-one/integrations/cloud-and-saas/troubleshooting/troubleshoot-compute-accounts.mdx @@ -20,7 +20,7 @@ Cloudflare CASB detects when compute accounts are unhealthy or outdated. Common To identify unhealthy compute accounts: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Integrations** > **Cloud & SaaS integrations**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Integrations** > **Cloud & SaaS integrations**. 2. Choose the integration you created for cloud scanning. 3. Select **Manage compute accounts**. @@ -38,7 +38,7 @@ Upgrading a compute account applies the latest software features, bug fixes, and To upgrade a compute account: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Integrations** > **Cloud & SaaS integrations**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Integrations** > **Cloud & SaaS integrations**. 2. Choose the integration you created for cloud scanning. 3. Select **Open connection instructions**. 4. Follow the instructions provided to validate your local Terraform and CLI configuration. diff --git a/src/content/docs/cloudflare-one/integrations/cloud-and-saas/troubleshooting/troubleshoot-integrations.mdx b/src/content/docs/cloudflare-one/integrations/cloud-and-saas/troubleshooting/troubleshoot-integrations.mdx index 4896d3775bd..2078cadf7ae 100644 --- a/src/content/docs/cloudflare-one/integrations/cloud-and-saas/troubleshooting/troubleshoot-integrations.mdx +++ b/src/content/docs/cloudflare-one/integrations/cloud-and-saas/troubleshooting/troubleshoot-integrations.mdx @@ -26,7 +26,7 @@ If CASB does not support self-service repairs for an integration, you will need You can repair unhealthy CASB integrations through your list of integrations or findings. -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Integrations** > **Cloud & SaaS integrations**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Integrations** > **Cloud & SaaS integrations**. 2. Choose your unhealthy integration. 3. Select **Reauthorize**. 4. In your SaaS app or cloud environment, reauthorize your account. @@ -35,7 +35,7 @@ You can repair unhealthy CASB integrations through your list of integrations or Upgrading an outdated integration will allow the integration to access new features and permissions. -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Integrations** > **Cloud & SaaS integrations**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Integrations** > **Cloud & SaaS integrations**. 2. Choose your outdated integration. 3. Select **Upgrade integration**. 4. In your SaaS app or cloud environment, upgrade your app and reauthorize your account. diff --git a/src/content/docs/cloudflare-one/integrations/cloud-and-saas/webhooks.mdx b/src/content/docs/cloudflare-one/integrations/cloud-and-saas/webhooks.mdx index 52a7632c560..3ac058be238 100644 --- a/src/content/docs/cloudflare-one/integrations/cloud-and-saas/webhooks.mdx +++ b/src/content/docs/cloudflare-one/integrations/cloud-and-saas/webhooks.mdx @@ -26,7 +26,7 @@ After you configure a webhook destination, you can test delivery from the **Webh ## Create a webhook -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Integrations** > **Webhooks**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Integrations** > **Webhooks**. 2. Select **Create webhook**. 3. Enter a **Name** for the webhook. 4. Enter the **Destination URL** for the system that will receive webhook requests. @@ -59,7 +59,7 @@ Test delivery does not send a live finding instance from your environment. To update an existing webhook: -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Integrations** > **Webhooks**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Integrations** > **Webhooks**. 2. Select the webhook you want to update. 3. Modify the webhook configuration. 4. Select **Save**. @@ -74,7 +74,7 @@ When you edit an existing webhook, Cloudflare does not display saved header valu After you configure one or more webhook destinations, you can send posture finding instances directly from the findings workflow. -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Cloud & SaaS findings** > **Posture Findings**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Cloud & SaaS findings** > **Posture Findings**. 2. Choose **SaaS** or **Cloud**. 3. Choose the finding you want to review, then select **Manage**. 4. Select an instance. diff --git a/src/content/docs/cloudflare-one/integrations/identity-providers/adfs.mdx b/src/content/docs/cloudflare-one/integrations/identity-providers/adfs.mdx index 4573f11f631..ba9d656c1e6 100644 --- a/src/content/docs/cloudflare-one/integrations/identity-providers/adfs.mdx +++ b/src/content/docs/cloudflare-one/integrations/identity-providers/adfs.mdx @@ -179,7 +179,7 @@ Set-ADFSRelyingPartyTrust -TargetName "Name of RPT Display Name" -SamlResponseSi To enable Cloudflare One to accept the claims and assertions sent from AD FS, follow these steps: -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Integrations** > **Identity providers**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Integrations** > **Identity providers**. 2. Under **Your identity providers**, select **Add new identity provider**. diff --git a/src/content/docs/cloudflare-one/integrations/identity-providers/aws-saml.mdx b/src/content/docs/cloudflare-one/integrations/identity-providers/aws-saml.mdx index 64da060efe5..43c3204da71 100644 --- a/src/content/docs/cloudflare-one/integrations/identity-providers/aws-saml.mdx +++ b/src/content/docs/cloudflare-one/integrations/identity-providers/aws-saml.mdx @@ -68,7 +68,7 @@ https://.cloudflareaccess.com/cdn-cgi/access/callback 16. Under **Assign users and groups**, add individuals and/or groups that should be allowed to login to Cloudflare One. -17. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Integrations** > **Identity providers**. +17. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Integrations** > **Identity providers**. 18. Under **Your identity providers**, select **Add new identity provider**. diff --git a/src/content/docs/cloudflare-one/integrations/identity-providers/awscognito-oidc.mdx b/src/content/docs/cloudflare-one/integrations/identity-providers/awscognito-oidc.mdx index 8f561989d8e..600a22651c6 100644 --- a/src/content/docs/cloudflare-one/integrations/identity-providers/awscognito-oidc.mdx +++ b/src/content/docs/cloudflare-one/integrations/identity-providers/awscognito-oidc.mdx @@ -74,7 +74,7 @@ To retrieve those values: ### 2. Add Amazon Cognito as an identity provider -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Integrations** > **Identity providers**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Integrations** > **Identity providers**. 2. Under **Your identity providers**, select **Add new identity provider**. diff --git a/src/content/docs/cloudflare-one/integrations/identity-providers/centrify-saml.mdx b/src/content/docs/cloudflare-one/integrations/identity-providers/centrify-saml.mdx index 119e23f8c79..da62ed20d25 100644 --- a/src/content/docs/cloudflare-one/integrations/identity-providers/centrify-saml.mdx +++ b/src/content/docs/cloudflare-one/integrations/identity-providers/centrify-saml.mdx @@ -68,7 +68,7 @@ Centrify secures access to infrastructure, DevOps, cloud, and other modern enter ### 2. Add Centrify to Cloudflare One -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Integrations** > **Identity providers**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Integrations** > **Identity providers**. 2. Under **Your identity providers**, select **Add new identity provider**. diff --git a/src/content/docs/cloudflare-one/integrations/identity-providers/centrify.mdx b/src/content/docs/cloudflare-one/integrations/identity-providers/centrify.mdx index 57a0c1d0f28..0e2e1c38f61 100644 --- a/src/content/docs/cloudflare-one/integrations/identity-providers/centrify.mdx +++ b/src/content/docs/cloudflare-one/integrations/identity-providers/centrify.mdx @@ -66,7 +66,7 @@ Centrify secures access to infrastructure, DevOps, cloud, and other modern enter ### 2. Add Centrify to Cloudflare One -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Integrations** > **Identity providers**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Integrations** > **Identity providers**. 2. Under **Your identity providers**, select **Add new identity provider**. diff --git a/src/content/docs/cloudflare-one/integrations/identity-providers/citrixadc-saml.mdx b/src/content/docs/cloudflare-one/integrations/identity-providers/citrixadc-saml.mdx index 9e8c4cc55d6..74611abfee8 100644 --- a/src/content/docs/cloudflare-one/integrations/identity-providers/citrixadc-saml.mdx +++ b/src/content/docs/cloudflare-one/integrations/identity-providers/citrixadc-saml.mdx @@ -72,7 +72,7 @@ To set up Citrix ADC (SAML) as your identity provider: bind authentication vserver nsidp -policy samlPol_CloudflareAccess ``` -3. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Integrations** > **Identity providers**. +3. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Integrations** > **Identity providers**. 4. Under **Your identity providers**, select **Add new identity provider**. diff --git a/src/content/docs/cloudflare-one/integrations/identity-providers/entra-id.mdx b/src/content/docs/cloudflare-one/integrations/identity-providers/entra-id.mdx index f0084f1095a..5e38ed23414 100644 --- a/src/content/docs/cloudflare-one/integrations/identity-providers/entra-id.mdx +++ b/src/content/docs/cloudflare-one/integrations/identity-providers/entra-id.mdx @@ -96,7 +96,7 @@ More narrow permissions may be used, however this is the set of permissions that -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Integrations** > **Identity providers**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Integrations** > **Identity providers**. 2. Under **Your identity providers**, select **Add new identity provider**. @@ -168,7 +168,7 @@ To receive an email claim in the `id_token` from Microsoft Entra, you must: 4. If you gave your email claim another name than `email`, you must update your configuration in Cloudflare One: - a. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Integrations** > **Identity providers** > **Azure AD** > **Edit**. + a. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Integrations** > **Identity providers** > **Azure AD** > **Edit**. b. Under **Optional configurations** > **Email claim**, enter the name of the claim representing your organization's email addresses. @@ -232,7 +232,7 @@ To check which users and groups were synchronized, select **Provisioning logs**. -To monitor the exchange of identity details between Cloudflare Access and Microsoft Entra ID, go to [Cloudflare One](https://one.dash.cloudflare.com) > **Insights** > **Logs** > **SCIM provisioning logs** and view the [SCIM activity logs](/cloudflare-one/insights/logs/dashboard-logs/scim-logs/). +To monitor the exchange of identity details between Cloudflare Access and Microsoft Entra ID, go to [Cloudflare One](https://dash.cloudflare.com/one/) > **Insights** > **Logs** > **SCIM provisioning logs** and view the [SCIM activity logs](/cloudflare-one/insights/logs/dashboard-logs/scim-logs/). ### Provisioning attributes diff --git a/src/content/docs/cloudflare-one/integrations/identity-providers/generic-oidc.mdx b/src/content/docs/cloudflare-one/integrations/identity-providers/generic-oidc.mdx index 77706b0dbfe..b1253da9452 100644 --- a/src/content/docs/cloudflare-one/integrations/identity-providers/generic-oidc.mdx +++ b/src/content/docs/cloudflare-one/integrations/identity-providers/generic-oidc.mdx @@ -39,7 +39,7 @@ Cloudflare Access has a generic OpenID Connect (OIDC) connector to help you inte -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Integrations** > **Identity providers**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Integrations** > **Identity providers**. 2. Under **Your identity providers**, select **Add new identity provider**. @@ -151,7 +151,7 @@ All OIDC IdP integrations support the use of custom OIDC claims. Once configured To add a custom OIDC claim to an IdP integration: 1. In your identity provider, ensure that the custom claim is included in your OIDC ID token. -2. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Integrations** > **Identity providers**. +2. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Integrations** > **Identity providers**. 3. Under **Your identity providers**, find your identity provider and select **Edit**. 4. Under **OIDC Claims**, enter the name of your custom claim (for example, `oid`). 5. Select **Save**. diff --git a/src/content/docs/cloudflare-one/integrations/identity-providers/generic-saml.mdx b/src/content/docs/cloudflare-one/integrations/identity-providers/generic-saml.mdx index 30fb3139652..5e7890a7b2a 100644 --- a/src/content/docs/cloudflare-one/integrations/identity-providers/generic-saml.mdx +++ b/src/content/docs/cloudflare-one/integrations/identity-providers/generic-saml.mdx @@ -50,7 +50,7 @@ To download the SAML metadata file, copy-paste the metadata endpoint into a web -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Integrations** > **Identity providers**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Integrations** > **Identity providers**. 2. Select **Add new identity provider** and select **SAML**. 3. Choose a descriptive name for your identity provider. 4. Enter the **Single Sign on URL**, **IdP Entity ID or Issuer URL**, and **Signing certificate** obtained from your identity provider. diff --git a/src/content/docs/cloudflare-one/integrations/identity-providers/github.mdx b/src/content/docs/cloudflare-one/integrations/identity-providers/github.mdx index 0f28debfcbb..8ce154ba02a 100644 --- a/src/content/docs/cloudflare-one/integrations/identity-providers/github.mdx +++ b/src/content/docs/cloudflare-one/integrations/identity-providers/github.mdx @@ -44,7 +44,7 @@ To configure GitHub access in both GitHub and Cloudflare One: 9. Select **Generate a new client secret** and copy the client secret to a safe place. -10. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Integrations** > **Identity providers**. +10. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Integrations** > **Identity providers**. 11. Select **Add new identity provider** and select **GitHub**. @@ -60,7 +60,7 @@ To configure GitHub access in both GitHub and Cloudflare One: 16. Select **Authorize**. -To test that your connection is working, go to [Cloudflare One](https://one.dash.cloudflare.com) > **Integrations** > **Identity providers** and select **Test** next to your GitHub login method. If you have GitHub two-factor authentication enabled, you will need to first login to GitHub directly and return to Access. +To test that your connection is working, go to [Cloudflare One](https://dash.cloudflare.com/one/) > **Integrations** > **Identity providers** and select **Test** next to your GitHub login method. If you have GitHub two-factor authentication enabled, you will need to first login to GitHub directly and return to Access. :::note[Troubleshooting organization policies] diff --git a/src/content/docs/cloudflare-one/integrations/identity-providers/google-workspace.mdx b/src/content/docs/cloudflare-one/integrations/identity-providers/google-workspace.mdx index e6cccbe7a58..14fa509f287 100644 --- a/src/content/docs/cloudflare-one/integrations/identity-providers/google-workspace.mdx +++ b/src/content/docs/cloudflare-one/integrations/identity-providers/google-workspace.mdx @@ -81,7 +81,7 @@ You do not need to be a Google Cloud Platform user to integrate Google Workspace ### 2. Add Google Workspace to Cloudflare One -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Integrations** > **Identity providers**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Integrations** > **Identity providers**. 2. Select **Add new identity provider** and select **Google Workspace**. diff --git a/src/content/docs/cloudflare-one/integrations/identity-providers/google.mdx b/src/content/docs/cloudflare-one/integrations/identity-providers/google.mdx index 434d556dec5..d9bc1f8eee8 100644 --- a/src/content/docs/cloudflare-one/integrations/identity-providers/google.mdx +++ b/src/content/docs/cloudflare-one/integrations/identity-providers/google.mdx @@ -54,7 +54,7 @@ You do not need to be a Google Cloud Platform user to integrate Google as an ide 9. After creating the OAuth client, select the OAuth client that you just created. Google will present the **OAuth Client ID** value and **Client secret** value. The client secret field functions like a password and should not be shared. Copy both the **OAuth Client ID** value and **Client secret** value. -10. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Integrations** > **Identity providers**. +10. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Integrations** > **Identity providers**. 11. Under **Your identity providers**, select **Add new identity provider**. Choose **Google** on the next page. diff --git a/src/content/docs/cloudflare-one/integrations/identity-providers/index.mdx b/src/content/docs/cloudflare-one/integrations/identity-providers/index.mdx index e7f2dcf7d48..f05ee9ecccd 100644 --- a/src/content/docs/cloudflare-one/integrations/identity-providers/index.mdx +++ b/src/content/docs/cloudflare-one/integrations/identity-providers/index.mdx @@ -15,7 +15,7 @@ Cloudflare One integrates with your organization's identity provider to apply Cl As an alternative to configuring an identity provider, Cloudflare One can send a [one-time PIN (OTP)](/cloudflare-one/integrations/identity-providers/one-time-pin/) to approved email addresses. No configuration needed — simply add a user's email address to an [Access policy](/cloudflare-one/access-controls/policies/) and to the group that allows your team to reach the application. You can simultaneously configure an OTP and an identity provider to allow users to use their own authentication method. -Adding an identity provider as a login method requires configuration both in [Cloudflare One](https://one.dash.cloudflare.com) and with the identity provider itself. Consult our IdP-specific documentation to learn more about what you need to set up. +Adding an identity provider as a login method requires configuration both in [Cloudflare One](https://dash.cloudflare.com/one/) and with the identity provider itself. Consult our IdP-specific documentation to learn more about what you need to set up. :::note diff --git a/src/content/docs/cloudflare-one/integrations/identity-providers/jumpcloud-saml.mdx b/src/content/docs/cloudflare-one/integrations/identity-providers/jumpcloud-saml.mdx index 67ce04f6e73..b5ae76ff8bd 100644 --- a/src/content/docs/cloudflare-one/integrations/identity-providers/jumpcloud-saml.mdx +++ b/src/content/docs/cloudflare-one/integrations/identity-providers/jumpcloud-saml.mdx @@ -58,7 +58,7 @@ The following steps are specific to setting up JumpCloud with Cloudflare Access. ### 2. Add JumpCloud to Cloudflare One -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Integrations** > **Identity providers**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Integrations** > **Identity providers**. 2. Under **Your identity providers**, select **Add new identity provider**. diff --git a/src/content/docs/cloudflare-one/integrations/identity-providers/keycloak.mdx b/src/content/docs/cloudflare-one/integrations/identity-providers/keycloak.mdx index 53bb39e8076..68de8491b8a 100644 --- a/src/content/docs/cloudflare-one/integrations/identity-providers/keycloak.mdx +++ b/src/content/docs/cloudflare-one/integrations/identity-providers/keycloak.mdx @@ -45,7 +45,7 @@ To set up Keycloak (SAML) as your identity provider: Next, you will need to integrate with Cloudflare Access. -8. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Integrations** > **Identity providers**. +8. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Integrations** > **Identity providers**. 9. Under **Your identity providers**, select **Add new identity provider**. diff --git a/src/content/docs/cloudflare-one/integrations/identity-providers/linkedin.mdx b/src/content/docs/cloudflare-one/integrations/identity-providers/linkedin.mdx index f6cc71a53b8..b37ace1b0f5 100644 --- a/src/content/docs/cloudflare-one/integrations/identity-providers/linkedin.mdx +++ b/src/content/docs/cloudflare-one/integrations/identity-providers/linkedin.mdx @@ -41,7 +41,7 @@ To configure LinkedIn as an IdP: ![LinkedIn account settings where you will copy the Client ID and Client Secret](~/assets/images/cloudflare-one/identity/linkedin/lin5.png) -10. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Integrations** > **Identity providers**. +10. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Integrations** > **Identity providers**. 11. Under **Your identity providers**, select **Add new identity provider**. @@ -61,7 +61,7 @@ To configure LinkedIn as an IdP: -To test that your connection is working, go to [Cloudflare One](https://one.dash.cloudflare.com/) > **Integrations** > **Identity providers** > select **Test** next to your LinkedIn login method. +To test that your connection is working, go to [Cloudflare One](https://dash.cloudflare.com/one/) > **Integrations** > **Identity providers** > select **Test** next to your LinkedIn login method. ## Example API configuration diff --git a/src/content/docs/cloudflare-one/integrations/identity-providers/okta-saml.mdx b/src/content/docs/cloudflare-one/integrations/identity-providers/okta-saml.mdx index a3e79cacd1e..dc5afbb2099 100644 --- a/src/content/docs/cloudflare-one/integrations/identity-providers/okta-saml.mdx +++ b/src/content/docs/cloudflare-one/integrations/identity-providers/okta-saml.mdx @@ -63,7 +63,7 @@ To set up SAML with Okta as your identity provider: ![Retrieving SAML provider information in Okta](~/assets/images/cloudflare-one/identity/okta-saml/okta-saml-5.png) -13. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Integrations** > **Identity provider**. +13. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Integrations** > **Identity provider**. 14. Under **Your identity providers**, select **Add new identity provider**, and select _SAML_. diff --git a/src/content/docs/cloudflare-one/integrations/identity-providers/one-time-pin.mdx b/src/content/docs/cloudflare-one/integrations/identity-providers/one-time-pin.mdx index 0f427de884d..6dc6840495b 100644 --- a/src/content/docs/cloudflare-one/integrations/identity-providers/one-time-pin.mdx +++ b/src/content/docs/cloudflare-one/integrations/identity-providers/one-time-pin.mdx @@ -22,7 +22,7 @@ For example, if your team uses Okta but you are collaborating with someone outsi -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Integrations** > **Identity providers**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Integrations** > **Identity providers**. 2. Under **Your identity providers**, select **Add new identity provider**. 3. Select **One-time PIN**. diff --git a/src/content/docs/cloudflare-one/integrations/identity-providers/onelogin-oidc.mdx b/src/content/docs/cloudflare-one/integrations/identity-providers/onelogin-oidc.mdx index e531425bb80..0f8c8d5959b 100644 --- a/src/content/docs/cloudflare-one/integrations/identity-providers/onelogin-oidc.mdx +++ b/src/content/docs/cloudflare-one/integrations/identity-providers/onelogin-oidc.mdx @@ -43,7 +43,7 @@ OneLogin provides SSO identity management. Cloudflare Access supports OneLogin a ### 2. Add OneLogin to Cloudflare One -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Integrations** > **Identity providers**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Integrations** > **Identity providers**. 2. Under **Your identity providers**, select **Add new identity provider**. diff --git a/src/content/docs/cloudflare-one/integrations/identity-providers/onelogin-saml.mdx b/src/content/docs/cloudflare-one/integrations/identity-providers/onelogin-saml.mdx index 80e3fb70e79..8a57dcb5680 100644 --- a/src/content/docs/cloudflare-one/integrations/identity-providers/onelogin-saml.mdx +++ b/src/content/docs/cloudflare-one/integrations/identity-providers/onelogin-saml.mdx @@ -56,7 +56,7 @@ OneLogin provides SSO identity management. Cloudflare Access supports OneLogin a ### 2. Add OneLogin to Cloudflare One -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Integrations** > **Identity providers**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Integrations** > **Identity providers**. 2. Under **Your identity providers**, select **Add new identity provider**. diff --git a/src/content/docs/cloudflare-one/integrations/identity-providers/pingfederate-saml.mdx b/src/content/docs/cloudflare-one/integrations/identity-providers/pingfederate-saml.mdx index f24529d2c46..28d9cb46d4e 100644 --- a/src/content/docs/cloudflare-one/integrations/identity-providers/pingfederate-saml.mdx +++ b/src/content/docs/cloudflare-one/integrations/identity-providers/pingfederate-saml.mdx @@ -46,7 +46,7 @@ In versions 9.0 above, you can leave both of these options enabled. This file shares several fields with Cloudflare Access so you do not have to input this data. -11. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Integrations** > **Identity providers**. +11. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Integrations** > **Identity providers**. 12. Under **Your identity providers**, select **Add new identity provider**. diff --git a/src/content/docs/cloudflare-one/integrations/identity-providers/pingone-oidc.mdx b/src/content/docs/cloudflare-one/integrations/identity-providers/pingone-oidc.mdx index 9a29814adc2..62e1257253f 100644 --- a/src/content/docs/cloudflare-one/integrations/identity-providers/pingone-oidc.mdx +++ b/src/content/docs/cloudflare-one/integrations/identity-providers/pingone-oidc.mdx @@ -37,7 +37,7 @@ The PingOne cloud platform from PingIdentity provides SSO identity management. C ### 2. Add PingOne to Cloudflare One -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Integrations** > **Identity providers**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Integrations** > **Identity providers**. 2. Under **Your identity providers**, select **Add new identity provider**. 3. Select **PingOne**. 4. Input the **Client ID**, **Client Secret**, and **Environment ID** generated previously. diff --git a/src/content/docs/cloudflare-one/integrations/identity-providers/pingone-saml.mdx b/src/content/docs/cloudflare-one/integrations/identity-providers/pingone-saml.mdx index 5d0077cdaa6..1280cc26f90 100644 --- a/src/content/docs/cloudflare-one/integrations/identity-providers/pingone-saml.mdx +++ b/src/content/docs/cloudflare-one/integrations/identity-providers/pingone-saml.mdx @@ -53,7 +53,7 @@ The PingOne cloud platform from PingIdentity provides SSO identity management. C ### 2. Add PingOne to Cloudflare One -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Integrations** > **Identity providers**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Integrations** > **Identity providers**. 2. Under **Your identity providers**, select **Add new identity provider**. diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/remote-tunnel-permissions.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/remote-tunnel-permissions.mdx index 4e7b333791b..550cb05295c 100644 --- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/remote-tunnel-permissions.mdx +++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/remote-tunnel-permissions.mdx @@ -22,7 +22,7 @@ To get the token for a remotely-managed tunnel: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Networks** > **Connectors** > **Cloudflare Tunnels**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Networks** > **Connectors** > **Cloudflare Tunnels**. 2. Select a `cloudflared` tunnel and select **Edit**. 3. Copy the `cloudflared` installation command into a text editor (do not run the command). The token is the `eyJ...` string. @@ -67,7 +67,7 @@ To rotate a tunnel token: - 1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Networks** > **Connectors** > **Cloudflare Tunnels**. + 1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Networks** > **Connectors** > **Cloudflare Tunnels**. 2. Select a `cloudflared` tunnel and select **Edit**. 3. Select **Refresh token**. 4. Copy the `cloudflared` installation command for your operating system. This command contains the new token. diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/deployment-guides/terraform.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/deployment-guides/terraform.mdx index 69b25e75df7..f414cc89b53 100644 --- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/deployment-guides/terraform.mdx +++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/deployment-guides/terraform.mdx @@ -93,7 +93,7 @@ Refer to the [Terraform installation guide](https://developer.hashicorp.com/terr -It may take several minutes for the GCP instance and tunnel to come online. You can view your new tunnel, Access application, and Access policy in [Cloudflare One](https://one.dash.cloudflare.com). The new DNS records are available in the [Cloudflare dashboard](/dns/manage-dns-records/how-to/create-dns-records/). +It may take several minutes for the GCP instance and tunnel to come online. You can view your new tunnel, Access application, and Access policy in [Cloudflare One](https://dash.cloudflare.com/one/). The new DNS records are available in the [Cloudflare dashboard](/dns/manage-dns-records/how-to/create-dns-records/). :::note[Remove Terraform resources] diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/tunnel-useful-terms.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/tunnel-useful-terms.mdx index 875e3bd1333..574a5e3fb2e 100644 --- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/tunnel-useful-terms.mdx +++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/tunnel-useful-terms.mdx @@ -32,7 +32,7 @@ A replica is an additional instance of `cloudflared` running the same tunnel on ## Remotely-managed tunnel -A remotely-managed tunnel is a [tunnel](#tunnel) that was created in [Cloudflare One](https://one.dash.cloudflare.com/) under **Networks** > **Tunnels**. Tunnel configuration is stored in Cloudflare, which allows you to manage the tunnel from the dashboard or using the [API](/api/resources/zero_trust/subresources/tunnels/subresources/cloudflared/subresources/configurations/methods/get/). +A remotely-managed tunnel is a [tunnel](#tunnel) that was created in [Cloudflare One](https://dash.cloudflare.com/one/) under **Networks** > **Tunnels**. Tunnel configuration is stored in Cloudflare, which allows you to manage the tunnel from the dashboard or using the [API](/api/resources/zero_trust/subresources/tunnels/subresources/cloudflared/subresources/configurations/methods/get/). ## Locally-managed tunnel diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/logs.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/logs.mdx index fd056e793a9..0d06ba572c8 100644 --- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/logs.mdx +++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/monitor-tunnels/logs.mdx @@ -65,7 +65,7 @@ The `cloudflared` daemon can stream logs from any tunnel in your account to the If you are running multiple `cloudflared` instances for the same tunnel (also known as [replicas](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-availability/)), you must specify an individual instance to stream logs from: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Networks** > **Connectors** > **Cloudflare Tunnels** and select your tunnel. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Networks** > **Connectors** > **Cloudflare Tunnels** and select your tunnel. 2. Find the **Connector ID** for the `cloudflared` instance you want to view. 3. Specify the Connector ID in `cloudflared tail`: ```sh diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/tunnel-virtual-networks.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/tunnel-virtual-networks.mdx index 12dea94ef09..7fa3554991d 100644 --- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/tunnel-virtual-networks.mdx +++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/tunnel-virtual-networks.mdx @@ -55,7 +55,7 @@ In this example, "private network" refers to a distinct environment (such as sta To route overlapping IPs over virtual networks: 1. Create two unique virtual networks: - 1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Networks** > **Routes** > **Virtual networks**. + 1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Networks** > **Routes** > **Virtual networks**. :::note The **Virtual networks** card will only appear if a CIDR route exists in your account. If you do not already have a route, you can navigate to **Virtual networks** using this [direct link](https://dash.cloudflare.com/?to=/:account/one/networks/routes/cidr/vnets). ::: @@ -233,7 +233,7 @@ In this example, "private network" refers to a distinct environment (such as sta To delete a virtual network: - 1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Networks** > **Connectors** > **Cloudflare Tunnels** and ensure that no IP routes are assigned to the virtual network you are trying to delete. If your virtual network is in use, delete the route or reassign it to a different virtual network. + 1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Networks** > **Connectors** > **Cloudflare Tunnels** and ensure that no IP routes are assigned to the virtual network you are trying to delete. If your virtual network is in use, delete the route or reassign it to a different virtual network. 2. Next, go to **Networks** > **Routes**. diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/public-load-balancers.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/public-load-balancers.mdx index a49b25ef89c..6ab01b06b09 100644 --- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/public-load-balancers.mdx +++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/public-load-balancers.mdx @@ -29,7 +29,7 @@ When you add a [published application route](/cloudflare-one/networks/connectors product="cloudflare-one" params={{ publishedAppRouteURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel/#2a-publish-an-application", - tunnelIdLocation: "[Cloudflare One](https://one.dash.cloudflare.com) under **Networks** > **Connectors** > **Cloudflare Tunnels**" + tunnelIdLocation: "[Cloudflare One](https://dash.cloudflare.com/one/) under **Networks** > **Connectors** > **Cloudflare Tunnels**" }} /> diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/rdp/rdp-browser.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/rdp/rdp-browser.mdx index dac2a283af7..99aff08f06d 100644 --- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/rdp/rdp-browser.mdx +++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/rdp/rdp-browser.mdx @@ -211,7 +211,7 @@ When a user attempts a restricted clipboard action, the clipboard content is rep -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Access controls** > **Applications**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Access controls** > **Applications**. 2. Locate your browser-based RDP application and select **Configure**. 3. Select the **Policies** tab. 4. Create a new policy or select an existing policy to edit. diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/ssh/ssh-infrastructure-access.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/ssh/ssh-infrastructure-access.mdx index 2187ee3c105..df0bcc6bbdf 100644 --- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/ssh/ssh-infrastructure-access.mdx +++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/ssh/ssh-infrastructure-access.mdx @@ -142,7 +142,7 @@ To turn off SSH command logging, delete your uploaded public key: -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Traffic policies** > **Traffic settings** > **SSH log encryption public key**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Traffic policies** > **Traffic settings** > **SSH log encryption public key**. 2. Select **Remove**. 3. Select **Remove key** to confirm. @@ -170,7 +170,7 @@ SSH command logs are not visible from the dashboard itself and must be exported To manually retrieve logs: -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Insights** > **Logs**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Insights** > **Logs**. 2. Select **SSH command logs**. 3. Filter the logs using the name of your [SSH application](#5-add-an-infrastructure-application). 4. Select the SSH session for which you want to export command logs. @@ -244,7 +244,7 @@ You will need Cloudflare dashboard access and log view [permissions](/cloudflare ::: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Insights** > **Logs**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Insights** > **Logs**. 2. Select **Access authentication logs**. @@ -272,7 +272,7 @@ If the end user cannot connect to the target, the tunnel you set up in [step 1: To check the status of your tunnel: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Networks** > **Routes**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Networks** > **Routes**. 2. Search your IP to find the tunnel associated with the IP. This IP will be visible in the `warp-cli target list` output in [the previous step](#1-review-access-policies). If you are an admin, you can also go to **Networks** > **Targets** and find the IP next to your Hostname. diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/vnc-browser-rendering.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/vnc-browser-rendering.mdx index cfb07839db7..3a0b278a11d 100644 --- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/vnc-browser-rendering.mdx +++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/vnc-browser-rendering.mdx @@ -208,7 +208,7 @@ Your VNC server is now ready to accept inbound requests from Cloudflare. Create a Cloudflare Access application that users can access through their browser: -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Access controls** > **Applications**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Access controls** > **Applications**. 2. Select **Add an application**. diff --git a/src/content/docs/cloudflare-one/networks/resolvers-and-proxies/dns/dns-over-tls.mdx b/src/content/docs/cloudflare-one/networks/resolvers-and-proxies/dns/dns-over-tls.mdx index 225eb43a07a..882e555f743 100644 --- a/src/content/docs/cloudflare-one/networks/resolvers-and-proxies/dns/dns-over-tls.mdx +++ b/src/content/docs/cloudflare-one/networks/resolvers-and-proxies/dns/dns-over-tls.mdx @@ -21,7 +21,7 @@ Cloudflare supports DoT on standard port `853` over TLS 1.2 and TLS 1.3 in compl Each Gateway DNS location has a unique DoT hostname. DNS locations and corresponding DoT hostnames have policies associated with them. -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Networks** > **Resolvers & Proxies**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Networks** > **Resolvers & Proxies**. 2. Under **DNS locations**, [add a new location](/cloudflare-one/networks/resolvers-and-proxies/dns/locations/) or select an existing location from the list. 3. Under **DoT endpoint**, copy the value in **DoT addresses**. diff --git a/src/content/docs/cloudflare-one/networks/resolvers-and-proxies/dns/locations/dns-resolver-ips.mdx b/src/content/docs/cloudflare-one/networks/resolvers-and-proxies/dns/locations/dns-resolver-ips.mdx index 7480922c589..41ea0b4614e 100644 --- a/src/content/docs/cloudflare-one/networks/resolvers-and-proxies/dns/locations/dns-resolver-ips.mdx +++ b/src/content/docs/cloudflare-one/networks/resolvers-and-proxies/dns/locations/dns-resolver-ips.mdx @@ -14,7 +14,7 @@ When you create a DNS location, Gateway assigns IPv4/IPv6 addresses and DoT/DoH To view the resolver endpoint IP addresses and hostnames for a DNS location: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Networks** > **Resolvers & Proxies**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Networks** > **Resolvers & Proxies**. 2. Select the DNS location, then select **Edit**. 3. Go to **Setup instructions**. The addresses and hostnames will appear in **Your configuration**. diff --git a/src/content/docs/cloudflare-one/networks/resolvers-and-proxies/proxy-endpoints/index.mdx b/src/content/docs/cloudflare-one/networks/resolvers-and-proxies/proxy-endpoints/index.mdx index 42f7dbb85e7..54f86e1fab9 100644 --- a/src/content/docs/cloudflare-one/networks/resolvers-and-proxies/proxy-endpoints/index.mdx +++ b/src/content/docs/cloudflare-one/networks/resolvers-and-proxies/proxy-endpoints/index.mdx @@ -101,7 +101,7 @@ All devices you add to the proxy endpoint can access your Cloudflare Tunnel appl To add an [authorization endpoint](#authorization-endpoint): -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Networks** > **Resolvers & Proxies**, then go to **Proxy endpoints**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Networks** > **Resolvers & Proxies**, then go to **Proxy endpoints**. 2. In **Proxy endpoints**, select **Add an endpoint**. 3. Choose **Add an authorization endpoint**. 4. Name your endpoint. @@ -116,7 +116,7 @@ To add an [authorization endpoint](#authorization-endpoint): To add a [source IP endpoint](#source-ip-endpoint): -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Networks** > **Resolvers & Proxies**, then go to **Proxy endpoints**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Networks** > **Resolvers & Proxies**, then go to **Proxy endpoints**. 2. In **Proxy endpoints**, select **Add an endpoint**. 3. Choose **Add a source IP endpoint**. 4. Name your endpoint. @@ -257,7 +257,7 @@ When you create a PAC file in Cloudflare One, Cloudflare will host it in a publi To create a hosted PAC file: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Networks** > **Resolvers & Proxies**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Networks** > **Resolvers & Proxies**. 2. Select **Proxy endpoints**. 3. [Create a proxy endpoint](#1-create-a-proxy-endpoint) or select an existing one, then select **Edit**. 4. Select **Add PAC files**. @@ -359,7 +359,7 @@ To get the domain of a proxy endpoint: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Networks** > **Resolvers & Proxies** > **Proxy endpoints**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Networks** > **Resolvers & Proxies** > **Proxy endpoints**. 2. Choose the proxy endpoint. Select **Edit**. 3. In **Proxy Endpoint**, copy the domain. @@ -467,7 +467,7 @@ You can modify proxy endpoint settings after creation. ### Edit authorization endpoint -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Networks** > **Resolvers & Proxies** > **Proxy endpoints**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Networks** > **Resolvers & Proxies** > **Proxy endpoints**. 2. Locate your authorization endpoint (indicated by **Authorization** under **Type**). 3. Select the three dots, then select **Configure**. 4. Choose what to edit: @@ -478,7 +478,7 @@ You can modify proxy endpoint settings after creation. ### Edit source IP endpoint -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Networks** > **Resolvers & Proxies** > **Proxy endpoints**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Networks** > **Resolvers & Proxies** > **Proxy endpoints**. 2. Locate your source IP endpoint (indicated by **Source IP** under **Type**). 3. Select the three dots, then select **Configure**. 4. Update the endpoint name or modify the allowed source IP addresses. diff --git a/src/content/docs/cloudflare-one/networks/routes/add-routes.mdx b/src/content/docs/cloudflare-one/networks/routes/add-routes.mdx index 31222a15c6e..ec72991709c 100644 --- a/src/content/docs/cloudflare-one/networks/routes/add-routes.mdx +++ b/src/content/docs/cloudflare-one/networks/routes/add-routes.mdx @@ -24,7 +24,7 @@ Before you add a CIDR route, ensure you have created a Cloudflare Tunnel using [ To add a CIDR route: -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Networks** > **Routes** > **CIDR**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Networks** > **Routes** > **CIDR**. 2. Select **Add CIDR route**. 3. In **CIDR**, enter the IP address or CIDR range that you wish to route through the tunnel (for example, `10.0.0.1` or `10.0.0.0/24`). This can be a private or public IP. 4. For **Tunnel**, select the Cloudflare Tunnel that is being used to connect your private network to Cloudflare. @@ -47,7 +47,7 @@ Before you add a hostname route, ensure you have created a Cloudflare Tunnel usi To add a hostname route: -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Networks** > **Routes** > **Hostname routes**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Networks** > **Routes** > **Hostname routes**. 2. Select **Create hostname route**. 3. In **Hostname**, enter the private or public hostname that represents your application (for example, `wiki.internal.local` or `app.bank.com`). 4. For **Tunnel**, select the Cloudflare Tunnel that is being used to connect your private network to Cloudflare. @@ -67,7 +67,7 @@ Before you publish an application, ensure you have: To add a published application route to an existing tunnel: -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Networks** > **Tunnels**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Networks** > **Tunnels**. 2. Select your tunnel and select **Edit**. diff --git a/src/content/docs/cloudflare-one/remote-browser-isolation/setup/clientless-browser-isolation.mdx b/src/content/docs/cloudflare-one/remote-browser-isolation/setup/clientless-browser-isolation.mdx index c0e775d854e..4feece91b0b 100644 --- a/src/content/docs/cloudflare-one/remote-browser-isolation/setup/clientless-browser-isolation.mdx +++ b/src/content/docs/cloudflare-one/remote-browser-isolation/setup/clientless-browser-isolation.mdx @@ -40,7 +40,7 @@ Your application will now be served in an isolated browser for users matching yo To open links using Browser Isolation: -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Browser isolation** > **Browser isolation settings**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Browser isolation** > **Browser isolation settings**. 2. Turn on **Allow users to open a remote browser without the device client**. 3. In **Launch browser**, enter the URL link, and then select **Launch**. Your URL will open in a secure isolated browser. diff --git a/src/content/docs/cloudflare-one/remote-browser-isolation/setup/index.mdx b/src/content/docs/cloudflare-one/remote-browser-isolation/setup/index.mdx index c45a25eaf8d..6f2e1a0e86d 100644 --- a/src/content/docs/cloudflare-one/remote-browser-isolation/setup/index.mdx +++ b/src/content/docs/cloudflare-one/remote-browser-isolation/setup/index.mdx @@ -29,7 +29,7 @@ Setup instructions vary depending on how you want to connect your devices to Clo To configure Browser Isolation policies: -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Traffic policies** > **Firewall policies** > **HTTP**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Traffic policies** > **Firewall policies** > **HTTP**. 2. Select **Add a policy** and enter a name for the policy. 3. Use the HTTP policy [selectors](/cloudflare-one/traffic-policies/http-policies/#selectors) and [operators](/cloudflare-one/traffic-policies/http-policies/#comparison-operators) to specify the websites or content you want to isolate. 4. For **Action**, choose either [_Isolate_](/cloudflare-one/remote-browser-isolation/isolation-policies/#isolate) or [_Do not Isolate_](/cloudflare-one/remote-browser-isolation/isolation-policies/#do-not-isolate). diff --git a/src/content/docs/cloudflare-one/remote-browser-isolation/setup/non-identity.mdx b/src/content/docs/cloudflare-one/remote-browser-isolation/setup/non-identity.mdx index 81deb161780..ed5fbde19c2 100644 --- a/src/content/docs/cloudflare-one/remote-browser-isolation/setup/non-identity.mdx +++ b/src/content/docs/cloudflare-one/remote-browser-isolation/setup/non-identity.mdx @@ -22,6 +22,6 @@ If you want to apply Isolate policies based on user identity, you will need to e - Configure your browser to forward traffic to a Gateway proxy endpoint with [PAC files](/cloudflare-one/networks/resolvers-and-proxies/proxy-endpoints/) (Proxy Auto-Configuration files that tell the browser which traffic to route through the proxy). - Connect your enterprise site router to Gateway with the [anycast GRE or IPsec tunnel on-ramp to Cloudflare WAN](/cloudflare-wan/zero-trust/cloudflare-gateway/) (site-to-site encrypted tunnels between your network and Cloudflare). 3. Enable non-identity browser isolation: - 1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Browser isolation** > **Browser isolation settings**. + 1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Browser isolation** > **Browser isolation settings**. 2. Turn on **Allow isolated HTTP traffic when user identity is unknown**. 4. Build a non-identity [HTTP policy](/cloudflare-one/remote-browser-isolation/isolation-policies/) to isolate websites in a remote browser. diff --git a/src/content/docs/cloudflare-one/reusable-components/custom-pages/app-launcher-customization.mdx b/src/content/docs/cloudflare-one/reusable-components/custom-pages/app-launcher-customization.mdx index eaf32ed2e52..95a8c36864f 100644 --- a/src/content/docs/cloudflare-one/reusable-components/custom-pages/app-launcher-customization.mdx +++ b/src/content/docs/cloudflare-one/reusable-components/custom-pages/app-launcher-customization.mdx @@ -19,7 +19,7 @@ You can display your own branding, messages, and links to users when they open t To customize the App Launcher appearance: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Reusable components** > **Custom pages**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Reusable components** > **Custom pages**. 2. Find the **App Launcher customization** setting and select **Manage**. 3. Give the App Launcher the look and feel of your organization by adding: - Your organization's name diff --git a/src/content/docs/cloudflare-one/reusable-components/custom-pages/gateway-block-page.mdx b/src/content/docs/cloudflare-one/reusable-components/custom-pages/gateway-block-page.mdx index f0ab810ee25..d3646b61ad8 100644 --- a/src/content/docs/cloudflare-one/reusable-components/custom-pages/gateway-block-page.mdx +++ b/src/content/docs/cloudflare-one/reusable-components/custom-pages/gateway-block-page.mdx @@ -22,7 +22,7 @@ Gateway will display a global block page in the browser of any user whose traffi To configure the global block page: -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Reusable components** > **Custom pages**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Reusable components** > **Custom pages**. 2. Under **Account Gateway block page**, Gateway will display the current block page setting. Select **Manage**. 3. Choose whether to use the [default Gateway block page](#use-the-default-block-page), a [URL redirect](#redirect-to-a-block-page), or a [custom Gateway block page](#customize-the-block-page). 4. Select **Save**. @@ -37,7 +37,7 @@ Instead of displaying the Cloudflare block page, you can configure Gateway to re To redirect users to a non-Cloudflare block page: -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Reusable components** > **Custom pages**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Reusable components** > **Custom pages**. 2. Under **Account Gateway block page**, select **Manage**. 3. Choose **URL redirect**. 4. Enter the URL you want to redirect blocked traffic to. diff --git a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/antivirus.mdx b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/antivirus.mdx index 34a0cb2913a..70ec68178fb 100644 --- a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/antivirus.mdx +++ b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/antivirus.mdx @@ -30,7 +30,7 @@ The Antivirus device posture attribute checks if any antivirus software is insta ## Enable the antivirus check -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Reusable components** > **Posture checks**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Reusable components** > **Posture checks**. 2. Go to **Cloudflare One Client checks** and select **Add a check**. 3. Select **Antivirus**. 4. Enter a descriptive name for the check. diff --git a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/application-check.mdx b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/application-check.mdx index 336b7299a76..b2c7ee05755 100644 --- a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/application-check.mdx +++ b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/application-check.mdx @@ -27,7 +27,7 @@ The Application Check device posture attribute checks that a specific applicatio ## Configure an application check -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Reusable components** > **Posture checks**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Reusable components** > **Posture checks**. 2. Go to **Cloudflare One Client checks** and select **Add a check**. diff --git a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/carbon-black.mdx b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/carbon-black.mdx index 13f0fb62a33..096f6caec4e 100644 --- a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/carbon-black.mdx +++ b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/carbon-black.mdx @@ -28,7 +28,7 @@ Cloudflare One can check if [Carbon Black](https://www.carbonblack.com/) is runn ## Configure the Carbon Black check -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Reusable components** > **Posture checks**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Reusable components** > **Posture checks**. 2. Go to **Cloudflare One Client checks** and select **Add a check**. diff --git a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/client-certificate.mdx b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/client-certificate.mdx index 4b26962b07a..d8489d7c9f1 100644 --- a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/client-certificate.mdx +++ b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/client-certificate.mdx @@ -64,7 +64,7 @@ To generate a sample root CA for testing, refer to [Generate mTLS certificates]( }} /> -2. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Reusable components** > **Posture checks**. +2. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Reusable components** > **Posture checks**. 3. Go to **Cloudflare One Client checks** and select **Add a check**. diff --git a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/corp-device.mdx b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/corp-device.mdx index 5752d33fe0d..1476b8d2366 100644 --- a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/corp-device.mdx +++ b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/corp-device.mdx @@ -29,7 +29,7 @@ Cloudflare One allows you to build Zero Trust rules based on device serial numbe To create rules based on device serial numbers, you first need to create a [Gateway List](/cloudflare-one/reusable-components/lists/) of numbers. -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Reusable components** > **Lists**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Reusable components** > **Lists**. 2. Select **Create manual list** or **Upload CSV**. For larger teams, we recommend uploading a CSV or using Cloudflare's [API endpoint](/api/resources/zero_trust/subresources/gateway/subresources/lists/methods/list/). diff --git a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/device-uuid.mdx b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/device-uuid.mdx index f25641091b6..961013a23f2 100644 --- a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/device-uuid.mdx +++ b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/device-uuid.mdx @@ -37,7 +37,7 @@ You will need to use a [managed deployment tool](/cloudflare-one/team-and-resour To create rules based on device UUIDs, you first need to create a [Gateway List](/cloudflare-one/reusable-components/lists/) of UUIDs. -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Reusable components** > **Lists**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Reusable components** > **Lists**. 2. Select **Create manual list** or **Upload CSV**. For larger teams, we recommend uploading a CSV or using Cloudflare's [API endpoint](/api/resources/zero_trust/subresources/gateway/subresources/lists/methods/list/). @@ -56,7 +56,7 @@ Hyphens are automatically stripped from UUIDs. For example, the posture check wi ## 3. Enable the posture check -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Reusable components** > **Posture checks**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Reusable components** > **Posture checks**. 2. Go to **Cloudflare One Client checks** and select **Add a check**. diff --git a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/disk-encryption.mdx b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/disk-encryption.mdx index 3eca89d2527..62af4798694 100644 --- a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/disk-encryption.mdx +++ b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/disk-encryption.mdx @@ -30,7 +30,7 @@ The Disk Encryption device posture attribute ensures that disks are encrypted on ## Enable the disk encryption check -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Reusable components** > **Posture checks**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Reusable components** > **Posture checks**. 2. Go to **Cloudflare One Client checks** and select **Add a check**. 3. Select **Disk Encryption**. 4. Enter a descriptive name for the check. diff --git a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/domain-joined.mdx b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/domain-joined.mdx index 81e879c5087..7f28057ab54 100644 --- a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/domain-joined.mdx +++ b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/domain-joined.mdx @@ -30,7 +30,7 @@ The Domain Joined device posture attribute ensures that a user is a member of a ## Enable the Domain Joined check -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Reusable components** > **Posture checks**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Reusable components** > **Posture checks**. 2. Go to **Cloudflare One Client checks** and select **Add a check**. 3. Select **Domain Joined**. 4. Enter a descriptive name for the check. diff --git a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/file-check.mdx b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/file-check.mdx index 94992263398..6c696687f54 100644 --- a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/file-check.mdx +++ b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/file-check.mdx @@ -27,7 +27,7 @@ The File Check device posture attribute checks for the presence of a file on a d ## Configure a file check -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Reusable components** > **Posture checks**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Reusable components** > **Posture checks**. 2. Go to **Cloudflare One Client checks** and select **Add a check**. diff --git a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/firewall.mdx b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/firewall.mdx index 8ee799b880d..887eb2b926c 100644 --- a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/firewall.mdx +++ b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/firewall.mdx @@ -30,7 +30,7 @@ The Firewall device posture attribute ensures that a firewall is running on a de ## Enable the firewall check -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Reusable components** > **Posture checks**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Reusable components** > **Posture checks**. 2. Go to **Cloudflare One Client checks** and select **Add a check**. 3. Select **Firewall**. 4. Enter a descriptive name for the check. diff --git a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/os-version.mdx b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/os-version.mdx index 1bdf7b95c4b..291c8c93506 100644 --- a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/os-version.mdx +++ b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/os-version.mdx @@ -27,7 +27,7 @@ The OS Version device posture attribute checks whether the version of a device's ## Enable the OS version check -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Reusable components** > **Posture checks**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Reusable components** > **Posture checks**. 2. Go to **Cloudflare One Client checks** and select **Add a check**. 3. Select **OS version**. 4. Configure the **Operating system**, **Operator**, and **Version** fields to specify the [OS version](#determine-the-os-version) you want devices to match. diff --git a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/require-gateway.mdx b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/require-gateway.mdx index e8ca857adde..b31709cdd69 100644 --- a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/require-gateway.mdx +++ b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/require-gateway.mdx @@ -30,7 +30,7 @@ With Require Gateway, you can allow access to your applications only to devices ## 1. Enable the Gateway check -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Reusable components** > **Posture checks**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Reusable components** > **Posture checks**. 2. Go to **Cloudflare One Client checks** and select **Add a check**. @@ -38,7 +38,7 @@ With Require Gateway, you can allow access to your applications only to devices ## 2. Add the check to an Access application -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Access controls** > **Applications**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Access controls** > **Applications**. 2. Locate the application for which you want to require Gateway. Select **Configure**. diff --git a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/require-warp.mdx b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/require-warp.mdx index cabee98ae82..f016b2daf8f 100644 --- a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/require-warp.mdx +++ b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/require-warp.mdx @@ -36,7 +36,7 @@ Cloudflare One enables you to restrict access to your applications to devices ru ## 1. Enable the WARP check -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Traffic policies** > **Traffic settings**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Traffic policies** > **Traffic settings**. 2. Ensure that *Allow Secure Web Gateway to proxy traffic** is enabled. 3. Go to **Reusable components** > **Posture checks**. 4. In **Cloudflare One Client checks**, select **Add a check**. @@ -44,7 +44,7 @@ Cloudflare One enables you to restrict access to your applications to devices ru ## 2. Add the check to an Access policy -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Access controls** > **Applications**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Access controls** > **Applications**. 2. Locate the application for which you want to require WARP. Select **Configure**. diff --git a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/sentinel-one.mdx b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/sentinel-one.mdx index 9ce377f4b5b..4aac14bf3b2 100644 --- a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/sentinel-one.mdx +++ b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/sentinel-one.mdx @@ -32,7 +32,7 @@ Cloudflare One can check if [SentinelOne](https://www.sentinelone.com/) is runni ## Configure the SentinelOne check -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Reusable components** > **Posture checks**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Reusable components** > **Posture checks**. 2. Go to **Cloudflare One Client checks** and select **Add a check**. diff --git a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/tanium.mdx b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/tanium.mdx index 5174c88f1f2..b9d81455c93 100644 --- a/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/tanium.mdx +++ b/src/content/docs/cloudflare-one/reusable-components/posture-checks/client-checks/tanium.mdx @@ -47,7 +47,7 @@ The integration does not currently support Safari. 1. Configure your Tanium deployment using the [step-by-step documentation](https://docs.tanium.com/endpoint_identity/endpoint_identity/userguide.html) provided. You will need the public key to integrate your Tanium deployment with Cloudflare Access. -2. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Reusable components** > **Posture checks**. +2. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Reusable components** > **Posture checks**. 3. Go to **Cloudflare One Client checks** and select **Add a check**. diff --git a/src/content/docs/cloudflare-one/reusable-components/posture-checks/index.mdx b/src/content/docs/cloudflare-one/reusable-components/posture-checks/index.mdx index f3d7ad2bd83..5f55f82298e 100644 --- a/src/content/docs/cloudflare-one/reusable-components/posture-checks/index.mdx +++ b/src/content/docs/cloudflare-one/reusable-components/posture-checks/index.mdx @@ -26,7 +26,7 @@ Setup instructions and requirements vary depending on the device posture attribu Before integrating a device posture check in a Gateway or Access policy, verify that the Pass/Fail results match your expectations. To view the latest test results for a specific device: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Team & Resources** > **Devices**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Team & Resources** > **Devices**. 2. Select the device. 3. Select **View details**. 4. Select the **Posture checks** tab. diff --git a/src/content/docs/cloudflare-one/setup/index.mdx b/src/content/docs/cloudflare-one/setup/index.mdx index e781c09dd87..802b5b24900 100644 --- a/src/content/docs/cloudflare-one/setup/index.mdx +++ b/src/content/docs/cloudflare-one/setup/index.mdx @@ -26,7 +26,7 @@ Sign up for a [Cloudflare account](https://dash.cloudflare.com/sign-up) and enab ## What would you like to do? -These use cases match the guided onboarding in the [Cloudflare One dashboard](https://one.dash.cloudflare.com). To follow along in the dashboard, select **Get Started**. +These use cases match the guided onboarding in the [Cloudflare One dashboard](https://dash.cloudflare.com/one/). To follow along in the dashboard, select **Get Started**. diff --git a/src/content/docs/cloudflare-one/setup/replace-vpn/device-to-network.mdx b/src/content/docs/cloudflare-one/setup/replace-vpn/device-to-network.mdx index fd94785b410..1c6261ab476 100644 --- a/src/content/docs/cloudflare-one/setup/replace-vpn/device-to-network.mdx +++ b/src/content/docs/cloudflare-one/setup/replace-vpn/device-to-network.mdx @@ -17,7 +17,7 @@ Connect a remote device to a private network so your users can securely access i To explore other connection scenarios, refer to [Replace your VPN](/cloudflare-one/setup/replace-vpn/). -This guide follows the same steps as the **Get Started** onboarding wizard in the [Cloudflare One dashboard](https://one.dash.cloudflare.com). +This guide follows the same steps as the **Get Started** onboarding wizard in the [Cloudflare One dashboard](https://dash.cloudflare.com/one/). ## How it works @@ -35,7 +35,7 @@ The [Cloudflare One Client](/cloud Cloudflare Tunnel establishes an outbound connection between your resources and Cloudflare. This is how new devices can reach your private network. You can install Tunnel on any Windows, Mac, or Linux device currently in your private network. -1. In [Cloudflare One](https://one.dash.cloudflare.com), select the **Get Started** tab. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), select the **Get Started** tab. 2. For **Replace my client-based or site-to-site VPN**, select **Get started**. 3. For **Device to network**, select **Continue**. 4. On the **Connect a remote device to a private network** screen, select **Continue**. @@ -104,7 +104,7 @@ After verifying your connection, consider securing your private network with pol - **Set up Gateway policies**: By default, all enrolled devices can reach your entire private network. Gateway policies let you scan, filter, and log traffic between your devices and your private network. For more information, refer to [DNS policies](/cloudflare-one/traffic-policies/dns-policies/), [Network policies](/cloudflare-one/traffic-policies/network-policies/), and [HTTP policies](/cloudflare-one/traffic-policies/http-policies/). - **Create an Access application**: Restrict access to specific applications or hostnames on your private network with identity-based rules. For more information, refer to [Secure a private IP or hostname](/cloudflare-one/access-controls/applications/non-http/self-hosted-private-app/). -- **Explore more with Zero Trust**: Review your tunnel, policies, and connected devices in the [Cloudflare One dashboard](https://one.dash.cloudflare.com). +- **Explore more with Zero Trust**: Review your tunnel, policies, and connected devices in the [Cloudflare One dashboard](https://dash.cloudflare.com/one/). For in-depth guidance on policy design and device posture checks, refer to the [Replace your VPN learning path](/learning-paths/replace-vpn/concepts/). diff --git a/src/content/docs/cloudflare-one/setup/secure-private-apps/clientless-ssh.mdx b/src/content/docs/cloudflare-one/setup/secure-private-apps/clientless-ssh.mdx index 5fda8fec1cd..f7eff2cf97d 100644 --- a/src/content/docs/cloudflare-one/setup/secure-private-apps/clientless-ssh.mdx +++ b/src/content/docs/cloudflare-one/setup/secure-private-apps/clientless-ssh.mdx @@ -17,7 +17,7 @@ Provide secure, in-browser command line access to an internal server without SSH To explore other access scenarios, refer to [Secure private apps](/cloudflare-one/setup/secure-private-apps/). -This guide follows the same steps as the **Get Started** experience in the [Cloudflare One dashboard](https://one.dash.cloudflare.com). +This guide follows the same steps as the **Get Started** experience in the [Cloudflare One dashboard](https://dash.cloudflare.com/one/). ## How it works @@ -38,7 +38,7 @@ For details on connection methods and advanced configuration, refer to [Connect In this step, you describe the internal server you want to make available through Cloudflare. -1. In [Cloudflare One](https://one.dash.cloudflare.com), select the **Get Started** tab. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), select the **Get Started** tab. 2. For **Set up secure access to private apps from any browser**, select **Get started**. 3. For **Configure clientless SSH access to an internal service**, select **Continue**. 4. On the **Zero Trust SSH terminal directly from your browser** screen, select **Continue**. diff --git a/src/content/docs/cloudflare-one/setup/secure-private-apps/in-browser-rdp.mdx b/src/content/docs/cloudflare-one/setup/secure-private-apps/in-browser-rdp.mdx index 6b3c59e897f..9d0c55c3b92 100644 --- a/src/content/docs/cloudflare-one/setup/secure-private-apps/in-browser-rdp.mdx +++ b/src/content/docs/cloudflare-one/setup/secure-private-apps/in-browser-rdp.mdx @@ -18,7 +18,7 @@ Provide secure, in-browser remote desktop access to Windows hosts without Remote To explore other access scenarios, refer to [Secure private apps](/cloudflare-one/setup/secure-private-apps/). -This guide follows the same steps as the **Get Started** experience in the [Cloudflare One dashboard](https://one.dash.cloudflare.com). +This guide follows the same steps as the **Get Started** experience in the [Cloudflare One dashboard](https://dash.cloudflare.com/one/). ## How it works @@ -39,7 +39,7 @@ For details on supported operating systems, connection methods, and known limita In this step, you describe the Windows host you want to make available through Cloudflare. -1. In [Cloudflare One](https://one.dash.cloudflare.com), select the **Get Started** tab. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), select the **Get Started** tab. 2. For **Set up secure access to private apps from any browser**, select **Get started**. 3. For **Enable in-browser remote desktop sessions to Windows hosts**, select **Continue**. 4. On the **Zero Trust RDP client directly from your browser** screen, select **Continue**. diff --git a/src/content/docs/cloudflare-one/setup/secure-private-apps/private-web-app.mdx b/src/content/docs/cloudflare-one/setup/secure-private-apps/private-web-app.mdx index b764ff1e34a..2d55aa049d7 100644 --- a/src/content/docs/cloudflare-one/setup/secure-private-apps/private-web-app.mdx +++ b/src/content/docs/cloudflare-one/setup/secure-private-apps/private-web-app.mdx @@ -17,7 +17,7 @@ Connect a self-hosted web application to Cloudflare so authorized users can acce To explore other access scenarios, refer to [Secure private apps](/cloudflare-one/setup/secure-private-apps/). -This guide follows the same steps as the **Get Started** experience in the [Cloudflare One dashboard](https://one.dash.cloudflare.com). +This guide follows the same steps as the **Get Started** experience in the [Cloudflare One dashboard](https://dash.cloudflare.com/one/). ## How it works @@ -36,7 +36,7 @@ This guide follows the same steps as the **Get Started** experience in the [Clou In this step, you describe the internal application you want to make available through Cloudflare. -1. In [Cloudflare One](https://one.dash.cloudflare.com), select the **Get Started** tab. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), select the **Get Started** tab. 2. For **Set up secure access to private apps from any browser**, select **Get started**. 3. For **Connect a private web application**, select **Continue**. 4. On the **Connect and access private web applications** screen, select **Continue**. diff --git a/src/content/docs/cloudflare-one/team-and-resources/app-library.mdx b/src/content/docs/cloudflare-one/team-and-resources/app-library.mdx index 76e36e384bd..b1c239dc9ff 100644 --- a/src/content/docs/cloudflare-one/team-and-resources/app-library.mdx +++ b/src/content/docs/cloudflare-one/team-and-resources/app-library.mdx @@ -14,7 +14,7 @@ import { Render, GlossaryTooltip } from "~/components"; The Application Library allows users to manage their SaaS applications in Cloudflare One by consolidating views across all relevant products: [Gateway](/cloudflare-one/traffic-policies/), [Access](/cloudflare-one/access-controls/policies/), and [Cloud Access Security Broker (CASB)](/cloudflare-one/integrations/cloud-and-saas/). The App Library provides visibility and control for available applications, as well as the ability to view categorized hostnames and manage configuration for Access for SaaS and Gateway policies. For example, you can use the App Library to review how Gateway uses specific hostnames to match against application traffic. -To access the App Library in [Cloudflare One](https://one.dash.cloudflare.com/), go to **Team & Resources** > **Application library**. Each application card will list the number of hostnames associated with the application, the supported Cloudflare One product usage, and the [app type](/cloudflare-one/traffic-policies/application-app-types/#app-types). +To access the App Library in [Cloudflare One](https://dash.cloudflare.com/one/), go to **Team & Resources** > **Application library**. Each application card will list the number of hostnames associated with the application, the supported Cloudflare One product usage, and the [app type](/cloudflare-one/traffic-policies/application-app-types/#app-types). The App Library groups [Do Not Inspect applications](/cloudflare-one/traffic-policies/application-app-types/#do-not-inspect-applications) within the corresponding application. For example, the App Library will group _Google Drive (Do Not Inspect)_ under **Google Drive**. Traffic that does not match a known application will not be included in the App Library. @@ -45,7 +45,7 @@ The **Policies** tab shows any [Gateway](/cloudflare-one/traffic-policies/) and The **Usage** tab shows any logs for [Gateway traffic requests](/cloudflare-one/insights/logs/dashboard-logs/gateway-logs/), [Access authentication events](/cloudflare-one/insights/logs/dashboard-logs/access-authentication-logs/#authentication-logs), [Shadow IT Discovery user sessions](/cloudflare-one/insights/analytics/shadow-it-discovery/), and [generative AI prompt logs](/cloudflare-one/data-loss-prevention/dlp-policies/logging-options/#view-prompt-logs) sent to the selected application. This section requires logs to be turned on for each feature. -The Shadow IT Discovery dashboard will provide more details for discovered applications. To access Shadow IT Discovery in [Cloudflare One](https://one.dash.cloudflare.com/), go to **Insights** > **Dashboards**, then select **Shadow IT: SaaS analytics** or **Shadow IT: Private Network analytics**. +The Shadow IT Discovery dashboard will provide more details for discovered applications. To access Shadow IT Discovery in [Cloudflare One](https://dash.cloudflare.com/one/), go to **Insights** > **Dashboards**, then select **Shadow IT: SaaS analytics** or **Shadow IT: Private Network analytics**. ## Review applications @@ -61,7 +61,7 @@ The scoring system evaluates applications across multiple security, compliance, To view an application's confidence scorecard: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Team & Resources** > **Application library** +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Team & Resources** > **Application library** 2. Find the application you would like to review or search it by name. 3. Review the Application Posture Score and the Generative AI Posture Score which are generated on the application card. diff --git a/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/client-sessions.mdx b/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/client-sessions.mdx index d1a2f29657d..dbb3b51ba33 100644 --- a/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/client-sessions.mdx +++ b/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/client-sessions.mdx @@ -35,7 +35,7 @@ You can allow users to log in to Access applications using their device client s To configure device client sessions for Access applications: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Team & Resources** > **Devices** > **Management**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Team & Resources** > **Devices** > **Management**. 2. In **Device enrollment permissions**, select **Manage**. 3. Go to the **Login methods** tab and enable **Device authentication identity**. 4. Under **Session duration**, choose a session timeout value. This timeout will apply to all Access applications that have **Device authentication identity** enabled. diff --git a/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/device-ips.mdx b/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/device-ips.mdx index 95985509686..6ad0723dac1 100644 --- a/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/device-ips.mdx +++ b/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/device-ips.mdx @@ -57,7 +57,7 @@ Create a custom IP subnet when the [default IPv4 range](#default-device-ips) con To define a custom IPv4 subnet for device IPs: -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Team & Resources** > **Devices** > **Device profiles**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Team & Resources** > **Devices** > **Device profiles**. 2. Under **Device IP subnets**, select **Add new IP subnet**. 3. Enter any name for the subnet. 4. In **CIDR**, enter a valid IPv4 CIDR block from the supported private ranges: @@ -88,7 +88,7 @@ Assign [custom IP subnets](#create-an-ip-subnet) to ensure devices are provision To assign IP subnets to your devices: -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Team & Resources** > **Devices** > **Device profiles**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Team & Resources** > **Devices** > **Device profiles**. 2. Under **Device IP profiles**, select **Add new IP profile**. 3. Enter a name for this group of devices (for example, `IT department`). 4. Create rules to define the users or devices that will receive these IPs. Learn more about the available [Selectors](#selectors), [Operators](#comparison-operators), and [Values](#value). @@ -202,7 +202,7 @@ The Cloudflare One Client checks the IP profiles from top to bottom as they appe To check the virtual IP addresses assigned to a specific device registration: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Team & Resources** > **Devices**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Team & Resources** > **Devices**. 2. Select your device > **View details**. :::tip[Device filters] The Cloudflare One dashboard defaults to showing devices that were last seen within the past year. You can select **Show filters** to change the date range or filter by the last active user. @@ -221,7 +221,7 @@ Monitor the consumption of your IPv4 subnets to ensure you have enough addresses Use the Cloudflare One dashboard to view a high-level overview of assigned and available IPs: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Team & Resources** > **Devices** > **Device profiles**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Team & Resources** > **Devices** > **Device profiles**. 2. Locate the **Device IP subnets** table. 3. The **IPs assigned** column displays the total number of IPs currently assigned to active device registrations versus the total capacity of the CIDR block. @@ -347,7 +347,7 @@ To get a list of all device registrations in a subnet (including revoked registr Cloudflare does not support editing an existing IPv4 subnet definition. To assign a different IPv4 subnet to your devices: -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Team & Resources** > **Devices** > **Device profiles**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Team & Resources** > **Devices** > **Device profiles**. 2. Under **Device IP profiles**, find the device group associated with the old subnet and select **Edit**. 3. Select **Create new subnet IP range** to define a new subnet. 4. Select **Save**. diff --git a/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/device-profiles.mdx b/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/device-profiles.mdx index d4fa7a3a464..2f76a66201b 100644 --- a/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/device-profiles.mdx +++ b/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/device-profiles.mdx @@ -18,7 +18,7 @@ import { Render, TabItem, Tabs, APIRequest } from "~/components"; -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Team & Resources** > **Devices** > **Device profiles** > **General profiles**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Team & Resources** > **Devices** > **Device profiles** > **General profiles**. 2. Select **Create new profile**. This will make a copy of the **Default** profile. 3. Enter any name for the profile. 4. Create rules to define the devices that will use this profile. Learn more about the available [Selectors](#selectors), [Operators](/cloudflare-one/traffic-policies/network-policies/#comparison-operators), and [Values](/cloudflare-one/traffic-policies/network-policies/#value). @@ -114,13 +114,13 @@ Send a `POST` request to the [Devices API](/api/resources/zero_trust/subresource To verify the last active device profile for a specific device: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Team & Resources** > **Devices**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Team & Resources** > **Devices**. 2. Under devices, find your device. 3. Review the device profile under **Last active device profile**. To verify the last active device profile for a user's devices: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Team & Resources** > **Users**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Team & Resources** > **Users**. 2. Under **User name**, find the user you would like to investigate. 3. Select **Devices** to see all devices used by the user. 4. Find the device you want to investigate and verify the last active device profile for that device under the **Device profile** column. diff --git a/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/managed-networks.mdx b/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/managed-networks.mdx index 6bf4919ad8b..33ad4b6868c 100644 --- a/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/managed-networks.mdx +++ b/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/managed-networks.mdx @@ -198,7 +198,7 @@ The SHA-256 fingerprint is only required if your TLS endpoint uses a self-signed -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Team & Resources** > **Devices** > **Device profiles**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Team & Resources** > **Devices** > **Device profiles**. 2. Select **Managed networks** and select **Add new managed network**. 3. Name your network location. 4. In **Host and Port**, enter the private IP address and port number of your [TLS endpoint](#create-a-new-tls-endpoint) (for example, `192.168.185.198:3333`). @@ -243,7 +243,7 @@ If a device profile uses [Split Tunnels](/cloudflare-one/team-and-resources/devi -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Team & Resources** > **Devices** > **Device profiles** > **General profiles**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Team & Resources** > **Devices** > **Device profiles** > **General profiles**. 2. Create a [new profile](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/device-profiles/) or edit an existing profile. diff --git a/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/device-information-only.mdx b/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/device-information-only.mdx index fae390f1f91..b39001360b8 100644 --- a/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/device-information-only.mdx +++ b/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/device-information-only.mdx @@ -42,7 +42,7 @@ Using the API, enable client certificate provisioning for [your zone](/fundament ## 2. Configure the Cloudflare One Client -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Team & Resources** > **Devices** > **Device profiles** > **General profiles**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Team & Resources** > **Devices** > **Device profiles** > **General profiles**. 2. Choose a [device profile](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/device-profiles/) and select **Edit**. diff --git a/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/index.mdx b/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/index.mdx index df643575fad..be9fbd662ff 100644 --- a/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/index.mdx +++ b/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/index.mdx @@ -69,7 +69,7 @@ The default profile is used for all devices that are not assigned to a specific To set up Local proxy mode: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Teams & Resources** > **Device profiles**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Teams & Resources** > **Device profiles**. 2. Decide whether you would like to edit the default profile or create a new device profile. 3. Select the device profile you want to configure > **Edit** (If you only see **View**, you lack the permissions required to modify profiles). 4. Ensure the **Device tunnel protocol** is set to `MASQUE`. diff --git a/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/local-domains.mdx b/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/local-domains.mdx index 70ea3624f50..c005b3916e3 100644 --- a/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/local-domains.mdx +++ b/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/local-domains.mdx @@ -46,7 +46,7 @@ Local Domain Fallback configuration only impacts where DNS requests get resolved To view the fallback domains applied to a device, you can: -- In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Team & Resources** > **Devices** > find the target device and the **Last active device profile** > follow the [steps above](#view-domains). +- In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Team & Resources** > **Devices** > find the target device and the **Last active device profile** > follow the [steps above](#view-domains). - (Desktop only) Run `warp-cli settings` in the terminal of the target device and review the [fallback domains](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/troubleshooting/troubleshooting-guide/#fallback-domains) section of the output. - (Desktop only) Collect [client diagnostic logs](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/troubleshooting/diagnostic-logs/) for the device and review the [fallback domain](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/troubleshooting/troubleshooting-guide/#fallback-domains) section in `warp_settings.txt`. diff --git a/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels.mdx b/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels.mdx index 38655698ad4..3170dee716e 100644 --- a/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels.mdx +++ b/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels.mdx @@ -105,7 +105,7 @@ Due to platform differences, mobile clients can only apply Split Tunnels rules w Removing default Split Tunnel entries may cause users to lose Internet connectivity or block their access to local resources. ::: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Team & Resources** > **Devices** > **Device profiles** > **General profiles**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Team & Resources** > **Devices** > **Device profiles** > **General profiles**. 2. Locate the [device profile](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/device-profiles/) you would like to modify and select **Edit**. 3. Under **Split Tunnels**, select **Manage**. 4. Find the IP address or hostname in the list and select the **Action** button. From the dropdown, select _Delete_. diff --git a/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/settings/external-disconnect.mdx b/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/settings/external-disconnect.mdx index 370f4911c8a..8a10eefdce4 100644 --- a/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/settings/external-disconnect.mdx +++ b/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/settings/external-disconnect.mdx @@ -141,7 +141,7 @@ The following example demonstrates how to deploy an external disconnect endpoint To configure External Emergency Disconnect using the dashboard: -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Team & Resources** > **Devices** > **Management**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Team & Resources** > **Devices** > **Management**. 2. Select **Global disconnection settings**. 3. Find **Manage device connection using an external signal** and select **Edit**. 4. Configure the following fields: @@ -232,7 +232,7 @@ If the external endpoint becomes unavailable or serves an invalid configuration, -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Team & Resources** > **Devices** > **Management**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Team & Resources** > **Devices** > **Management**. 2. Select **Global disconnection settings**. 3. Turn off **Manage device connection using an external signal**. diff --git a/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/mdm-deployment/partners/intune.mdx b/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/mdm-deployment/partners/intune.mdx index 54f77b794e2..b478520541a 100644 --- a/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/mdm-deployment/partners/intune.mdx +++ b/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/mdm-deployment/partners/intune.mdx @@ -324,7 +324,7 @@ By completing this step, you preconfigure the Cloudflare One Client with your te Complete Step 4 at least one hour after steps 1, 2, and 3 so clients have enough time to check in and update their device configurations. ::: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), [download the Cloudflare One Client](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/download/#macos) in `.pkg` format. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), [download the Cloudflare One Client](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/download/#macos) in `.pkg` format. :::note[Repeat this step to update the Cloudflare One Client when a new release is available] Every time a new Cloudflare One Client version is released, you must repeat this process and get a new `.pkg` file for the new version. @@ -459,7 +459,7 @@ Per-app VPN is supported on Cloudflare One Agent version `1.8` or greater for iO Before proceeding with per-app VPN configuration, you must make sure [Auto connect](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/settings/#auto-connect) is disabled in Zero Trust. To disable Auto connect: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Team & Resources** > **Devices** > **Device profiles** > **General profiles**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Team & Resources** > **Devices** > **Device profiles** > **General profiles**. 2. Select your device profile and select **Edit**. 3. Turn off **Auto Connect**. diff --git a/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/mdm-deployment/partners/jamf.mdx b/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/mdm-deployment/partners/jamf.mdx index ae67092ef1e..8ca89d3ceb5 100644 --- a/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/mdm-deployment/partners/jamf.mdx +++ b/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/mdm-deployment/partners/jamf.mdx @@ -56,7 +56,7 @@ Every time a new Cloudflare One Client version is released, you must repeat this 1. [Create a `plist` file](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/mdm-deployment/#plist-file) with your desired deployment parameters. 2. Upload your `plist` file to Jamf and select **Save**. 6. (Recommended) Advanced security features require deploying a [user-side certificate](/cloudflare-one/team-and-resources/devices/user-side-certificates/) so that devices can establish trust with Cloudflare when their traffic is inspected. To deploy a user-side certificate using Jamf: - 1. In [Cloudflare One](https://one.dash.cloudflare.com/), [generate and activate](/cloudflare-one/team-and-resources/devices/user-side-certificates/#generate-a-cloudflare-root-certificate) a Cloudflare root certificate. + 1. In [Cloudflare One](https://dash.cloudflare.com/one/), [generate and activate](/cloudflare-one/team-and-resources/devices/user-side-certificates/#generate-a-cloudflare-root-certificate) a Cloudflare root certificate. 2. [Download the Cloudflare root certificate](/cloudflare-one/team-and-resources/devices/user-side-certificates/manual-deployment/#download-a-cloudflare-root-certificate) in `.pem` format. 3. [Convert](/cloudflare-one/team-and-resources/devices/user-side-certificates/manual-deployment/#convert-the-certificate) the certificate to `.cer` format. 4. In your Jamf configuration profile, scroll down the **Options** list and select **Certificate** > **Configure**. @@ -99,7 +99,7 @@ Per-app VPN is supported on Cloudflare One Agent version `1.8` or greater for iO Before proceeding with per-app VPN configuration, you must make sure [Auto connect](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/settings/#auto-connect) is disabled in Zero Trust. To disable Auto connect: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Team & Resources** > **Devices** > **Device profiles** > **General profiles**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Team & Resources** > **Devices** > **Device profiles** > **General profiles**. 2. Select your device profile and select **Edit**. 3. Turn off **Auto Connect**. diff --git a/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/set-up.mdx b/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/set-up.mdx index 259dbd933fc..a4804180128 100644 --- a/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/set-up.mdx +++ b/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/set-up.mdx @@ -28,7 +28,7 @@ This mode enables the complete suite of [device security features](/cloudflare-o ### 1. Create a Cloudflare Zero Trust account. -The [Cloudflare Zero Trust home](https://one.dash.cloudflare.com/) will be your go-to place to check device connectivity data, as well as create Secure Web Gateway and Zero Trust policies for your organization. +The [Cloudflare Zero Trust home](https://dash.cloudflare.com/one/) will be your go-to place to check device connectivity data, as well as create Secure Web Gateway and Zero Trust policies for your organization. As you complete the [Cloudflare Zero Trust onboarding](/cloudflare-one/setup/), you will be asked to create a team name for your organization. You will need the team name when you deploy the Cloudflare One Client on your devices; it will allow your users to connect to your organization's Cloudflare Zero Trust instance. diff --git a/src/content/docs/cloudflare-one/team-and-resources/devices/device-registration.mdx b/src/content/docs/cloudflare-one/team-and-resources/devices/device-registration.mdx index 13c9f6a1309..b279677301b 100644 --- a/src/content/docs/cloudflare-one/team-and-resources/devices/device-registration.mdx +++ b/src/content/docs/cloudflare-one/team-and-resources/devices/device-registration.mdx @@ -34,13 +34,13 @@ A single physical device can have [multiple device registrations](/cloudflare-on To review how many device registrations are associated with a device: -1. Log into [Cloudflare One](https://one.dash.cloudflare.com/) and go to **Teams & Resources** > **Devices**. +1. Log into [Cloudflare One](https://dash.cloudflare.com/one/) and go to **Teams & Resources** > **Devices**. 2. Select a device and select **View details**. 3. Scroll down to **Users** and review users who enrolled on this device. To review a device registration's status: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Teams & Resources** > **Devices**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Teams & Resources** > **Devices**. 2. Select the device and select **View details**. 3. Scroll down to **Users** and find the user associated with the device. 4. Review the status (such as `Active` or `Revoked`) of the device registration under **Status**. @@ -125,7 +125,7 @@ Devices can have multiple device registrations. Deleting one registration does n To delete a device registration: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Teams & Resources** > **Devices**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Teams & Resources** > **Devices**. 2. Select the device > **View details**. 3. Go to **Users** and mark the checkbox next to the device registration you want to delete. 4. Select **Action** > _Delete access_. @@ -169,7 +169,7 @@ If a user re-authenticates while the device registration is revoked, a new devic ::: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Teams & Resources** > **Devices**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Teams & Resources** > **Devices**. 2. Select the device and select **View details**. 3. To revoke access, select **Revoke access**. This revokes access for all associated registrations on the device. 4. To unrevoke access, scroll down to the **Users** section and select one or more users using the checkbox. Select **Actions** > **Unrevoke access**. diff --git a/src/content/docs/cloudflare-one/team-and-resources/devices/user-side-certificates/automated-deployment.mdx b/src/content/docs/cloudflare-one/team-and-resources/devices/user-side-certificates/automated-deployment.mdx index 3611d43b722..575d8cd558f 100644 --- a/src/content/docs/cloudflare-one/team-and-resources/devices/user-side-certificates/automated-deployment.mdx +++ b/src/content/docs/cloudflare-one/team-and-resources/devices/user-side-certificates/automated-deployment.mdx @@ -40,7 +40,7 @@ The certificate is required if you want to [apply HTTP policies to encrypted web To configure the Cloudflare One Client to install a root certificate on your organization's devices: 1. (Optional) [Upload](/cloudflare-one/team-and-resources/devices/user-side-certificates/custom-certificate/) a custom root certificate to Cloudflare. -2. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Team & Resources** > **Devices** > **Management**. +2. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Team & Resources** > **Devices** > **Management**. 3. Under **Global Cloudflare One Client settings**, turn on [**Install CA to system certificate store**](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/settings/#install-ca-to-system-certificate-store). 4. [Install](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/download/) the Cloudflare One Client on the device. 5. [Enroll the device](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/manual-deployment/) in your Zero Trust organization. diff --git a/src/content/docs/cloudflare-one/team-and-resources/devices/user-side-certificates/custom-certificate.mdx b/src/content/docs/cloudflare-one/team-and-resources/devices/user-side-certificates/custom-certificate.mdx index 3a855c1836d..5a113ac3e53 100644 --- a/src/content/docs/cloudflare-one/team-and-resources/devices/user-side-certificates/custom-certificate.mdx +++ b/src/content/docs/cloudflare-one/team-and-resources/devices/user-side-certificates/custom-certificate.mdx @@ -122,7 +122,7 @@ You can upload a single root certificate or a full certificate chain. When uploa -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Traffic policies** > **Traffic settings** > **Certificates**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Traffic policies** > **Traffic settings** > **Certificates**. 2. Select **Upload certificate**. 3. Enter the private key and SSL certificate you generated or select **Paste certificate from file** to upload them from a file. If uploading a certificate chain, paste all certificates (root and intermediates) in PEM format with the root certificate first. 4. Select **Upload custom certificate**. diff --git a/src/content/docs/cloudflare-one/team-and-resources/devices/user-side-certificates/index.mdx b/src/content/docs/cloudflare-one/team-and-resources/devices/user-side-certificates/index.mdx index e5e79f4d6c7..8ecdebe8391 100644 --- a/src/content/docs/cloudflare-one/team-and-resources/devices/user-side-certificates/index.mdx +++ b/src/content/docs/cloudflare-one/team-and-resources/devices/user-side-certificates/index.mdx @@ -39,7 +39,7 @@ To generate a new Cloudflare root certificate for your Zero Trust organization: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Traffic policies** > **Traffic settings**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Traffic policies** > **Traffic settings**. 2. Select **Certificates**. 3. Select **Generate certificate**. 4. Choose a duration of time before the certificate expires. Cloudflare recommends expiration after five years. Alternatively, choose _Custom_ and enter a custom amount in days. @@ -73,7 +73,7 @@ To activate your root certificate: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Traffic policies** > **Traffic settings**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Traffic policies** > **Traffic settings**. 2. Select **Certificates**. 3. Select the certificate you want to activate. 4. Select **Activate**. @@ -97,7 +97,7 @@ Once you deploy and install your certificate, you can turn it on for use in insp -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Traffic policies** > **Traffic settings**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Traffic policies** > **Traffic settings**. 2. Select **Certificates**. 3. Select the certificate you want to turn on. 4. In **Basic information**, select **Confirm and turn on certificate**. diff --git a/src/content/docs/cloudflare-one/team-and-resources/devices/user-side-certificates/manual-deployment.mdx b/src/content/docs/cloudflare-one/team-and-resources/devices/user-side-certificates/manual-deployment.mdx index 637247df35f..9045c627b4c 100644 --- a/src/content/docs/cloudflare-one/team-and-resources/devices/user-side-certificates/manual-deployment.mdx +++ b/src/content/docs/cloudflare-one/team-and-resources/devices/user-side-certificates/manual-deployment.mdx @@ -36,7 +36,7 @@ You can only download Cloudflare-generated certificates from the Cloudflare One First, [generate](/cloudflare-one/team-and-resources/devices/user-side-certificates/#generate-a-cloudflare-root-certificate) and download a Cloudflare certificate. The certificate is available in both `.pem` and `.crt` file format. Certain applications require the certificate to be in a specific file type, so ensure you download the most appropriate file for your use case. -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Traffic policies** > **Traffic settings**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Traffic policies** > **Traffic settings**. 2. Select **Certificates**. 3. Select the certificate you want to download. 4. Select **More actions**. diff --git a/src/content/docs/cloudflare-one/team-and-resources/users/risk-score.mdx b/src/content/docs/cloudflare-one/team-and-resources/users/risk-score.mdx index 7baf04d8c1f..440b8c894dc 100644 --- a/src/content/docs/cloudflare-one/team-and-resources/users/risk-score.mdx +++ b/src/content/docs/cloudflare-one/team-and-resources/users/risk-score.mdx @@ -31,7 +31,7 @@ Cloudflare One assigns a risk score of Low, Medium, or High based on detections To view a user's risk score: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Teams & Resources**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Teams & Resources**. 2. Select **Users**. 3. Select **Risk score** > **Risk scoring**. 4. Select a user's name to view their instances of risk behaviors, if any. You can select an instance of a risk behavior to view the log associated with the detection. @@ -42,7 +42,7 @@ Users that have had their risk score [cleared](#clear-a-users-risk-score) will n If required, you can reset risk scores for specific users. Once reset, users will not appear in the associated risk table until they trigger another risk behavior. -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Teams & Resources**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Teams & Resources**. 2. Select **Risk score** > **Risk scoring**. 3. Select the user you want to clear the risk score for. 4. In **User risk overview**, select **Reset user risk**. @@ -89,7 +89,7 @@ When a risk behavior is disabled, monitoring for future activity will cease. Pre You can change the risk level for a behavior at any time. -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Teams & Resources**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Teams & Resources**. 2. Go to **Users**. 3. Select **Risk score** > **Risk behaviors**. 2. Select the risk behavior you want to modify. @@ -102,7 +102,7 @@ You can use risk scores to control access to applications protected by [Cloudfla To add a risk score requirement to an Access policy: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Access controls** > **Policies**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Access controls** > **Policies**. 2. Create a new policy or select an existing policy to edit. 3. Add a rule with the _User Risk Score_ selector. 4. For **Value**, select the risk level threshold (Low, Medium, or High). diff --git a/src/content/docs/cloudflare-one/team-and-resources/users/seat-management.mdx b/src/content/docs/cloudflare-one/team-and-resources/users/seat-management.mdx index e51bd7c513a..7f4eb17716d 100644 --- a/src/content/docs/cloudflare-one/team-and-resources/users/seat-management.mdx +++ b/src/content/docs/cloudflare-one/team-and-resources/users/seat-management.mdx @@ -34,7 +34,7 @@ Removing a user will delete all device registrations associated with the user. F ### Check number of seats used -To check the number of seats consumed by active users in your organization, log in to [Cloudflare One](https://one.dash.cloudflare.com). **Cloudflare One overview** will display the amount of seats consumed and the remaining amount available. For more details on your users, go to **Team & Resources** > **Users**. +To check the number of seats consumed by active users in your organization, log in to [Cloudflare One](https://dash.cloudflare.com/one/). **Cloudflare One overview** will display the amount of seats consumed and the remaining amount available. For more details on your users, go to **Team & Resources** > **Users**. ### Revoke a user @@ -42,7 +42,7 @@ When you revoke a user, this action will terminate active sessions, but will not To revoke a user from your Zero Trust Organization: -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Team & Resources** > **Users**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Team & Resources** > **Users**. 2. Select the checkbox next to a user with an **Active** status in the **Seat usage** column. 3. Select **Action** > **Revoke**. 4. Select **Revoke sessions**. @@ -59,7 +59,7 @@ Cloudflare One can automatically remove any user who does not log in to an Acces To enable user seat expiration: -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Settings** > **Admin controls**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Settings** > **Admin controls**. 2. In **Remove inactive users from seats**, select **Edit**. 3. Select an inactivity time from the dropdown menu. 4. Select **Save**. diff --git a/src/content/docs/cloudflare-one/team-and-resources/users/users.mdx b/src/content/docs/cloudflare-one/team-and-resources/users/users.mdx index 8dd1e9f4db6..babaaf8ea96 100644 --- a/src/content/docs/cloudflare-one/team-and-resources/users/users.mdx +++ b/src/content/docs/cloudflare-one/team-and-resources/users/users.mdx @@ -14,7 +14,7 @@ User logs show a list of all users who have authenticated to Cloudflare One. For ## View user logs -In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Teams & Resources** > **Users**. +In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Teams & Resources** > **Users**. This page lists all users who have registered the Cloudflare One Client or authenticated to a Cloudflare Access application. You can select a user's name to view detailed logs, [revoke their session](/cloudflare-one/access-controls/access-settings/session-management/#revoke-user-sessions), or [remove their seat](/cloudflare-one/team-and-resources/users/seat-management/). diff --git a/src/content/docs/cloudflare-one/tutorials/ai-wrapper-tenant-control.mdx b/src/content/docs/cloudflare-one/tutorials/ai-wrapper-tenant-control.mdx index 5c8de6430a4..1b3b96b9801 100644 --- a/src/content/docs/cloudflare-one/tutorials/ai-wrapper-tenant-control.mdx +++ b/src/content/docs/cloudflare-one/tutorials/ai-wrapper-tenant-control.mdx @@ -408,7 +408,7 @@ The Worker is now behind an addressable public hostname. Make sure to turn off b To secure the AI agent wrapper to ensure that only trusted users can access it: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Access controls** > **Applications**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Access controls** > **Applications**. 2. Select **Add an application**. 3. Choose **Self-hosted**. 4. Enter a name for your AI agent wrapper application. @@ -423,7 +423,7 @@ Now your AI wrapper can only be accessed by your users that successfully match y You can now block access to all unauthorized public AI agents with a Gateway [HTTP policy](/cloudflare-one/traffic-policies/http-policies/). -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Traffic policies** > **Firewall policies** > **HTTP**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Traffic policies** > **Firewall policies** > **HTTP**. 2. Select **Add a policy**. 3. Add the following policy: @@ -445,7 +445,7 @@ Now that you have full control over access to your AI agent wrapper, you can enf You can use [Data Loss Prevention (DLP)](/cloudflare-one/data-loss-prevention/) to prevent your users from sending sensitive data to the AI agent. -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Data loss prevention** > **Profiles**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Data loss prevention** > **Profiles**. 2. Ensure that the [DLP profiles](/cloudflare-one/data-loss-prevention/dlp-profiles/) you want to enforce are properly configured. 3. Add an HTTP policy to enforce the DLP profile for the hostname for your wrapper. For example: diff --git a/src/content/docs/cloudflare-one/tutorials/deploy-client-headless-linux.mdx b/src/content/docs/cloudflare-one/tutorials/deploy-client-headless-linux.mdx index 25e1cd38a0b..d2d0f92e522 100644 --- a/src/content/docs/cloudflare-one/tutorials/deploy-client-headless-linux.mdx +++ b/src/content/docs/cloudflare-one/tutorials/deploy-client-headless-linux.mdx @@ -38,7 +38,7 @@ Device enrollment permissions determine the users and devices that can register To allow devices to enroll using a service token: -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Team & Resources** > **Devices**. Select the **Management** tab. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Team & Resources** > **Devices**. Select the **Management** tab. 2. In **Device enrollment permissions**, select **Manage**. 3. In the **Policies** tab, select **Create new policy**. A new tab will open with the policy creation page. 4. For **Action**, select _Service Auth_. @@ -124,4 +124,4 @@ To install the Cloudflare One Client using the example script: sudo ./install_warp.sh ``` -The Cloudflare One Client is now deployed with the configuration parameters stored in `/var/lib/cloudflare-warp/mdm.xml`. Assuming [`auto_connect`](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/mdm-deployment/parameters/#auto_connect) is configured, the Cloudflare One Client will automatically connect to your Zero Trust organization. Once connected, the device will appear in [Cloudflare One](https://one.dash.cloudflare.com) under **Team & Resources** > **Devices** with the email `non_identity@.cloudflareaccess.com`. +The Cloudflare One Client is now deployed with the configuration parameters stored in `/var/lib/cloudflare-warp/mdm.xml`. Assuming [`auto_connect`](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/mdm-deployment/parameters/#auto_connect) is configured, the Cloudflare One Client will automatically connect to your Zero Trust organization. Once connected, the device will appear in [Cloudflare One](https://dash.cloudflare.com/one/) under **Team & Resources** > **Devices** with the email `non_identity@.cloudflareaccess.com`. diff --git a/src/content/docs/cloudflare-one/tutorials/entra-id-conditional-access.mdx b/src/content/docs/cloudflare-one/tutorials/entra-id-conditional-access.mdx index a86b7eb68a7..3f44d954982 100644 --- a/src/content/docs/cloudflare-one/tutorials/entra-id-conditional-access.mdx +++ b/src/content/docs/cloudflare-one/tutorials/entra-id-conditional-access.mdx @@ -62,7 +62,7 @@ Once the base IdP integration is tested and working, grant permission for Cloudf To import your Conditional Access policies into Cloudflare Access: -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Access controls** > **Access settings**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Access controls** > **Access settings**. 2. In **Manage your App Launcher**, select **Manage**. 3. Choose **Login methods**. 4. Find your Microsoft Entra ID integration and select **Edit**. @@ -73,7 +73,7 @@ To import your Conditional Access policies into Cloudflare Access: To enforce your Conditional Access policies on a Cloudflare Access application: -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Access controls** > **Applications**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Access controls** > **Applications**. 2. Select **Add an application**. diff --git a/src/content/docs/cloudflare-one/tutorials/entra-id-risky-users.mdx b/src/content/docs/cloudflare-one/tutorials/entra-id-risky-users.mdx index fbfa9dc10b8..221a483a8f2 100644 --- a/src/content/docs/cloudflare-one/tutorials/entra-id-risky-users.mdx +++ b/src/content/docs/cloudflare-one/tutorials/entra-id-risky-users.mdx @@ -158,7 +158,7 @@ Cloudflare Access will now synchronize changes in group membership with Entra ID Finally, create a [Gateway HTTP policy](/cloudflare-one/traffic-policies/http-policies/) to isolate traffic for risky user groups. -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Traffic policies** > **Firewall policies** > **HTTP**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Traffic policies** > **Firewall policies** > **HTTP**. 2. Select **Add a policy**. diff --git a/src/content/docs/cloudflare-one/tutorials/integrate-microsoft-mcas-teams.mdx b/src/content/docs/cloudflare-one/tutorials/integrate-microsoft-mcas-teams.mdx index ab595a65b90..3f90f2d19f4 100644 --- a/src/content/docs/cloudflare-one/tutorials/integrate-microsoft-mcas-teams.mdx +++ b/src/content/docs/cloudflare-one/tutorials/integrate-microsoft-mcas-teams.mdx @@ -67,7 +67,7 @@ curl -v "https:///api/discovery_block_scripts/?format=120&type=all ## Adding a hostname list in Cloudflare One -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Reusable components** > **Lists** +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Reusable components** > **Lists** 2. Select **Upload CSV**. Even though the hostname list is not in CSV format, it will work with no issues. 3. Add a name for the list, specify _Hostnames_ as the list type, and give it a description. 4. Drag and drop your MCAS output file created via the API call, or you can select **Select a file**. diff --git a/src/content/docs/cloudflare-one/tutorials/kubectl.mdx b/src/content/docs/cloudflare-one/tutorials/kubectl.mdx index b082c06b9b3..4834e0b0524 100644 --- a/src/content/docs/cloudflare-one/tutorials/kubectl.mdx +++ b/src/content/docs/cloudflare-one/tutorials/kubectl.mdx @@ -35,7 +35,7 @@ You can connect to machines over `kubectl` using Cloudflare's Zero Trust platfor ## Create an Access policy -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Access controls** > **Applications**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Access controls** > **Applications**. 2. Select **Add an application**. 3. Select **Self-hosted**. 4. Enter a name for your Access application. diff --git a/src/content/docs/cloudflare-one/tutorials/m365-dedicated-egress-ips.mdx b/src/content/docs/cloudflare-one/tutorials/m365-dedicated-egress-ips.mdx index 20be140548c..c32fd2a2a55 100644 --- a/src/content/docs/cloudflare-one/tutorials/m365-dedicated-egress-ips.mdx +++ b/src/content/docs/cloudflare-one/tutorials/m365-dedicated-egress-ips.mdx @@ -33,7 +33,7 @@ Make sure you have: ## Create an egress policy in Cloudflare Gateway -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Traffic policies** > **Egress policies**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Traffic policies** > **Egress policies**. 2. Select **Add a policy**. diff --git a/src/content/docs/cloudflare-one/tutorials/mongodb-tunnel.mdx b/src/content/docs/cloudflare-one/tutorials/mongodb-tunnel.mdx index b269d2f3fbc..cb53cc1651c 100644 --- a/src/content/docs/cloudflare-one/tutorials/mongodb-tunnel.mdx +++ b/src/content/docs/cloudflare-one/tutorials/mongodb-tunnel.mdx @@ -37,7 +37,7 @@ In this tutorial, a client running `cloudflared` connects over SSH to a MongoDB You can build a rule in Cloudflare Access to control who can connect to your MongoDB deployment. Cloudflare Access rules are built around a hostname; even though this deployment will be accessible over SSH, the resource will be represented in Cloudflare as a hostname. For example, if you have the website `app.com` in your Cloudflare account, you can build a rule to secure `mongodb.app.com`. -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Access controls** > **Applications**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Access controls** > **Applications**. 2. Select **Add an application**. diff --git a/src/content/docs/cloudflare-one/tutorials/okta-u2f.mdx b/src/content/docs/cloudflare-one/tutorials/okta-u2f.mdx index 5ba73ee05a8..cde8a4a840f 100644 --- a/src/content/docs/cloudflare-one/tutorials/okta-u2f.mdx +++ b/src/content/docs/cloudflare-one/tutorials/okta-u2f.mdx @@ -47,7 +47,7 @@ An Okta administrator in your organization must first [enable U2F support](https You can begin building U2F policies by testing your Okta integration. -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to the **Access controls** > **Access settings**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to the **Access controls** > **Access settings**. 2. In **Manage your App Launcher**, select **Manage**. 3. Choose **Login methods**. 4. Choose the row for Okta and select **Test**. diff --git a/src/content/docs/cloudflare-one/tutorials/r2-logs.mdx b/src/content/docs/cloudflare-one/tutorials/r2-logs.mdx index a78c2233c32..48e9f5f847f 100644 --- a/src/content/docs/cloudflare-one/tutorials/r2-logs.mdx +++ b/src/content/docs/cloudflare-one/tutorials/r2-logs.mdx @@ -45,7 +45,7 @@ This tutorial covers how to build a [Cloudflare R2 bucket](/r2/buckets/) to stor ## Connect a Zero Trust Logpush job -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Insights** > **Logs**. Select **Manage Logpush**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Insights** > **Logs**. Select **Manage Logpush**. 2. Select **Connect a service**. 3. Choose which data sets and fields you want to send to your bucket. Select **Next**. 4. Select **S3 Compatible**. diff --git a/src/content/docs/cloudflare-one/tutorials/s3-buckets.mdx b/src/content/docs/cloudflare-one/tutorials/s3-buckets.mdx index 9360af12834..f1b6f98e488 100644 --- a/src/content/docs/cloudflare-one/tutorials/s3-buckets.mdx +++ b/src/content/docs/cloudflare-one/tutorials/s3-buckets.mdx @@ -98,7 +98,7 @@ A bucket website endpoint will be available at `http://.s3-web ### 4. Add a published application to the Cloudflare Tunnel -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Networks** > **Connectors** > **Cloudflare Tunnels**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Networks** > **Connectors** > **Cloudflare Tunnels**. 2. Select your Tunnel, then select **Configure**. 3. Go to **Published applications**, then select **Add a public hostname**. 4. Enter a subdomain your organization will use to access the S3 bucket. For example, `s3-bucket..com`. @@ -188,7 +188,7 @@ A bucket website endpoint will be available at `http://.s3-web ### 3. Setup a dedicated egress IP policy -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Traffic policies** > **Egress policies**. Select **Add a policy**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Traffic policies** > **Egress policies**. Select **Add a policy**. 2. Create a policy that specifies which proxied traffic Gateway should assign a [dedicated egress IP](/cloudflare-one/traffic-policies/egress-policies/dedicated-egress-ips/) to. For more information, refer to [Egress policies](/cloudflare-one/traffic-policies/egress-policies/). 3. In **Select an egress IP**, choose _Use dedicated Cloudflare egress IPs_. Select the dedicated egress IP defined in your bucket policy. 4. Select **Create policy**. diff --git a/src/content/docs/cloudflare-one/tutorials/user-selectable-egress-ips.mdx b/src/content/docs/cloudflare-one/tutorials/user-selectable-egress-ips.mdx index c4b74f34f3d..5ace869415e 100644 --- a/src/content/docs/cloudflare-one/tutorials/user-selectable-egress-ips.mdx +++ b/src/content/docs/cloudflare-one/tutorials/user-selectable-egress-ips.mdx @@ -43,7 +43,7 @@ First, create [virtual networks](/cloudflare-one/networks/connectors/cloudflare- -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Networks** > **Routes**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Networks** > **Routes**. 2. In **Virtual networks**, select **Create virtual network**. 3. Name your virtual network. We recommend using a name related to the location of the corresponding dedicated egress IP. For example, if your users will egress from the Americas, you can name the virtual network `vnet-AMER`. 4. Select **Save**. @@ -137,7 +137,7 @@ Next, assign your dedicated egress IPs to each virtual network using Gateway egr -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Traffic policies** > **Egress policies**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Traffic policies** > **Egress policies**. 2. Select **Add a policy**. diff --git a/src/content/docs/dns/internal-dns/get-started.mdx b/src/content/docs/dns/internal-dns/get-started.mdx index b760d0ce037..bd9ec7bcde7 100644 --- a/src/content/docs/dns/internal-dns/get-started.mdx +++ b/src/content/docs/dns/internal-dns/get-started.mdx @@ -143,7 +143,7 @@ Besides selecting an internal DNS view when setting up your resolver policies, y -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Traffic policies** > **Firewall policies** > **Resolver policies**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Traffic policies** > **Firewall policies** > **Resolver policies**. 2. Select **Add a policy** and enter a name and description. 3. Create an expression for the traffic you wish to route. For guidance about selectors, operators, and values, refer to [Gateway resolver policies](/cloudflare-one/traffic-policies/resolver-policies/#selectors). 4. Select **Use Internal DNS**. Choose the view that queries matching the expression should be sent to. diff --git a/src/content/docs/email-security/migrate-to-email-security.mdx b/src/content/docs/email-security/migrate-to-email-security.mdx index 0f8848970f5..a64b5c64290 100644 --- a/src/content/docs/email-security/migrate-to-email-security.mdx +++ b/src/content/docs/email-security/migrate-to-email-security.mdx @@ -39,7 +39,7 @@ In Area 1, you [invite users](/email-security/account-setup/manage-account-membe To invite users in Zero Trust Email security: -1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/). +1. Log in to [Cloudflare One](https://dash.cloudflare.com/one/). 2. Go to **Manage Account**. 3. Select **Members** > **Invite** > [Add account members](/fundamentals/manage-members/manage/#add-account-members). diff --git a/src/content/docs/fundamentals/manage-members/dashboard-sso.mdx b/src/content/docs/fundamentals/manage-members/dashboard-sso.mdx index 0e50e2c24e4..737035ee439 100644 --- a/src/content/docs/fundamentals/manage-members/dashboard-sso.mdx +++ b/src/content/docs/fundamentals/manage-members/dashboard-sso.mdx @@ -176,7 +176,7 @@ curl "https://api.cloudflare.com/client/v4/accounts/{account_id}/sso_connectors/ Before enabling SSO for your domain, verify that your identity provider is configured correctly: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Integrations** > **Identity providers**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Integrations** > **Identity providers**. 2. Find your IdP and select **Test**. 3. Confirm that the test returns a successful authentication result. @@ -210,7 +210,7 @@ Configure an identity provider (IdP)-initiated single sign-on (SSO) session usin #### Prerequisites -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Access controls** > **Applications** > select your **SSO App**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Access controls** > **Applications** > select your **SSO App**. 2. Select **Configure** to access the application settings. 3. In the **Basic Information** section, copy the **SSO Endpoint URL** and **Access Entity ID or Issuer**. You will need these values for your IdP setup. @@ -231,7 +231,7 @@ Configure an identity provider (IdP)-initiated single sign-on (SSO) session usin If you use only one IdP (for example, Okta) for Cloudflare SSO and want users to skip the identity provider selection prompt: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Access controls** > **Applications** > select your **SSO App**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Access controls** > **Applications** > select your **SSO App**. 2. Go to **Login methods**. 3. Disable **Accept all available identity providers** and ensure only Okta is selected as the login method. 4. Enable **Instant Auth** to allow users to skip identity provider selection. @@ -421,7 +421,7 @@ Cloudflare does not allow you to change your t -4. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Reusable components** > **Custom pages**. +4. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Reusable components** > **Custom pages**. 5. Under **Team domain**, select **Edit** to enter the new team name. Select **Save**. 6. In your identity provider, update your Cloudflare integration with the new team name. For example, if you are using a SAML IdP, you will need to update the Single Sign-on URL and Entity ID to `https://.cloudflareaccess.com/cdn-cgi/access/callback`. 7. Recreate any deleted SSO connectors using the steps in [Register your domain with Cloudflare for SSO](/fundamentals/manage-members/dashboard-sso/#2-register-your-domain-with-cloudflare-for-sso). diff --git a/src/content/docs/hyperdrive/configuration/connect-to-private-database.mdx b/src/content/docs/hyperdrive/configuration/connect-to-private-database.mdx index fd255debc7f..4e7c480daa3 100644 --- a/src/content/docs/hyperdrive/configuration/connect-to-private-database.mdx +++ b/src/content/docs/hyperdrive/configuration/connect-to-private-database.mdx @@ -93,7 +93,7 @@ The service token will be used to restrict requests to the tunnel, and is needed -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Access controls** > **Service credentials** > **Service Tokens**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Access controls** > **Service credentials** > **Service Tokens**. 2. Select **Create Service Token**. @@ -116,7 +116,7 @@ The service token will be used to restrict requests to the tunnel, and is needed [Cloudflare Access](/cloudflare-one/access-controls/policies/) will be used to verify that requests to the tunnel originate from Hyperdrive using the service token created above. -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Access controls** > **Applications**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Access controls** > **Applications**. 2. Select **Add an application**. diff --git a/src/content/docs/learning-paths/clientless-access/terraform/publish-apps-with-terraform.mdx b/src/content/docs/learning-paths/clientless-access/terraform/publish-apps-with-terraform.mdx index 7742cac279f..35456c3a9d8 100644 --- a/src/content/docs/learning-paths/clientless-access/terraform/publish-apps-with-terraform.mdx +++ b/src/content/docs/learning-paths/clientless-access/terraform/publish-apps-with-terraform.mdx @@ -32,7 +32,7 @@ Create a `.tf` file and copy-paste the following example. Fill in your API token
-1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Networks** > **Connectors** > **Cloudflare Tunnels**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Networks** > **Connectors** > **Cloudflare Tunnels**. 2. Select the tunnel name. 3. Copy the **Tunnel ID**. @@ -152,7 +152,7 @@ resource "cloudflare_access_policy" "example_policy" { -Users can now access the private application by going to the public URL and authenticating with Cloudflare Access. You can view your new tunnel route, Access application, and Access policy in [Cloudflare One](https://one.dash.cloudflare.com). The new DNS record is shown in the [Cloudflare dashboard](https://dash.cloudflare.com). +Users can now access the private application by going to the public URL and authenticating with Cloudflare Access. You can view your new tunnel route, Access application, and Access policy in [Cloudflare One](https://dash.cloudflare.com/one/). The new DNS record is shown in the [Cloudflare dashboard](https://dash.cloudflare.com). :::note diff --git a/src/content/docs/learning-paths/holistic-ai-security/build-security-policies/set-policy-approval.mdx b/src/content/docs/learning-paths/holistic-ai-security/build-security-policies/set-policy-approval.mdx index 106b2506257..2a81b2f02dc 100644 --- a/src/content/docs/learning-paths/holistic-ai-security/build-security-policies/set-policy-approval.mdx +++ b/src/content/docs/learning-paths/holistic-ai-security/build-security-policies/set-policy-approval.mdx @@ -16,7 +16,7 @@ If you use specific AI tools within your organization, you may want to create po ## Create a Gateway policy for monitoring and evaluating all AI tool usage -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Traffic policies** > **Firewall policies**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Traffic policies** > **Firewall policies**. 2. In the **HTTP** tab, select **Add a policy**. 3. Name the policy. 4. Under **Traffic**, build a logical expression that defines the traffic you want to allow for AI at your organization. @@ -40,7 +40,7 @@ Cloudflare Workers are an easy method to stand up custom user coaching pages. Th ## Redirect users towards approved AI tools -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Traffic policies** > **Firewall policies**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Traffic policies** > **Firewall policies**. 2. In the **HTTP** tab, select **Add a policy**. 3. Name the policy. 4. Under **Traffic**, build a logical expression that defines the traffic you want to allow for AI at your organization. @@ -65,7 +65,7 @@ For more information, refer to [Configure policy block behavior](/cloudflare-one You can build policies that enable Prompt Capture for AI applications in specific, complex scenarios. This gives you the flexibility to apply advanced functionality to certain applications, tool types, or user groups, such as contractors or new employees, especially if they pose a higher risk for using unsanctioned applications due to lack of awareness or training. -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Traffic policies** > **Firewall policies**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Traffic policies** > **Firewall policies**. 2. In the **HTTP** tab, select **Add a policy**. 3. Name the policy. 4. Under **Traffic**, build a logical expression that defines the traffic you want to allow for AI at your organization. @@ -89,7 +89,7 @@ If your organization uses [ChatGPT Business](https://chatgpt.com/business/), you To create this policy, you will add a custom HTTP header to your Gateway policy. This header, `Chatgpt-Allowed-Workspace-Id`, ensures that only requests with your organization's unique workspace ID are permitted. -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Traffic policies** > **Firewall policies**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Traffic policies** > **Firewall policies**. 2. In the **HTTP** tab, select **Add a policy**. 3. Name the policy. 4. Under **Traffic**, build a logical expression that defines the traffic you want to allow. diff --git a/src/content/docs/learning-paths/replace-vpn/build-policies/create-policy.mdx b/src/content/docs/learning-paths/replace-vpn/build-policies/create-policy.mdx index ba115d24863..6c77d448ba5 100644 --- a/src/content/docs/learning-paths/replace-vpn/build-policies/create-policy.mdx +++ b/src/content/docs/learning-paths/replace-vpn/build-policies/create-policy.mdx @@ -21,7 +21,7 @@ To ensure holistic security precautions, we recommend securing each distinct pri ## Create a Gateway policy -To create a new policy, open [Cloudflare One](https://one.dash.cloudflare.com/) and go to **Traffic policies** > **Firewall policies**. +To create a new policy, open [Cloudflare One](https://dash.cloudflare.com/one/) and go to **Traffic policies** > **Firewall policies**. ## Example DNS policy diff --git a/src/content/docs/learning-paths/replace-vpn/build-policies/test-your-first-application.mdx b/src/content/docs/learning-paths/replace-vpn/build-policies/test-your-first-application.mdx index 3763a799a1e..c7bbfdf15b8 100644 --- a/src/content/docs/learning-paths/replace-vpn/build-policies/test-your-first-application.mdx +++ b/src/content/docs/learning-paths/replace-vpn/build-policies/test-your-first-application.mdx @@ -34,7 +34,7 @@ If your manual test fails, troubleshoot the Cloudflare One Client. Cloudflare re Analytics provide visualizations of [log data](/learning-paths/replace-vpn/build-policies/test-your-first-application/#review-logs). To review Access or Gateway analytics: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Insights** > **Analytics** > **Dashboards**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Insights** > **Analytics** > **Dashboards**. 2. Select **[Access event analytics](/cloudflare-one/insights/analytics/access/)** for a summary of login events or **[Application Access Report](/cloudflare-one/insights/analytics/application-access/)** for a summary of overall Access Activity. 3. Select the **HTTP request analytics**, **DNS query analytics** or **Network session analytics** depending on [your Gateway investigation scope](/cloudflare-one/insights/analytics/gateway/). @@ -43,12 +43,12 @@ Analytics provide visualizations of [log data](/learning-paths/replace-vpn/build [Logs](/cloudflare-one/insights/logs/) provide event-level (such as an authentication attempt or a DNS query) visibility into your Cloudflare One environment. To review traffic activity for applications protected by Access: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Insights** > **Logs**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Insights** > **Logs**. 2. Select **Access authentication logs**. 3. Review the [per-request logs](/cloudflare-one/insights/logs/dashboard-logs/access-authentication-logs/#per-request-logs) for your application. To review traffic activity in the [Gateway logs](/cloudflare-one/insights/logs/dashboard-logs/gateway-logs/): -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Insights** > **Logs**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Insights** > **Logs**. 2. Select **HTTP request logs**, **Network logs**, or **DNS query logs** depending on your investigation scope. Refer to [Troubleshoot Gateway](/cloudflare-one/traffic-policies/troubleshoot-gateway/) to troubleshoot common issues with Gateway egress policies. diff --git a/src/content/docs/learning-paths/secure-internet-traffic/build-dns-policies/create-policy.mdx b/src/content/docs/learning-paths/secure-internet-traffic/build-dns-policies/create-policy.mdx index 50ad698712c..93de0da015b 100644 --- a/src/content/docs/learning-paths/secure-internet-traffic/build-dns-policies/create-policy.mdx +++ b/src/content/docs/learning-paths/secure-internet-traffic/build-dns-policies/create-policy.mdx @@ -24,7 +24,7 @@ To create a new DNS policy: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Traffic policies** > **Firewall policies**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Traffic policies** > **Firewall policies**. 2. In the **DNS** tab, select **Add a policy**. 3. Name the policy. 4. Under **Traffic**, build a logical expression that defines the traffic you want to allow or block. diff --git a/src/content/docs/learning-paths/secure-internet-traffic/build-egress-policies/egress-policies.mdx b/src/content/docs/learning-paths/secure-internet-traffic/build-egress-policies/egress-policies.mdx index 4645f64d04f..35d0fee7ab5 100644 --- a/src/content/docs/learning-paths/secure-internet-traffic/build-egress-policies/egress-policies.mdx +++ b/src/content/docs/learning-paths/secure-internet-traffic/build-egress-policies/egress-policies.mdx @@ -23,7 +23,7 @@ Egress policies allow you to determine whether your organization's traffic egres To create a new egress policy: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Traffic policies** > **Egress policies**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Traffic policies** > **Egress policies**. 2. Select **Add a policy**. diff --git a/src/content/docs/learning-paths/secure-internet-traffic/build-http-policies/browser-isolation.mdx b/src/content/docs/learning-paths/secure-internet-traffic/build-http-policies/browser-isolation.mdx index 3903a3a848b..1e588900377 100644 --- a/src/content/docs/learning-paths/secure-internet-traffic/build-http-policies/browser-isolation.mdx +++ b/src/content/docs/learning-paths/secure-internet-traffic/build-http-policies/browser-isolation.mdx @@ -32,7 +32,7 @@ You can control potential risk and shape user behavior without applying heavy-ha -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Traffic policies** > **Firewall policies**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Traffic policies** > **Firewall policies**. 2. In the **HTTP** tab, select **Add a policy**. diff --git a/src/content/docs/learning-paths/secure-your-email/configure-email-security/active-directory-sync.mdx b/src/content/docs/learning-paths/secure-your-email/configure-email-security/active-directory-sync.mdx index a017783809f..be2e08fed23 100644 --- a/src/content/docs/learning-paths/secure-your-email/configure-email-security/active-directory-sync.mdx +++ b/src/content/docs/learning-paths/secure-your-email/configure-email-security/active-directory-sync.mdx @@ -14,7 +14,7 @@ Directories are folders to store user data. Email security allows you to manage To manage your Microsoft 365 directory: -1. Log in to [Zero Trust ](https://one.dash.cloudflare.com/). +1. Log in to [Zero Trust ](https://dash.cloudflare.com/one/). 2. Select **Email security**. 3. Select **Directories**. 4. Under **Directory name**, select **MS directory**. @@ -24,7 +24,7 @@ To manage your Microsoft 365 directory: To manage your Google Workspace Directory: -1. Log in to [Zero Trust ](https://one.dash.cloudflare.com/). +1. Log in to [Zero Trust ](https://dash.cloudflare.com/one/). 2. Select **Email security**. 3. Select **Directories**. 4. Under **Directory name**, select **Google Workspace Directory**. @@ -49,4 +49,4 @@ In addition, Email security allows you to: - [Remove groups from the registry](/cloudflare-one/email-security/directories/manage-integrated-directories/manage-groups-directory/#remove-groups-from-registry). - [Filter the impersonation registry](/cloudflare-one/email-security/directories/manage-integrated-directories/manage-groups-directory/#filter-impersonation-registry). -- [Manage users in your directory](/cloudflare-one/email-security/directories/manage-integrated-directories/manage-users-directory/). \ No newline at end of file +- [Manage users in your directory](/cloudflare-one/email-security/directories/manage-integrated-directories/manage-users-directory/). diff --git a/src/content/docs/learning-paths/secure-your-email/configure-email-security/create-allow-policies.mdx b/src/content/docs/learning-paths/secure-your-email/configure-email-security/create-allow-policies.mdx index ce5a674615d..0d89e26c68a 100644 --- a/src/content/docs/learning-paths/secure-your-email/configure-email-security/create-allow-policies.mdx +++ b/src/content/docs/learning-paths/secure-your-email/configure-email-security/create-allow-policies.mdx @@ -20,7 +20,7 @@ You can choose how Email security will handle messages that match your criteria: To configure allow policies: -1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/). +1. Log in to [Cloudflare One](https://dash.cloudflare.com/one/). 2. Select **Email security**. 3. Select **Settings**, then go to **Detection settings** > **Allow policies**. 4. On the **Detection settings** page, select **Add a policy**. diff --git a/src/content/docs/learning-paths/secure-your-email/configure-email-security/impersonation-registry.mdx b/src/content/docs/learning-paths/secure-your-email/configure-email-security/impersonation-registry.mdx index 0378058f8d8..906ea8f259a 100644 --- a/src/content/docs/learning-paths/secure-your-email/configure-email-security/impersonation-registry.mdx +++ b/src/content/docs/learning-paths/secure-your-email/configure-email-security/impersonation-registry.mdx @@ -14,7 +14,7 @@ The impersonation registry protects against these attacks by looking for spoofs To add a user to the impersonation registry: -1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/). +1. Log in to [Cloudflare One](https://dash.cloudflare.com/one/). 2. Select **Email security**. 3. Select **Settings** > **Impersonation registry**. 4. Select **Add a user**. diff --git a/src/content/docs/learning-paths/secure-your-email/configure-email-security/set-additional-detections.mdx b/src/content/docs/learning-paths/secure-your-email/configure-email-security/set-additional-detections.mdx index ad7c97fb428..e32cae13bfe 100644 --- a/src/content/docs/learning-paths/secure-your-email/configure-email-security/set-additional-detections.mdx +++ b/src/content/docs/learning-paths/secure-your-email/configure-email-security/set-additional-detections.mdx @@ -17,7 +17,7 @@ Email security allows you to configure the following additional detections: To configure additional detections: -1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/). +1. Log in to [Cloudflare One](https://dash.cloudflare.com/one/). 2. Select **Email security**. 3. Select **Settings**. 4. On the Settings page, go to **Detection settings** > **Additional detections**, and select **Edit**. diff --git a/src/content/docs/learning-paths/secure-your-email/enable-auto-moves/configure-auto-moves.mdx b/src/content/docs/learning-paths/secure-your-email/enable-auto-moves/configure-auto-moves.mdx index 0182e9c8c20..bf90e8eed4b 100644 --- a/src/content/docs/learning-paths/secure-your-email/enable-auto-moves/configure-auto-moves.mdx +++ b/src/content/docs/learning-paths/secure-your-email/enable-auto-moves/configure-auto-moves.mdx @@ -10,7 +10,7 @@ products: To configure auto-move events: -1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/). +1. Log in to [Cloudflare One](https://dash.cloudflare.com/one/). 2. Select **Email security**. 3. Select **Settings**. 4. Select **Moves**. diff --git a/src/content/docs/learning-paths/secure-your-email/get-started/setup-google-workspace.mdx b/src/content/docs/learning-paths/secure-your-email/get-started/setup-google-workspace.mdx index 28bf9247f9c..9a30687dbeb 100644 --- a/src/content/docs/learning-paths/secure-your-email/get-started/setup-google-workspace.mdx +++ b/src/content/docs/learning-paths/secure-your-email/get-started/setup-google-workspace.mdx @@ -8,7 +8,7 @@ products: - email-security --- -1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/). +1. Log in to [Cloudflare One](https://dash.cloudflare.com/one/). 2. Select **Email security** > **Settings**. 3. Select **Connect an integration**, choose **Google Workspace CASB + EMAIL**, then select **Select Integration**. 4. Follow the wizard to create an integration, then select **Create Integration**. Refer to [Enable Gmail BCC integration](/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/enable-gmail-integration/) for further instructions. \ No newline at end of file diff --git a/src/content/docs/learning-paths/secure-your-email/get-started/setup-ms-graph-api.mdx b/src/content/docs/learning-paths/secure-your-email/get-started/setup-ms-graph-api.mdx index 447dea2119c..3b8f4cd1801 100644 --- a/src/content/docs/learning-paths/secure-your-email/get-started/setup-ms-graph-api.mdx +++ b/src/content/docs/learning-paths/secure-your-email/get-started/setup-ms-graph-api.mdx @@ -8,11 +8,11 @@ products: - email-security --- -1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/). +1. Log in to [Cloudflare One](https://dash.cloudflare.com/one/). 2. Select **Email security** > **Settings**. 3. Select **Connect an integration**, choose **Microsoft CASB + EMAIL**, then select **Select Integration**. 4. Enable **Microsoft Integration**: - 1. **Configure policy**: Choose how you wannt [CASB](/cloudflare-one/cloud-and-saas-findings/) to access the data from your integration. + 1. **Configure policy**: Choose how you wannt [CASB](/cloudflare-one/cloud-and-saas-findings/) to access the data from your integration. 2. **Name integration**: Add your integration name, then select **Continue**. 3. **Authorize integration**: - Select **Authorize**. Selecting **Authorize** will take you to the Microsoft Sign in page where you will have to enter your email address. diff --git a/src/content/docs/learning-paths/secure-your-email/monitor-your-inbox/index.mdx b/src/content/docs/learning-paths/secure-your-email/monitor-your-inbox/index.mdx index 99194b1606d..1efb1107d58 100644 --- a/src/content/docs/learning-paths/secure-your-email/monitor-your-inbox/index.mdx +++ b/src/content/docs/learning-paths/secure-your-email/monitor-your-inbox/index.mdx @@ -10,7 +10,7 @@ products: To access an overview of your account, the total number of emails processed, a breakdown of types of threads detected, and other useful information: -1. Log in to [Zero Trust.](https://one.dash.cloudflare.com/) +1. Log in to [Zero Trust.](https://dash.cloudflare.com/one/) 2. Select **Email security**. Under **Email security**, select **Monitoring**. diff --git a/src/content/docs/load-balancing/private-network/public-to-tunnel.mdx b/src/content/docs/load-balancing/private-network/public-to-tunnel.mdx index 8a3d3bb1002..5632401462e 100644 --- a/src/content/docs/load-balancing/private-network/public-to-tunnel.mdx +++ b/src/content/docs/load-balancing/private-network/public-to-tunnel.mdx @@ -25,7 +25,7 @@ The specific configuration steps can vary depending on your infrastructure and s To create a virtual network: -1. Within the [Zero Trust dashboard](https://one.dash.cloudflare.com), go to **Settings** > **WARP Client** and find the **Virtual networks** setting. +1. Within the [Zero Trust dashboard](https://dash.cloudflare.com/one/), go to **Settings** > **WARP Client** and find the **Virtual networks** setting. 2. Select **Add new** or **Manage** > **Create virtual network** to create virtual networks. 3. Define your virtual network name and select **Save**. diff --git a/src/content/docs/load-balancing/private-network/warp-to-tunnel.mdx b/src/content/docs/load-balancing/private-network/warp-to-tunnel.mdx index 1cc329e0f44..e20838b145f 100644 --- a/src/content/docs/load-balancing/private-network/warp-to-tunnel.mdx +++ b/src/content/docs/load-balancing/private-network/warp-to-tunnel.mdx @@ -133,7 +133,7 @@ After completing the setup, you will be redirected to the Load Balancing dashboa In order for Cloudflare One Clients to connect to your load balancer, the load balancer's IP address must route through the WARP tunnel in your [Split Tunnel settings](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/). -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Team & Resources** > **Device profiles**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Team & Resources** > **Device profiles**. 2. Find the [device profile](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/device-profiles/) you would like to modify and select **Edit**. 3. Under **Split Tunnels**, check whether your [Split Tunnels mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/#change-split-tunnels-mode) is set to **Exclude** or **Include**. 4. Select **Manage**. Depending on the mode: @@ -149,7 +149,7 @@ Cloudflare One Client traffic can now reach your private load balancer. For exam If you want your load balancer and its endpoints to be transparently accessible to users via a hostname, you can create a Gateway DNS [Override policy](/cloudflare-one/traffic-policies/dns-policies/#override) that maps the hostname to the load balancer's IP address. This ensures that traffic destined for the hostname resolves to the correct IP. -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Traffic policies** > **Firewall policies**> **DNS**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Traffic policies** > **Firewall policies**> **DNS**. 2. Select **Add a policy**. 3. In **Traffic**, create an expression where the **Selector** equals `Host`, the **Operator** equals `is`, and **Value** is the hostname you wish to associate with your load balancer. For example, diff --git a/src/content/docs/pages/platform/known-issues.mdx b/src/content/docs/pages/platform/known-issues.mdx index 1c5abd5f593..d87848337c6 100644 --- a/src/content/docs/pages/platform/known-issues.mdx +++ b/src/content/docs/pages/platform/known-issues.mdx @@ -81,7 +81,7 @@ At this step, your `*.pages.dev` domain has been secured behind Access. To resec If you have a custom domain and protected your `*.pages.dev` domain behind Access, you must: -10. Select **Add an application** > **Self hosted** in [Cloudflare Zero Trust](https://one.dash.cloudflare.com/). +10. Select **Add an application** > **Self hosted** in [Cloudflare Zero Trust](https://dash.cloudflare.com/one/). 11. Input an **Application name** and select your custom domain from the _Domain_ dropdown menu. 12. Select **Next** and configure your access rules to define who can reach the Access authentication page. 13. Select **Add application**. diff --git a/src/content/docs/r2/tutorials/cloudflare-access.mdx b/src/content/docs/r2/tutorials/cloudflare-access.mdx index 9c111e3c569..f1b5ec76fac 100644 --- a/src/content/docs/r2/tutorials/cloudflare-access.mdx +++ b/src/content/docs/r2/tutorials/cloudflare-access.mdx @@ -39,7 +39,7 @@ If you have not configured Cloudflare Access before, we recommend: To create an Access application for your R2 bucket: -1. Go to [**Access**](https://one.dash.cloudflare.com/?to=/:account/access/apps) and select **Add an application** +1. Go to [**Access**](https://dash.cloudflare.com/?to=/:account/one/access-controls/apps/self-hosted/add) and select **Add an application** 2. Select **Self-hosted**. 3. Enter an **Application name**. 4. Select **Add a public hostname** and enter the application domain. The **Domain** must be a domain hosted on Cloudflare, and the **Subdomain** part of the custom domain you will connect to your R2 bucket. For example, if you want to serve files from `behind-access.example.com` and `example.com` is a domain within your Cloudflare account, then enter `behind-access` in the subdomain field and select `example.com` from the **Domain** list. diff --git a/src/content/docs/reference-architecture/architectures/sase.mdx b/src/content/docs/reference-architecture/architectures/sase.mdx index 737fee4c2b7..236591d8b00 100644 --- a/src/content/docs/reference-architecture/architectures/sase.mdx +++ b/src/content/docs/reference-architecture/architectures/sase.mdx @@ -684,7 +684,7 @@ The dashboard shows a comprehensive summary of the entire device fleet, displayi Having acquired a comprehensive understanding of Cloudflare's SASE platform, you are now well-equipped to integrate it with existing infrastructure. This system efficiently secures access to applications for both employees and external users, starting from the initial request on the device and extending across every network to the application, regardless of its location. This powerful new model for securing networks, applications, devices, and users is built on the massive Cloudflare network and managed through an intuitive management interface. -It's worth noting that many of the capabilities described in this document can be used for free, without any time constraints, for up to 50 users. [Sign up](https://dash.cloudflare.com/sign-up) for an account and head to the [Cloudflare One](https://one.dash.cloudflare.com/) section. While this document has provided an overview of the platform as a whole, for those interested in delving deeper into specific areas, we recommend exploring the following resources. +It's worth noting that many of the capabilities described in this document can be used for free, without any time constraints, for up to 50 users. [Sign up](https://dash.cloudflare.com/sign-up) for an account and head to the [Cloudflare One](https://dash.cloudflare.com/one/) section. While this document has provided an overview of the platform as a whole, for those interested in delving deeper into specific areas, we recommend exploring the following resources. | Topic | Content | | ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | diff --git a/src/content/docs/security-center/indicator-feeds.mdx b/src/content/docs/security-center/indicator-feeds.mdx index 9b98b96dd29..1edaed4a758 100644 --- a/src/content/docs/security-center/indicator-feeds.mdx +++ b/src/content/docs/security-center/indicator-feeds.mdx @@ -135,7 +135,7 @@ Providers can create and manage a Custom Indicator Feed with the [Custom Indicat Once an account is granted access to a feed, it will be available to match traffic as a [selector in Gateway DNS policies](/cloudflare-one/traffic-policies/dns-policies/#indicator-feeds). -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Traffic policies** > **Firewall policies**. Select **DNS**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Traffic policies** > **Firewall policies**. Select **DNS**. 2. To create a new DNS policy, select **Add a policy**. 3. Name your policy. 4. In **Traffic**, add a condition with the **Indicator Feeds** selector. If your account has been granted access to a Custom Indicator Feed, Gateway will list the feed in **Value**. For example, you can block sites that appear in a feed: diff --git a/src/content/partials/cloudflare-one/access/add-infrastructure-app.mdx b/src/content/partials/cloudflare-one/access/add-infrastructure-app.mdx index 9f4e07530cf..b25b20b70d7 100644 --- a/src/content/partials/cloudflare-one/access/add-infrastructure-app.mdx +++ b/src/content/partials/cloudflare-one/access/add-infrastructure-app.mdx @@ -13,7 +13,7 @@ import { -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Access controls** > **Applications**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Access controls** > **Applications**. 2. Select **Add an application**. 3. Select **Infrastructure**. 4. Enter any name for the application. diff --git a/src/content/partials/cloudflare-one/access/add-mtls-cert.mdx b/src/content/partials/cloudflare-one/access/add-mtls-cert.mdx index caf3fa6187e..07c29549f48 100644 --- a/src/content/partials/cloudflare-one/access/add-mtls-cert.mdx +++ b/src/content/partials/cloudflare-one/access/add-mtls-cert.mdx @@ -3,7 +3,7 @@ params: - product --- -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Access controls** > **Service credentials** > **Mutual TLS**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Access controls** > **Service credentials** > **Mutual TLS**. 2. Select **Add mTLS Certificate**. diff --git a/src/content/partials/cloudflare-one/access/add-target.mdx b/src/content/partials/cloudflare-one/access/add-target.mdx index 51c02dd8617..1a4a080688b 100644 --- a/src/content/partials/cloudflare-one/access/add-target.mdx +++ b/src/content/partials/cloudflare-one/access/add-target.mdx @@ -16,7 +16,7 @@ To create a new target:

) : -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Access controls** > **Targets**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Access controls** > **Targets**. 2. Select **Add a target**. 3. In **Target hostname**, enter a user-friendly name for the target. We recommend using the server hostname, for example `production-server`. The target hostname does not need to be unique and can be reused for multiple targets. Hostnames are used to define the targets secured by an Access application; they are not used for DNS address resolution.
diff --git a/src/content/partials/cloudflare-one/access/app-launcher.mdx b/src/content/partials/cloudflare-one/access/app-launcher.mdx index 84940f7989a..d291e86e851 100644 --- a/src/content/partials/cloudflare-one/access/app-launcher.mdx +++ b/src/content/partials/cloudflare-one/access/app-launcher.mdx @@ -18,7 +18,7 @@ By default, the App Launcher is disabled. To enable it, you must configure a pol To enable the App Launcher: -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Access controls** > **Access settings**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Access controls** > **Access settings**. 2. Under the **Manage your App Launcher** card, select **Manage**. @@ -36,7 +36,7 @@ Tiles have a one-to-one relationship with each application you create in Access. To show an Access application in the App Launcher: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Access controls** > **Applications**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Access controls** > **Applications**. 2. Select an application and select **Configure**. 3. Go to **Experience settings**. 4. Select **Show application in App Launcher**. The App Launcher link will only appear for users who are allowed by your Access policies. Blocked users will not see the app in their App Launcher. diff --git a/src/content/partials/cloudflare-one/access/block-page.mdx b/src/content/partials/cloudflare-one/access/block-page.mdx index 451aad660bb..868da6cbb40 100644 --- a/src/content/partials/cloudflare-one/access/block-page.mdx +++ b/src/content/partials/cloudflare-one/access/block-page.mdx @@ -31,7 +31,7 @@ Only available on Pay-as-you-go and Enterprise plans. To create a custom block page for Access: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Reusable components** > **Custom pages**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Reusable components** > **Custom pages**. 2. Find the **Access Custom Pages** setting and select **Manage**. diff --git a/src/content/partials/cloudflare-one/access/bookmarks.mdx b/src/content/partials/cloudflare-one/access/bookmarks.mdx index 82b8d8655a1..ace621c064a 100644 --- a/src/content/partials/cloudflare-one/access/bookmarks.mdx +++ b/src/content/partials/cloudflare-one/access/bookmarks.mdx @@ -7,7 +7,7 @@ With Cloudflare One, you can show applications on the [App Launcher](/cloudflare Links to applications not protected by Access can be added as bookmarks. You can assign [Access policies](/cloudflare-one/access-controls/policies/) to control which users see the bookmark in the App Launcher. Users who do not match an Allow policy will not see the bookmark tile. Unlike policies for other Access application types, bookmark policies only affect visibility in the App Launcher and do not control access to the destination URL. -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Access controls** > **Applications**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Access controls** > **Applications**. 2. Select **Add an application** > **Bookmark**. diff --git a/src/content/partials/cloudflare-one/access/create-linked-app-token-policy.mdx b/src/content/partials/cloudflare-one/access/create-linked-app-token-policy.mdx index d002b0f749d..e46f6930970 100644 --- a/src/content/partials/cloudflare-one/access/create-linked-app-token-policy.mdx +++ b/src/content/partials/cloudflare-one/access/create-linked-app-token-policy.mdx @@ -13,7 +13,7 @@ import { Tabs, TabItem, APIRequest, Code } from "~/components"; -1. In the [Cloudflare dashboard](https://one.dash.cloudflare.com), go to **Zero Trust** > **Access controls** > **Applications**. +1. In the [Cloudflare dashboard](https://dash.cloudflare.com/one/), go to **Zero Trust** > **Access controls** > **Applications**. 2. Select {props.downstreamAppLabel} and select **Edit**. 3. Go to the **Policies** tab and select **Create new policy**. 4. Set the policy **Action** to _Service Auth_. diff --git a/src/content/partials/cloudflare-one/access/create-service-token.mdx b/src/content/partials/cloudflare-one/access/create-service-token.mdx index 166f4b605ef..65bffb2eb45 100644 --- a/src/content/partials/cloudflare-one/access/create-service-token.mdx +++ b/src/content/partials/cloudflare-one/access/create-service-token.mdx @@ -7,7 +7,7 @@ import { Tabs, TabItem, Details, APIRequest } from '~/components'; -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Access controls** > **Service credentials** > **Service Tokens**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Access controls** > **Service credentials** > **Service Tokens**. 2. Select **Create Service Token**. diff --git a/src/content/partials/cloudflare-one/access/enable-scim-on-dashboard.mdx b/src/content/partials/cloudflare-one/access/enable-scim-on-dashboard.mdx index 8e7c7b436bd..442ed19645e 100644 --- a/src/content/partials/cloudflare-one/access/enable-scim-on-dashboard.mdx +++ b/src/content/partials/cloudflare-one/access/enable-scim-on-dashboard.mdx @@ -6,7 +6,7 @@ params: import { Markdown } from "~/components" -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Integrations** > **Identity providers**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Integrations** > **Identity providers**. 2. Find the {props.idp} integration and select **Edit**. diff --git a/src/content/partials/cloudflare-one/access/idp-integration.mdx b/src/content/partials/cloudflare-one/access/idp-integration.mdx index 0b585e38a59..abeaf807005 100644 --- a/src/content/partials/cloudflare-one/access/idp-integration.mdx +++ b/src/content/partials/cloudflare-one/access/idp-integration.mdx @@ -2,11 +2,11 @@ {} --- -import {Render, Tabs, TabItem} from "~/components" +import { Render, Tabs, TabItem } from "~/components" -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Integrations** > **Identity providers**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Integrations** > **Identity providers**. 2. In the **Your identity providers** card, select **Add new identity provider**. diff --git a/src/content/partials/cloudflare-one/access/login-page.mdx b/src/content/partials/cloudflare-one/access/login-page.mdx index 08bbebc719c..5409df2f3f9 100644 --- a/src/content/partials/cloudflare-one/access/login-page.mdx +++ b/src/content/partials/cloudflare-one/access/login-page.mdx @@ -4,7 +4,7 @@ To change the appearance of your login page: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Reusable components** > **Custom pages**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Reusable components** > **Custom pages**. 2. Find the **Access login page** setting and select **Manage**. diff --git a/src/content/partials/cloudflare-one/access/modify-gateway-policy-precedence.mdx b/src/content/partials/cloudflare-one/access/modify-gateway-policy-precedence.mdx index d3c39dfe6df..7224f128843 100644 --- a/src/content/partials/cloudflare-one/access/modify-gateway-policy-precedence.mdx +++ b/src/content/partials/cloudflare-one/access/modify-gateway-policy-precedence.mdx @@ -8,7 +8,7 @@ By default, Cloudflare will evaluate Access application policies after evaluatin
  1. -In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Traffic policies** > **Firewall policies**. In **Network**, [create a Network policy](/cloudflare-one/traffic-policies/network-policies/) with the following configuration: +In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Traffic policies** > **Firewall policies**. In **Network**, [create a Network policy](/cloudflare-one/traffic-policies/network-policies/) with the following configuration: | Selector | Operator | Value | Action | | ---------------------------- | -------- | --------- | ------ | diff --git a/src/content/partials/cloudflare-one/access/okta-zt-steps.mdx b/src/content/partials/cloudflare-one/access/okta-zt-steps.mdx index 3a4c76a6a09..486389e9d21 100644 --- a/src/content/partials/cloudflare-one/access/okta-zt-steps.mdx +++ b/src/content/partials/cloudflare-one/access/okta-zt-steps.mdx @@ -4,7 +4,7 @@ import {} from "~/components"; -11. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Integrations** > **Identity providers**. +11. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Integrations** > **Identity providers**. 12. Under **Your identity providers**, select **Add new identity provider**. Select **Okta** as your identity provider. @@ -14,11 +14,11 @@ import {} from "~/components"; - **Client secret**: Enter your Okta client secret. - **Okta account URL**: Enter your [Okta domain](https://developer.okta.com/docs/guides/find-your-domain/main/), for example `https://my-company.okta.com`. -14. (Optional) Create an Okta API token and enter it in [Cloudflare One](https://one.dash.cloudflare.com/) (the token can be read-only). This will prevent your Okta groups from failing if you have more than 100 groups. +14. (Optional) Create an Okta API token and enter it in [Cloudflare One](https://dash.cloudflare.com/one/) (the token can be read-only). This will prevent your Okta groups from failing if you have more than 100 groups. 15. (Optional) To configure [custom OIDC claims](/cloudflare-one/integrations/identity-providers/generic-oidc/#custom-oidc-claims): 1. In Okta, create a [custom authorization server](https://developer.okta.com/docs/guides/customize-authz-server/main/) and ensure that the `groups` scope is enabled. - 2. In [Cloudflare One](https://one.dash.cloudflare.com/), enter the **Authorization Server ID** obtained from Okta. + 2. In [Cloudflare One](https://dash.cloudflare.com/one/), enter the **Authorization Server ID** obtained from Okta. 3. Under **Optional configurations**, enter the claims that you wish to add to your users' identity. 16. (Optional) Enable [Proof of Key Exchange (PKCE)](https://www.oauth.com/oauth2-servers/pkce/). PKCE will be performed on all login attempts. diff --git a/src/content/partials/cloudflare-one/access/rule-group.mdx b/src/content/partials/cloudflare-one/access/rule-group.mdx index 6057108aa95..73fea4ef08c 100644 --- a/src/content/partials/cloudflare-one/access/rule-group.mdx +++ b/src/content/partials/cloudflare-one/access/rule-group.mdx @@ -8,7 +8,7 @@ To create an Access rule group: -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Access controls** > **Policies**, and select the **Rule groups** tab. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Access controls** > **Policies**, and select the **Rule groups** tab. 2. Select **Add a group**. 3. Enter a name for the group (for example, `Lisbon-team`). 4. Specify as many rules as needed to define your user group. For example, the following rules define a team based in Lisbon, Portugal: diff --git a/src/content/partials/cloudflare-one/access/secure-private-apps-shared-steps.mdx b/src/content/partials/cloudflare-one/access/secure-private-apps-shared-steps.mdx index 8ae55814e6e..cf57fe968f9 100644 --- a/src/content/partials/cloudflare-one/access/secure-private-apps-shared-steps.mdx +++ b/src/content/partials/cloudflare-one/access/secure-private-apps-shared-steps.mdx @@ -48,7 +48,7 @@ The dashboard confirms that your application is available and protected behind C 3. Select **Send me a code**. 4. Enter the code from your email and select **Sign in**. -- **Explore more with Zero Trust**: Review your applications, policies, and tunnels in the [Cloudflare One dashboard](https://one.dash.cloudflare.com). +- **Explore more with Zero Trust**: Review your applications, policies, and tunnels in the [Cloudflare One dashboard](https://dash.cloudflare.com/one/). - **Configure an identity provider**: Replace email one-time PINs with your organization's identity provider for a seamless login experience. For more information, refer to [Identity providers](/cloudflare-one/integrations/identity-providers/). For in-depth guidance on clientless access, refer to the [Clientless access learning path](/learning-paths/clientless-access/concepts/what-is-clientless-access/). diff --git a/src/content/partials/cloudflare-one/access/self-hosted-app/create-app.mdx b/src/content/partials/cloudflare-one/access/self-hosted-app/create-app.mdx index 031d341c3f3..424fec782c9 100644 --- a/src/content/partials/cloudflare-one/access/self-hosted-app/create-app.mdx +++ b/src/content/partials/cloudflare-one/access/self-hosted-app/create-app.mdx @@ -6,7 +6,7 @@ params: import { Render } from "~/components" -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Access controls** > **Applications**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Access controls** > **Applications**. 2. Select **Add an application**. diff --git a/src/content/partials/cloudflare-one/access/tags.mdx b/src/content/partials/cloudflare-one/access/tags.mdx index d23d8d11816..fce319db570 100644 --- a/src/content/partials/cloudflare-one/access/tags.mdx +++ b/src/content/partials/cloudflare-one/access/tags.mdx @@ -9,7 +9,7 @@ You can label an Access application with up to 25 custom tags. End users can the To create a new tag: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Reusable components** > **Tags**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Reusable components** > **Tags**. 2. Select **Add a tag**. 3. Enter up to 35 alphanumeric characters for the tag (for example, `Human Resources`) and select it in the dropdown menu. 4. Select **Save**. @@ -20,7 +20,7 @@ You can now [add this tag](#tag-an-access-application) to an Access application. To add a tag to an existing Access application: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Access controls** > **Applications**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Access controls** > **Applications**. 2. Select an application and select **Configure**. 3. Go to **Experience settings**. 4. In the **Tags** dropdown, select the tags that you would like to assign to this application. The tag must be [created](#create-a-tag) before you can select it in the dropdown. diff --git a/src/content/partials/cloudflare-one/app-library-review-apps.mdx b/src/content/partials/cloudflare-one/app-library-review-apps.mdx index a5b31cbce6d..ab7bdaefcae 100644 --- a/src/content/partials/cloudflare-one/app-library-review-apps.mdx +++ b/src/content/partials/cloudflare-one/app-library-review-apps.mdx @@ -15,7 +15,7 @@ To organize applications into their approval status for your organization, you c To set the status of an application: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Team & Resources** > **Applications**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Team & Resources** > **Applications**. 2. Locate the card for the application. 3. In the three-dot menu, select the option to mark your desired status. diff --git a/src/content/partials/cloudflare-one/casb/aws-compute-account.mdx b/src/content/partials/cloudflare-one/casb/aws-compute-account.mdx index c4c2c368508..8199b33a1de 100644 --- a/src/content/partials/cloudflare-one/casb/aws-compute-account.mdx +++ b/src/content/partials/cloudflare-one/casb/aws-compute-account.mdx @@ -4,7 +4,7 @@ To connect a compute account to your AWS integration: -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Cloud & SaaS findings** > **Integrations**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Cloud & SaaS findings** > **Integrations**. 2. Find and select your AWS integration. 3. Select **Open connection instructions**. 4. Follow the instructions provided to connect a new compute account. diff --git a/src/content/partials/cloudflare-one/casb/manage-integrations.mdx b/src/content/partials/cloudflare-one/casb/manage-integrations.mdx index e4eec357f4d..d79e179beb8 100644 --- a/src/content/partials/cloudflare-one/casb/manage-integrations.mdx +++ b/src/content/partials/cloudflare-one/casb/manage-integrations.mdx @@ -10,7 +10,7 @@ Before you can integrate a SaaS application or cloud environment with CASB, your ### Add an integration -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Cloud & SaaS findings** > **Integrations**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Cloud & SaaS findings** > **Integrations**. 2. Select **Connect an integration** or **Add integration**. 3. Browse the available integrations and select the application you would like to add. 4. Follow the step-by-step integration instructions in the UI. @@ -22,7 +22,7 @@ Once CASB detects at least one finding, you can [view and manage your findings]( ### Pause an integration -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Cloud & SaaS findings** > **Integrations**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Cloud & SaaS findings** > **Integrations**. 2. Find the integration you would like to pause and select **Configure**. 3. To stop scanning the application, turn off **Scan for findings**. 4. Select **Save integration**. @@ -35,7 +35,7 @@ You can resume CASB scanning at any time by turning on **Scan for findings**. When you delete an integration, all keys and OAuth data will be deleted. This means you cannot restore a deleted integration or its scanned data. ::: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Cloud & SaaS findings** > **Integrations**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Cloud & SaaS findings** > **Integrations**. 2. Find the integration you would like to delete and select **Configure**. 3. Select **Disenroll**. diff --git a/src/content/partials/cloudflare-one/choose-team-name.mdx b/src/content/partials/cloudflare-one/choose-team-name.mdx index 0f8fc0491e9..1fb6e8e8e1a 100644 --- a/src/content/partials/cloudflare-one/choose-team-name.mdx +++ b/src/content/partials/cloudflare-one/choose-team-name.mdx @@ -2,10 +2,10 @@ import { GlossaryTooltip, DashButton } from "~/components"; 1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), select **Zero Trust**. - + 2. On the onboarding screen, choose a team name. The team name is a unique, internal identifier for your Zero Trust organization. Users will enter this team name when they enroll their device manually, and it will be the subdomain for your App Launcher (as relevant). Your business name is the typical entry. - You can find your team name in [Cloudflare One](https://one.dash.cloudflare.com) by going to **Settings**. + You can find your team name in [Cloudflare One](https://dash.cloudflare.com/one/) by going to **Settings**. 3. Complete your onboarding by selecting a subscription plan and entering your payment details. If you chose the **Zero Trust Free plan**, this step is still needed but you will not be charged. diff --git a/src/content/partials/cloudflare-one/clientless-browser-isolation.mdx b/src/content/partials/cloudflare-one/clientless-browser-isolation.mdx index fe7557d4765..40e1d89a4e0 100644 --- a/src/content/partials/cloudflare-one/clientless-browser-isolation.mdx +++ b/src/content/partials/cloudflare-one/clientless-browser-isolation.mdx @@ -3,5 +3,5 @@ --- -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Browser isolation** > **Browser isolation settings**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Browser isolation** > **Browser isolation settings**. 2. Turn on **Allow users to open a remote browser without the device client**. \ No newline at end of file diff --git a/src/content/partials/cloudflare-one/dex/http-test-create-steps.mdx b/src/content/partials/cloudflare-one/dex/http-test-create-steps.mdx index 708d43bafc7..6d6a15d3bad 100644 --- a/src/content/partials/cloudflare-one/dex/http-test-create-steps.mdx +++ b/src/content/partials/cloudflare-one/dex/http-test-create-steps.mdx @@ -1,6 +1,6 @@ To set up an HTTP test for an application: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Insights** > **Digital experience**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Insights** > **Digital experience**. 2. Select the **Tests** tab. 3. Select **Add a Test**. 4. Fill in the following fields: diff --git a/src/content/partials/cloudflare-one/dex/pcaps-download.mdx b/src/content/partials/cloudflare-one/dex/pcaps-download.mdx index d12598c7476..10e8e19d21a 100644 --- a/src/content/partials/cloudflare-one/dex/pcaps-download.mdx +++ b/src/content/partials/cloudflare-one/dex/pcaps-download.mdx @@ -2,7 +2,7 @@ {} --- -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **DEX** > **Remote captures**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **DEX** > **Remote captures**. 2. Find a successful capture. 3. Select the three-dot menu and select **Download**. diff --git a/src/content/partials/cloudflare-one/dex/pcaps-run.mdx b/src/content/partials/cloudflare-one/dex/pcaps-run.mdx index 65a8f00486b..8b32390f193 100644 --- a/src/content/partials/cloudflare-one/dex/pcaps-run.mdx +++ b/src/content/partials/cloudflare-one/dex/pcaps-run.mdx @@ -8,7 +8,7 @@ Devices must be actively connected to the Internet for remote captures to run. To capture data from a remote device: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **DEX** > **Remote captures**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **DEX** > **Remote captures**. 2. Select up to 10 devices that you want to run a capture on. Devices must be [registered](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/) in your Zero Trust organization. 3. Configure the types of captures to run. - **Packet captures (PCAP)**: Performs packet captures for traffic outside of the WARP tunnel (default network interface) and traffic inside of the WARP tunnel ([virtual interface](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/client-architecture/#ip-traffic)). diff --git a/src/content/partials/cloudflare-one/dex/pcaps-view-warp-diag.mdx b/src/content/partials/cloudflare-one/dex/pcaps-view-warp-diag.mdx index 079d435bdb3..40b1ed6763c 100644 --- a/src/content/partials/cloudflare-one/dex/pcaps-view-warp-diag.mdx +++ b/src/content/partials/cloudflare-one/dex/pcaps-view-warp-diag.mdx @@ -8,7 +8,7 @@ The diagnostics analyzer highlights what Cloudflare determines to be the most im To access the diagnostics analyzer: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **DEX** > **Remote captures**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **DEX** > **Remote captures**. 2. Locate an existing `warp-diag` log from the list or select **Run diagnostics** to generate a new `warp-diag` log. 3. Select the three dots for the `warp-diag` log that you want to analyze, then select **View Device Diag**. diff --git a/src/content/partials/cloudflare-one/email-security/domain-information.mdx b/src/content/partials/cloudflare-one/email-security/domain-information.mdx index 23143351441..98d60dccaf2 100644 --- a/src/content/partials/cloudflare-one/email-security/domain-information.mdx +++ b/src/content/partials/cloudflare-one/email-security/domain-information.mdx @@ -5,14 +5,14 @@ When you configure your domain, the Cloudflare dashboard will display you the fo - **MS Graph API**: Your current email provider is Microsoft 365, and Email security has been configured via the Microsoft Graph API. You do not need to change any MX record. - **BCC/Journaling**: You have chosen to set your email via BCC/Journaling. A copy of your email is sent to Cloudflare. - **MX/ Inline**: You have configured your email domain using MX/Inline. This configuration requires a [DNS record change](/dns/manage-dns-records/how-to/create-dns-records/#edit-dns-records). -- **Status**: Status indicates the state of the configuration. +- **Status**: Status indicates the state of the configuration. - For MX/Inline and BCC/Journaling, the dashboard will display **Active** if Email security has processed any email in the last seven days. The dashboard will display **No mail flow** if there has been no email activity in the last seven days. This is likely due to a misconfiguration. Refer to [Configuration checklist](/cloudflare-one/email-security/setup/#5-configuration-checklist) to ensure you have configured your environment correctly. - For MS Graph API, the dashboard will display **Active** if your integration has been successfully connected, and Email security can scan your inbox with the integration. The dashboard will display **Broken** if the API is not scanning emails. This could be due to a CASB misconfiguration. To troubleshoot this, refer to [Troubleshoot CASB](/cloudflare-one/cloud-and-saas-findings/troubleshoot-casb/). - **Service address**: This is the email address you will use to send a copy of your email. - **Source**: Depending on how you added the domains, the dashboard will display **MS integration**, **Google**, **CF zones**, or **Manual add**. - **Integration name**: Name of the integration. This field will only be displayed for Microsoft integrations. To rename your integration: - 1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/) > **Integrations** > **Cloud & SaaS**. + 1. Log in to [Cloudflare One](https://dash.cloudflare.com/one/) > **Integrations** > **Cloud & SaaS**. 2. Locate your integration, select **Configure**, then select **Edit**. - 3. Rename your integration, then select **Save**. + 3. Rename your integration, then select **Save**. - **Hops**: The number of hops. This will not be displayed if the configuration method is Microsoft Graph API. Hop count will be visible only if it has been configured. - **Date added**: Date when the domain was added. \ No newline at end of file diff --git a/src/content/partials/cloudflare-one/email-security/post-verification-setup.mdx b/src/content/partials/cloudflare-one/email-security/post-verification-setup.mdx index 0b8d43681a9..c5720986762 100644 --- a/src/content/partials/cloudflare-one/email-security/post-verification-setup.mdx +++ b/src/content/partials/cloudflare-one/email-security/post-verification-setup.mdx @@ -6,6 +6,6 @@ To verify that the deployment has been successful and that your emails are being scanned: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), select **Email security**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), select **Email security**. 2. Go to **Settings** > **Domain management** > **Domains**, then select **View**. 3. Under **Your domains**, locate your domain, and verify that **Status** (which describes the state of the configuration) displays **Active**. diff --git a/src/content/partials/cloudflare-one/intune-download-certificate.mdx b/src/content/partials/cloudflare-one/intune-download-certificate.mdx index 235dcb24ad3..7b6371f594c 100644 --- a/src/content/partials/cloudflare-one/intune-download-certificate.mdx +++ b/src/content/partials/cloudflare-one/intune-download-certificate.mdx @@ -7,4 +7,4 @@ You must deploy a [user-side certificate](/cloudflare-one/team-and-resources/dev 1. (Optional) Generate a [Cloudflare root certificate](/cloudflare-one/team-and-resources/devices/user-side-certificates/#generate-a-cloudflare-root-certificate). -2. In [Cloudflare One](https://one.dash.cloudflare.com), find and [download a root certificate](/cloudflare-one/team-and-resources/devices/user-side-certificates/manual-deployment/#download-a-cloudflare-root-certificate) in `.crt` format. +2. In [Cloudflare One](https://dash.cloudflare.com/one/), find and [download a root certificate](/cloudflare-one/team-and-resources/devices/user-side-certificates/manual-deployment/#download-a-cloudflare-root-certificate) in `.crt` format. diff --git a/src/content/partials/cloudflare-one/posture/add-service-provider.mdx b/src/content/partials/cloudflare-one/posture/add-service-provider.mdx index e9f9057f81c..c0e8097268a 100644 --- a/src/content/partials/cloudflare-one/posture/add-service-provider.mdx +++ b/src/content/partials/cloudflare-one/posture/add-service-provider.mdx @@ -5,7 +5,7 @@ params: import { Markdown } from "~/components"; -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Integrations** > **Service providers**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Integrations** > **Service providers**. 2. Select **Add new**. 3. Select **{props.provider}**. 4. Enter any name for the provider. This name will be used throughout the dashboard to reference this connection. diff --git a/src/content/partials/cloudflare-one/posture/configure-posture-check.mdx b/src/content/partials/cloudflare-one/posture/configure-posture-check.mdx index 4876c29f4e7..5201aa549f2 100644 --- a/src/content/partials/cloudflare-one/posture/configure-posture-check.mdx +++ b/src/content/partials/cloudflare-one/posture/configure-posture-check.mdx @@ -5,7 +5,7 @@ inputParameters: param1 import { Markdown } from "~/components" -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Reusable components** > **Posture checks** > **Service provider checks**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Reusable components** > **Posture checks** > **Service provider checks**. 2. Select **Add a check**. 3. Select the {props.one} provider. 4. Enter any name for the posture check. diff --git a/src/content/partials/cloudflare-one/send-risk-scores-okta.mdx b/src/content/partials/cloudflare-one/send-risk-scores-okta.mdx index 656b3c80b97..88f867525b4 100644 --- a/src/content/partials/cloudflare-one/send-risk-scores-okta.mdx +++ b/src/content/partials/cloudflare-one/send-risk-scores-okta.mdx @@ -5,7 +5,7 @@ First, configure Cloudflare One to send user risk scores to Okta. 1. Set up the [Okta SSO integration](/cloudflare-one/integrations/identity-providers/okta/). -2. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Integrations** > **Identity providers**. +2. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Integrations** > **Identity providers**. 3. In **Your identity providers**, locate your Okta integration and select **Edit**. 4. Turn on **Send risk score to Okta**. 5. Select **Save**. diff --git a/src/content/partials/cloudflare-one/tunnel/1033-error.mdx b/src/content/partials/cloudflare-one/tunnel/1033-error.mdx index 527ec929a01..7e1ac3f6dfe 100644 --- a/src/content/partials/cloudflare-one/tunnel/1033-error.mdx +++ b/src/content/partials/cloudflare-one/tunnel/1033-error.mdx @@ -7,6 +7,6 @@ import { Render } from "~/components"; A `1033` error indicates your tunnel is not connected to Cloudflare's network because Cloudflare's network cannot find a healthy `cloudflared` instance to receive the traffic. -First, review whether your tunnel is listed as `Active` on the [Cloudflare One](https://one.dash.cloudflare.com/) dashboard by going to **Networks** > **Connectors** > **Cloudflare Tunnels** or run `cloudflared tunnel list`. If the tunnel is not `Active`, review the following and take the action necessary for your tunnel status: +First, review whether your tunnel is listed as `Active` on the [Cloudflare One](https://dash.cloudflare.com/one/) dashboard by going to **Networks** > **Connectors** > **Cloudflare Tunnels** or run `cloudflared tunnel list`. If the tunnel is not `Active`, review the following and take the action necessary for your tunnel status: \ No newline at end of file diff --git a/src/content/partials/cloudflare-one/tunnel/connect-private-network.mdx b/src/content/partials/cloudflare-one/tunnel/connect-private-network.mdx index e7d6a0a5d43..3322f78d809 100644 --- a/src/content/partials/cloudflare-one/tunnel/connect-private-network.mdx +++ b/src/content/partials/cloudflare-one/tunnel/connect-private-network.mdx @@ -2,6 +2,6 @@ {} --- -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Networks** > **Connectors** > **Cloudflare Tunnels**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Networks** > **Connectors** > **Cloudflare Tunnels**. 2. [Create a new tunnel](/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel/) or edit an existing `cloudflared` tunnel. diff --git a/src/content/partials/cloudflare-one/tunnel/deployment-guides/cloud-create-tunnel.mdx b/src/content/partials/cloudflare-one/tunnel/deployment-guides/cloud-create-tunnel.mdx index 94251cd340c..fc78bb03b04 100644 --- a/src/content/partials/cloudflare-one/tunnel/deployment-guides/cloud-create-tunnel.mdx +++ b/src/content/partials/cloudflare-one/tunnel/deployment-guides/cloud-create-tunnel.mdx @@ -7,7 +7,7 @@ import { Markdown } from "~/components" Create a Cloudflare Tunnel in Cloudflare One and run the tunnel on the {props.one}. -1. Log in to [Cloudflare One](https://one.dash.cloudflare.com) and go to **Networks** > **Connectors** > **Cloudflare Tunnels**. +1. Log in to [Cloudflare One](https://dash.cloudflare.com/one/) and go to **Networks** > **Connectors** > **Cloudflare Tunnels**. 2. Select **Create a tunnel**. diff --git a/src/content/partials/cloudflare-one/tunnel/deployment-guides/cloud-private-ip.mdx b/src/content/partials/cloudflare-one/tunnel/deployment-guides/cloud-private-ip.mdx index 8f4320caa8d..69491c6dcbc 100644 --- a/src/content/partials/cloudflare-one/tunnel/deployment-guides/cloud-private-ip.mdx +++ b/src/content/partials/cloudflare-one/tunnel/deployment-guides/cloud-private-ip.mdx @@ -7,7 +7,7 @@ import SubtractIPCalculator from "~/components/SubtractIPCalculator.tsx"; [Private network routes](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/) allow users to connect to your {props.networkName} using the Cloudflare One Client. To add a private network route for your Cloudflare Tunnel: -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Networks** > **Routes**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Networks** > **Routes**. 2. In the **CIDR** tab, enter the **Private IP address** of your {props.resourceName} (for example, {props.exampleIp}). You can expand the IP range later if necessary. 3. In your [Split Tunnel configuration](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/#add-a-route), make sure the private IP is routing through the Cloudflare One Client. For example, if you are using Split Tunnels in **Exclude** mode, delete {props.splitTunnelCidr}. We recommend re-adding the IPs that are not explicitly used by your {props.resourceName}. diff --git a/src/content/partials/cloudflare-one/tunnel/deployment-guides/deploy-ansible.mdx b/src/content/partials/cloudflare-one/tunnel/deployment-guides/deploy-ansible.mdx index 150f4fad405..a3ece382cc2 100644 --- a/src/content/partials/cloudflare-one/tunnel/deployment-guides/deploy-ansible.mdx +++ b/src/content/partials/cloudflare-one/tunnel/deployment-guides/deploy-ansible.mdx @@ -305,7 +305,7 @@ Once you have created the configuration files, you can deploy them through Terra ``` {props.product === "cloudflare-one" ? ( -<>It may take several minutes for the GCP instance and tunnel to come online. You can view your new tunnel in Cloudflare One under Networks > Connectors > Cloudflare Tunnels. +<>It may take several minutes for the GCP instance and tunnel to come online. You can view your new tunnel in Cloudflare One under Networks > Connectors > Cloudflare Tunnels. ) : ( <>It may take several minutes for the GCP instance and tunnel to come online. You can view your new tunnel in the Cloudflare dashboard under Networking > Tunnels. )} diff --git a/src/content/partials/cloudflare-one/tunnel/deployment-guides/deploy-kubernetes.mdx b/src/content/partials/cloudflare-one/tunnel/deployment-guides/deploy-kubernetes.mdx index 08311a438ca..8635e68f41c 100644 --- a/src/content/partials/cloudflare-one/tunnel/deployment-guides/deploy-kubernetes.mdx +++ b/src/content/partials/cloudflare-one/tunnel/deployment-guides/deploy-kubernetes.mdx @@ -159,7 +159,7 @@ To create a Cloudflare Tunnel: <>
  2. Open a new browser tab and log in to{" "} - Cloudflare One. + Cloudflare One.
  3. Go to Networks > Connectors >{" "} diff --git a/src/content/partials/cloudflare-one/tunnel/logs/view-logs-dashboard.mdx b/src/content/partials/cloudflare-one/tunnel/logs/view-logs-dashboard.mdx index 34d000e3075..b22d26b0def 100644 --- a/src/content/partials/cloudflare-one/tunnel/logs/view-logs-dashboard.mdx +++ b/src/content/partials/cloudflare-one/tunnel/logs/view-logs-dashboard.mdx @@ -6,7 +6,7 @@ import { GlossaryTooltip } from "~/components"; Dashboard log streams are only available for remotely-managed tunnels. To stream tunnel logs from the dashboard: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Networks** > **Connectors** > **Cloudflare Tunnels**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Networks** > **Connectors** > **Cloudflare Tunnels**. 2. Select **View logs** next to the tunnel you want to monitor. 3. Select **Begin log stream**. @@ -14,6 +14,6 @@ Dashboard log streams are only available for -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Networks** > **Connectors** > **Cloudflare Tunnels**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Networks** > **Connectors** > **Cloudflare Tunnels**. 2. Choose a tunnel and select **Edit**. 3. Select the **Published application routes** tab. 4. Choose an application and select **Edit**. diff --git a/src/content/partials/cloudflare-one/tunnel/update-cloudflared.mdx b/src/content/partials/cloudflare-one/tunnel/update-cloudflared.mdx index 0b75864c6b4..85a8df51697 100644 --- a/src/content/partials/cloudflare-one/tunnel/update-cloudflared.mdx +++ b/src/content/partials/cloudflare-one/tunnel/update-cloudflared.mdx @@ -92,7 +92,7 @@ sudo systemctl restart cloudflared.service **If you created a remotely-managed tunnel using the dashboard:** -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Networks** > **Connectors** > **Cloudflare Tunnels**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Networks** > **Connectors** > **Cloudflare Tunnels**. 2. Select your tunnel and select **Edit**. 3. Select **Docker** and copy the installation command shown in the dashboard. The copied command will contain your token. 4. Paste this command into a terminal window. diff --git a/src/content/partials/cloudflare-one/users/remove-user-from-seat.mdx b/src/content/partials/cloudflare-one/users/remove-user-from-seat.mdx index a394b46799d..573a4ac1708 100644 --- a/src/content/partials/cloudflare-one/users/remove-user-from-seat.mdx +++ b/src/content/partials/cloudflare-one/users/remove-user-from-seat.mdx @@ -2,7 +2,7 @@ Removing a user from your Zero Trust Organization will free up the seat the user To remove a user from your Zero Trust Organization: -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Team & Resources** > **Users**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Team & Resources** > **Users**. 2. Select the checkbox next to a user with an **Active** status in the **Seat usage** column. 3. Select **Action** > **Remove users**. 4. Select **Remove**. diff --git a/src/content/partials/cloudflare-one/warp/add-split-tunnels-route.mdx b/src/content/partials/cloudflare-one/warp/add-split-tunnels-route.mdx index a87ea5f332b..e9a5cb4bc2d 100644 --- a/src/content/partials/cloudflare-one/warp/add-split-tunnels-route.mdx +++ b/src/content/partials/cloudflare-one/warp/add-split-tunnels-route.mdx @@ -7,7 +7,7 @@ import SubtractIPCalculator from "~/components/SubtractIPCalculator.tsx"; -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Team & Resources** > **Devices** > **Device profiles** > **General profiles**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Team & Resources** > **Devices** > **Device profiles** > **General profiles**. 2. Locate the [device profile](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/device-profiles/) you would like to modify and select **Configure**. 3. Under **Split Tunnels**, check whether your [Split Tunnels mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/#change-split-tunnels-mode) is set to **Exclude** or **Include**. 4. Select **Manage**. diff --git a/src/content/partials/cloudflare-one/warp/change-split-tunnels-mode.mdx b/src/content/partials/cloudflare-one/warp/change-split-tunnels-mode.mdx index 2b2811d3c47..8fa62e37c63 100644 --- a/src/content/partials/cloudflare-one/warp/change-split-tunnels-mode.mdx +++ b/src/content/partials/cloudflare-one/warp/change-split-tunnels-mode.mdx @@ -6,7 +6,7 @@ import { Tabs, TabItem } from "~/components"; -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Team & Resources** > **Devices** > **Device profiles** > **General profiles**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Team & Resources** > **Devices** > **Device profiles** > **General profiles**. 2. Locate the [device profile](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/device-profiles/) you would like to modify and select **Configure**. 3. Scroll down to **Split Tunnels**. 4. (Optional) To view your existing Split Tunnel configuration, select **Manage**. You will see a list of the IPs and domains Cloudflare Zero Trust excludes or includes, depending on the mode you have selected. We recommend making a copy of your Split Tunnel entries, as they will revert to the default upon switching modes. diff --git a/src/content/partials/cloudflare-one/warp/device-enrollment.mdx b/src/content/partials/cloudflare-one/warp/device-enrollment.mdx index 5465fbd833f..6dab765d25c 100644 --- a/src/content/partials/cloudflare-one/warp/device-enrollment.mdx +++ b/src/content/partials/cloudflare-one/warp/device-enrollment.mdx @@ -6,7 +6,7 @@ import { Tabs, TabItem } from "~/components"; -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Team & Resources** > **Devices** > **Device profiles** > **Management**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Team & Resources** > **Devices** > **Device profiles** > **Management**. 2. In **Device enrollment** > **Device enrollment permissions**, select **Manage**. 3. In the **Policies** tab, configure one or more [Access policies](/cloudflare-one/access-controls/policies/) to define who can join their device. For example, you could allow all users with a company email address: diff --git a/src/content/partials/cloudflare-one/warp/edit-profile-settings.mdx b/src/content/partials/cloudflare-one/warp/edit-profile-settings.mdx index f5ec88497d2..6405ba13e0e 100644 --- a/src/content/partials/cloudflare-one/warp/edit-profile-settings.mdx +++ b/src/content/partials/cloudflare-one/warp/edit-profile-settings.mdx @@ -4,7 +4,7 @@ import { Render } from "~/components"; -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Team & Resources** > **Devices** > **Device profiles** > **General profiles**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Team & Resources** > **Devices** > **Device profiles** > **General profiles**. 2. Locate the [device profile](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/device-profiles/) you would like to update and select **Configure**. 3. Use [selectors](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/device-profiles/#selectors) to add or adjust match rules, and modify [device client settings](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/settings/#device-settings) for this profile as needed. :::note diff --git a/src/content/partials/cloudflare-one/warp/view-local-domains.mdx b/src/content/partials/cloudflare-one/warp/view-local-domains.mdx index be45ec9ede5..cd6bc14b343 100644 --- a/src/content/partials/cloudflare-one/warp/view-local-domains.mdx +++ b/src/content/partials/cloudflare-one/warp/view-local-domains.mdx @@ -2,6 +2,6 @@ {} --- -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Team & Resources** > **Devices** > **Device profiles** > **General profiles**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Team & Resources** > **Devices** > **Device profiles** > **General profiles**. 2. Locate the [device profile](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/device-profiles/) you would like to view or modify and select **Configure**. 3. Scroll down to **Local Domain Fallback** and select **Manage**. diff --git a/src/content/partials/cloudflare-one/warp/vpn-ip-traffic.mdx b/src/content/partials/cloudflare-one/warp/vpn-ip-traffic.mdx index 09d8a94dc92..df9d23d1b6f 100644 --- a/src/content/partials/cloudflare-one/warp/vpn-ip-traffic.mdx +++ b/src/content/partials/cloudflare-one/warp/vpn-ip-traffic.mdx @@ -3,7 +3,7 @@ --- -Perform these steps in [Cloudflare One](https://one.dash.cloudflare.com/). +Perform these steps in [Cloudflare One](https://dash.cloudflare.com/one/). 1. Set your [Split Tunnels mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/#change-split-tunnels-mode) to **Exclude IPs and domains**. 2. [Add the following entries](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/#add-a-route) to your Split Tunnel Exclude list: diff --git a/src/content/partials/cloudflare-one/warp/warp-sessions-gateway.mdx b/src/content/partials/cloudflare-one/warp/warp-sessions-gateway.mdx index 49ffdc8056c..9f2062e491e 100644 --- a/src/content/partials/cloudflare-one/warp/warp-sessions-gateway.mdx +++ b/src/content/partials/cloudflare-one/warp/warp-sessions-gateway.mdx @@ -12,7 +12,7 @@ To configure a session timeout for a Gateway policy: -1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to either **Traffic policies** > **Firewall policies**. Choose either **Network** or **HTTP**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to either **Traffic policies** > **Firewall policies**. Choose either **Network** or **HTTP**. 2. Add a policy and select the _Allow_ action. Alternatively, choose any existing _Allow_ policy. 3. Under **Step 4 - Configure policy settings**, select **Edit** next to **Enforce Cloudflare One Client session duration**. 4. Enter a session expiration time in `1h30m0s` format and save. diff --git a/src/content/partials/learning-paths/zero-trust/create-zero-trust-org.mdx b/src/content/partials/learning-paths/zero-trust/create-zero-trust-org.mdx index 06372fec8de..57bc1993881 100644 --- a/src/content/partials/learning-paths/zero-trust/create-zero-trust-org.mdx +++ b/src/content/partials/learning-paths/zero-trust/create-zero-trust-org.mdx @@ -33,7 +33,7 @@ To add Zero Trust to your Terraform configuration: } ``` - Replace `` with the Zero Trust organization name selected during [onboarding](#sign-up-for-zero-trust). You can also view your team name on [Cloudflare One](https://one.dash.cloudflare.com) under **Settings** > **Team name and domain**. + Replace `` with the Zero Trust organization name selected during [onboarding](#sign-up-for-zero-trust). You can also view your team name on [Cloudflare One](https://dash.cloudflare.com/one/) under **Settings** > **Team name and domain**. You can now update Zero Trust organization settings using Terraform. diff --git a/src/content/partials/learning-paths/zero-trust/device-profiles.mdx b/src/content/partials/learning-paths/zero-trust/device-profiles.mdx index 7e92c7925c2..619b6e65e77 100644 --- a/src/content/partials/learning-paths/zero-trust/device-profiles.mdx +++ b/src/content/partials/learning-paths/zero-trust/device-profiles.mdx @@ -14,7 +14,7 @@ To customize the default settings: -1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Team & Resources** > **Devices** > **Device profiles** > **General profiles**. +1. In [Cloudflare One](https://dash.cloudflare.com/one/), go to **Team & Resources** > **Devices** > **Device profiles** > **General profiles**. 2. Select the **Default** profile and select **Edit*. diff --git a/src/content/partials/networking-services/analytics/traceroutes.mdx b/src/content/partials/networking-services/analytics/traceroutes.mdx index b8299a5be86..3fae4e25723 100644 --- a/src/content/partials/networking-services/analytics/traceroutes.mdx +++ b/src/content/partials/networking-services/analytics/traceroutes.mdx @@ -14,7 +14,7 @@ You can run traceroutes to analyze the hop-by-hop Internet path and latency betw text={` To run a traceroute from a specific Cloudflare data center to your network: -1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/) > **Insights**. +1. Log in to [Cloudflare One](https://dash.cloudflare.com/one/) > **Insights**. 2. Go to **Network health** > **WAN connector health**. 3. Find the tunnel for the traceroute. 4. Select the three dots > **Traceroute details**. diff --git a/src/content/partials/networking-services/cloudflare-wan/third-party/ubiquiti.mdx b/src/content/partials/networking-services/cloudflare-wan/third-party/ubiquiti.mdx index 8ef69b83eb2..6c37165f7b6 100644 --- a/src/content/partials/networking-services/cloudflare-wan/third-party/ubiquiti.mdx +++ b/src/content/partials/networking-services/cloudflare-wan/third-party/ubiquiti.mdx @@ -31,7 +31,7 @@ Connect a Ubiquiti UniFi Gateway to Cloudflare's network using Cloudflare WAN (f ) : ( Cloudflare One, and go to **Networks**. + text={`1. Log in to Cloudflare One, and go to **Networks**. 2. Go to **Connectors** > **Cloudflare WAN**, and select **Create**.`} inline={false} /> @@ -99,7 +99,7 @@ Connect a Ubiquiti UniFi Gateway to Cloudflare's network using Cloudflare WAN (f ) : ( Cloudflare One, and go to **Networks**. + text={`1. Log in to Cloudflare One, and go to **Networks**. 2. In **Cloudflare WAN**, find the IPsec tunnel you have just created.`} inline={false} /> @@ -129,7 +129,7 @@ Connect a Ubiquiti UniFi Gateway to Cloudflare's network using Cloudflare WAN (f ) : ( Cloudflare One, and go to **Networks**. + text={`1. Log in to Cloudflare One, and go to **Networks**. 2. Go to **Routes** > **WAN routes** > **Create**.`} inline={false} /> @@ -161,7 +161,7 @@ Wait a few minutes, then access both Cloudflare and UniFi to verify the tunnel's ) : ( Cloudflare One, and go to **Insights**. + text={`1. Log in to Cloudflare One, and go to **Insights**. 2. Go to **Network visibility** > **WAN connector health**. 3. Find the tunnel you have just created and make sure its status shows **Up**. Refer to [Check tunnel health in the dashboard](/cloudflare-one/networks/connectors/cloudflare-wan/configuration/common-settings/check-tunnel-health-dashboard/) for more information.`} inline={false} diff --git a/src/content/partials/networking-services/cloudflare-wan/zero-trust/warp.mdx b/src/content/partials/networking-services/cloudflare-wan/zero-trust/warp.mdx index c47c0470b7a..bc736533215 100644 --- a/src/content/partials/networking-services/cloudflare-wan/zero-trust/warp.mdx +++ b/src/content/partials/networking-services/cloudflare-wan/zero-trust/warp.mdx @@ -40,7 +40,7 @@ When connecting a device to Cloudflare WAN, you will have virtual IP addresses f Route packets back to Cloudflare One Client devices from services behind an anycast GRE or other type tunnel. Complete this configuration before installing WARP. Otherwise, your infrastructure will not route packets correctly to Cloudflare global network and connectivity will fail. -Cloudflare will assign IP addresses from the virtual IP (VIP) space to your devices. To view your virtual IP address, go to [Cloudflare One](https://one.dash.cloudflare.com/), and select **{props.ztDashPath}**. +Cloudflare will assign IP addresses from the virtual IP (VIP) space to your devices. To view your virtual IP address, go to [Cloudflare One](https://dash.cloudflare.com/one/), and select **{props.ztDashPath}**. All packets with a destination IP in the VIP space need to be routed back through the tunnel. For example, with a single GRE tunnel named `gre1`, in Linux, the following command would add a routing rule that would route such packets: diff --git a/src/content/partials/networking-services/mconn/configure-connectors.mdx b/src/content/partials/networking-services/mconn/configure-connectors.mdx index d9f3d01c6d0..9c020826733 100644 --- a/src/content/partials/networking-services/mconn/configure-connectors.mdx +++ b/src/content/partials/networking-services/mconn/configure-connectors.mdx @@ -346,7 +346,7 @@ To create a profile: { props.dashName === "CF1 Cloudflare WAN" && ( <>
      -
    1. Log in to Cloudflare One, and go to Networks.
      2. +
    2. Log in to Cloudflare One, and go to Networks.
    3. Go to Connectors > Appliances > Create a profile.
    @@ -580,7 +580,7 @@ When you are ready to connect your { props.magicWord === "virtual" ? props.produ <> Cloudflare One, and go to **Networks**. + 1. Log in to Cloudflare One, and go to **Networks**. 2. Go to **Connectors** > **Appliances**. 3. Find the ${ props.magicWord === "virtual" ? props.productNameVirtual : props.productName } you want to activate, select the three dots next to it > **Edit**. Make sure you verify the serial number to choose the right ${ props.magicWord === "virtual" ? props.productNameVirtual : props.productName } you want to activate. 4. In the new window, the **Status** dropdown will show as **Deactivated**. Select it to change the status to **Activated**. @@ -862,7 +862,7 @@ To check the IPsec tunnels and static routes created by your { props.magicWord = <> Cloudflare One, and go to **Connectors**. + 1. Log in to Cloudflare One, and go to **Connectors**. 2. In **Cloudflare WAN** you can inspect the IPsec tunnels created by your ${props.magicWord === "virtual" ? props.productNameVirtual : props.productName }. 3. In **Routes** you can inspect the static routes created by your ${props.magicWord === "virtual" ? props.productNameVirtual : props.productName }. diff --git a/src/content/partials/networking-services/mconn/maintenance/deactivate-connector.mdx b/src/content/partials/networking-services/mconn/maintenance/deactivate-connector.mdx index abb2c35e51b..ae64d928b6f 100644 --- a/src/content/partials/networking-services/mconn/maintenance/deactivate-connector.mdx +++ b/src/content/partials/networking-services/mconn/maintenance/deactivate-connector.mdx @@ -9,7 +9,7 @@ import { DashButton, Markdown } from '~/components'; <> Cloudflare One, and go to **Networks**. + 1. Log in to Cloudflare One, and go to **Networks**. 2. Go to **Connectors** > **Appliances** > **Appliances**. 3. Find the Cloudflare One Appliance you want to deactivate, select the three dots next to it > **Edit**. `} diff --git a/src/content/partials/networking-services/mconn/maintenance/edit-basic-info.mdx b/src/content/partials/networking-services/mconn/maintenance/edit-basic-info.mdx index b11277c02a7..73f2dffe3db 100644 --- a/src/content/partials/networking-services/mconn/maintenance/edit-basic-info.mdx +++ b/src/content/partials/networking-services/mconn/maintenance/edit-basic-info.mdx @@ -11,7 +11,7 @@ In **Basic information**, you can change the name and description of your Cloudf <> Cloudflare One, and go to **Networks**. + 1. Log in to Cloudflare One, and go to **Networks**. 2. Go to **Connectors** > **Appliances** > **Appliances**. `} inline={false} diff --git a/src/content/partials/networking-services/mconn/maintenance/edit-network-settings.mdx b/src/content/partials/networking-services/mconn/maintenance/edit-network-settings.mdx index f71c11c0de5..eb36962e049 100644 --- a/src/content/partials/networking-services/mconn/maintenance/edit-network-settings.mdx +++ b/src/content/partials/networking-services/mconn/maintenance/edit-network-settings.mdx @@ -9,7 +9,7 @@ import { DashButton, Markdown } from "~/components"; <> Cloudflare One, and go to **Networks**. + 1. Log in to Cloudflare One, and go to **Networks**. 2. Go to **Connectors** > **Appliances** > **Profiles**. `} inline={false} diff --git a/src/content/partials/networking-services/mconn/maintenance/edit-sites.mdx b/src/content/partials/networking-services/mconn/maintenance/edit-sites.mdx index 7a5e68df4e8..7f954264064 100644 --- a/src/content/partials/networking-services/mconn/maintenance/edit-sites.mdx +++ b/src/content/partials/networking-services/mconn/maintenance/edit-sites.mdx @@ -9,7 +9,7 @@ import { DashButton, Markdown } from "~/components"; <> Cloudflare One > **Insights**. + 1. Log in to Cloudflare One > **Insights**. 2. Go to **Network visibility** > **Traffic overview**, and find the site you want to make changes on. 3. Select the three dots next to it > **Edit**. 4. In **Basic information**, make changes to the site's name, description, and geographic coordinates. diff --git a/src/content/partials/networking-services/mconn/maintenance/edit-traffic-steering.mdx b/src/content/partials/networking-services/mconn/maintenance/edit-traffic-steering.mdx index 267156ca7a1..56892a5dfe7 100644 --- a/src/content/partials/networking-services/mconn/maintenance/edit-traffic-steering.mdx +++ b/src/content/partials/networking-services/mconn/maintenance/edit-traffic-steering.mdx @@ -11,7 +11,7 @@ You can only add or remove applications to Breakout traffic and Prioritized traf <> Cloudflare One, and go to **Networks**. + 1. Log in to Cloudflare One, and go to **Networks**. 2. Go to **Connectors** > **Appliances** > **Profiles**. `} inline={false} diff --git a/src/content/partials/networking-services/mconn/maintenance/heartbeat.mdx b/src/content/partials/networking-services/mconn/maintenance/heartbeat.mdx index c8f54f97a75..4c3267ed995 100644 --- a/src/content/partials/networking-services/mconn/maintenance/heartbeat.mdx +++ b/src/content/partials/networking-services/mconn/maintenance/heartbeat.mdx @@ -21,7 +21,7 @@ There are three symbols for the heartbeat signal that allow you to quickly check <> Cloudflare One, and go to **Networks**. + 1. Log in to Cloudflare One, and go to **Networks**. 2. Go to **Connectors** > **Appliances** > **Appliances**. 3. Find your Cloudflare One Appliance, and place your cursor over the icon on the **Status** column to check the timestamp. The timestamp displays the last time Cloudflare One Appliance successfully contacted Cloudflare. `} diff --git a/src/content/partials/networking-services/mconn/maintenance/interrupt-service-window.mdx b/src/content/partials/networking-services/mconn/maintenance/interrupt-service-window.mdx index b94efb16efe..5cebf3c8332 100644 --- a/src/content/partials/networking-services/mconn/maintenance/interrupt-service-window.mdx +++ b/src/content/partials/networking-services/mconn/maintenance/interrupt-service-window.mdx @@ -11,7 +11,7 @@ The Interrupt window defines when Cloudflare One Appliance (formerly Magic WAN C <> Cloudflare One, and go to **Networks** > **Connectors**. + 1. Log in to Cloudflare One, and go to **Networks** > **Connectors**. 2. In **Appliances** > **Appliances**, select the Cloudflare One Appliance for which you want to set up the update window > **Edit**. `} inline={false} diff --git a/src/content/partials/networking-services/mconn/maintenance/register-hardware-appliance.mdx b/src/content/partials/networking-services/mconn/maintenance/register-hardware-appliance.mdx index ad72dcbe7fe..fb37ca48ee8 100644 --- a/src/content/partials/networking-services/mconn/maintenance/register-hardware-appliance.mdx +++ b/src/content/partials/networking-services/mconn/maintenance/register-hardware-appliance.mdx @@ -11,7 +11,7 @@ To set up and use the hardware version of Cloudflare One Appliance (formerly Mag { props.dashName === "CF1 Cloudflare WAN" && ( <>
      -
    1. Log in to Cloudflare One, and go to Networks.
      2. +
    2. Log in to Cloudflare One, and go to Networks.
    3. Go to Connectors > Appliances, and select Register an appliance.
    diff --git a/src/content/partials/networking-services/mconn/maintenance/remove-connectors.mdx b/src/content/partials/networking-services/mconn/maintenance/remove-connectors.mdx index fa154fec8ac..dd64015465b 100644 --- a/src/content/partials/networking-services/mconn/maintenance/remove-connectors.mdx +++ b/src/content/partials/networking-services/mconn/maintenance/remove-connectors.mdx @@ -17,7 +17,7 @@ You can have more than one Cloudflare One Appliance in one profile if you initia <> Cloudflare One, and go to **Networks**. + 1. Log in to Cloudflare One, and go to **Networks**. 2. Go to **Connectors** > **Appliances** > **Profiles**. `} inline={false} @@ -52,7 +52,7 @@ To remove a Cloudflare One Appliance from your account: <> Cloudflare One, and go to **Networks**. + 1. Log in to Cloudflare One, and go to **Networks**. 2. Go to **Connectors** > **Appliances** > **Appliances**. `} inline={false} diff --git a/src/content/partials/networking-services/mconn/network-options/app-aware-policies/breakout-prioritized.mdx b/src/content/partials/networking-services/mconn/network-options/app-aware-policies/breakout-prioritized.mdx index 7eb868cf827..8964ad7c617 100644 --- a/src/content/partials/networking-services/mconn/network-options/app-aware-policies/breakout-prioritized.mdx +++ b/src/content/partials/networking-services/mconn/network-options/app-aware-policies/breakout-prioritized.mdx @@ -99,7 +99,7 @@ You need to configure {props.featureName} applications for each of your existing <> Cloudflare One dashboard, and go to **Networks**. + 1. Log in to the Cloudflare One dashboard, and go to **Networks**. 2. Go to **Connectors** > **Appliances** > **Profiles**. `} inline={false} @@ -228,7 +228,7 @@ The traffic for the application you chose ${props.whatHappensApp}. <> Cloudflare One dashboard, and go to **Networks**. + 1. Log in to the Cloudflare One dashboard, and go to **Networks**. 2. Go to **Connectors** > **Appliances** > **Profiles**. `} inline={false} @@ -333,7 +333,7 @@ To pin applications to a WAN port: <> Cloudflare One dashboard, and go to **Networks**. + 1. Log in to the Cloudflare One dashboard, and go to **Networks**. 2. Go to **Connectors** > **Appliances** > **Profiles**. 3. Select the Cloudflare One Appliance you want to configure > **Edit**. `} diff --git a/src/content/partials/networking-services/mconn/network-options/dhcp/dhcp-relay.mdx b/src/content/partials/networking-services/mconn/network-options/dhcp/dhcp-relay.mdx index a00df213960..7546367bc28 100644 --- a/src/content/partials/networking-services/mconn/network-options/dhcp/dhcp-relay.mdx +++ b/src/content/partials/networking-services/mconn/network-options/dhcp/dhcp-relay.mdx @@ -43,7 +43,7 @@ To configure DHCP relay: <> Cloudflare One, and go to **Networks**. + 1. Log in to Cloudflare One, and go to **Networks**. 2. Go to **Connectors** > **Appliances** > **Profiles**. `} inline={false} diff --git a/src/content/partials/networking-services/mconn/network-options/dhcp/dhcp-server.mdx b/src/content/partials/networking-services/mconn/network-options/dhcp/dhcp-server.mdx index 94056a78a61..c07ca66a126 100644 --- a/src/content/partials/networking-services/mconn/network-options/dhcp/dhcp-server.mdx +++ b/src/content/partials/networking-services/mconn/network-options/dhcp/dhcp-server.mdx @@ -13,7 +13,7 @@ When you use a static IP address, Cloudflare One Appliance (formerly Magic WAN C <> Cloudflare One, and go to **Networks**. + 1. Log in to Cloudflare One, and go to **Networks**. 2. Go to **Connectors** > **Appliances** > **Profiles**. `} inline={false} diff --git a/src/content/partials/networking-services/mconn/network-options/network-segmentation.mdx b/src/content/partials/networking-services/mconn/network-options/network-segmentation.mdx index 6243e2b3a08..e27ddf0e6db 100644 --- a/src/content/partials/networking-services/mconn/network-options/network-segmentation.mdx +++ b/src/content/partials/networking-services/mconn/network-options/network-segmentation.mdx @@ -52,7 +52,7 @@ Follow these steps to create a new LAN policy to segment your network. Only the <> Cloudflare One, and go to **Networks**. + 1. Log in to Cloudflare One, and go to **Networks**. 2. Go to **Connectors** > **Appliances** > **Profiles**. `} inline={false} @@ -203,7 +203,7 @@ The new policy will ensure that traffic between the specified LANs flows locally <> Cloudflare One, and go to **Networks**. + 1. Log in to Cloudflare One, and go to **Networks**. 2. Go to **Connectors** > **Appliances** > **Profiles**. `} inline={false} @@ -315,7 +315,7 @@ Example: <> Cloudflare One, and go to **Networks**. + 1. Log in to Cloudflare One, and go to **Networks**. 2. Go to **Connectors** > **Appliances** > **Profiles**. `} inline={false} diff --git a/src/content/partials/networking-services/mconn/troubleshooting/troubleshooting-steps.mdx b/src/content/partials/networking-services/mconn/troubleshooting/troubleshooting-steps.mdx index 17ad08b8a07..582301c228e 100644 --- a/src/content/partials/networking-services/mconn/troubleshooting/troubleshooting-steps.mdx +++ b/src/content/partials/networking-services/mconn/troubleshooting/troubleshooting-steps.mdx @@ -9,7 +9,7 @@ import { DashButton, Markdown } from "~/components"; <> Cloudflare One, and go to **Networks** > **Connectors**. + 1. Log in to Cloudflare One, and go to **Networks** > **Connectors**. 2. Go to **Appliances** > **Profiles**. 3. Select your Appliance > **View analytics**. `} diff --git a/src/content/partials/networking-services/routing/configure-routes.mdx b/src/content/partials/networking-services/routing/configure-routes.mdx index d5d624b230a..0d7438a225b 100644 --- a/src/content/partials/networking-services/routing/configure-routes.mdx +++ b/src/content/partials/networking-services/routing/configure-routes.mdx @@ -60,7 +60,7 @@ Refer to Traffic Steering for more infor <> Cloudflare One, and go to **Networks**. + 1. Log in to Cloudflare One, and go to **Networks**. 2. Go to **Routes** > **WAN Routes**, and select **Create** to add a new route. `} inline={false} @@ -429,7 +429,7 @@ To set this ASN: <> Cloudflare One, and go to **Networks**. + 1. Log in to Cloudflare One, and go to **Networks**. 2. Go to **Routes** > **WAN configuration**. 3. In **Border Gateway Protocol (BGP) configuration**, select **Edit** and enter your ASN. 4. Select **Save**. @@ -516,7 +516,7 @@ BGP over CNI is in closed beta and is not currently available to new customers. <> Cloudflare One, and go to **Networks**. + 1. Log in to Cloudflare One, and go to **Networks**. 2. Go to **Routes** > **WAN configuration**. 3. In **Border Gateway Protocol (BGP) configuration**, select **Edit ASN** and enter your ASN. 4. Go to **Networks** > **Connectors** > **Interconnects**. @@ -570,7 +570,7 @@ BGP over CNI is in closed beta and is not currently available to new customers. <> Cloudflare One, and go to **Networks**. + 1. Log in to Cloudflare One, and go to **Networks**. 2. Go to **Routes** > **WAN configuration**. 3. In **Border Gateway Protocol (BGP) configuration**, select **Edit ASN** and enter your ASN. 4. Go to **Networks** > **Connectors** > **Cloudflare WAN**. diff --git a/src/content/partials/networking-services/routing/configure-tunnels.mdx b/src/content/partials/networking-services/routing/configure-tunnels.mdx index 58348962311..bb68056a52d 100644 --- a/src/content/partials/networking-services/routing/configure-tunnels.mdx +++ b/src/content/partials/networking-services/routing/configure-tunnels.mdx @@ -92,7 +92,7 @@ Beyond GRE and IPsec tunnels, you can also use Network Interconnect (CNI) to onb <> Cloudflare One, and go to **Networks**. + 1. Log in to Cloudflare One, and go to **Networks**. 2. Go to **Connectors** > **Cloudflare WAN**, and select **Create**. 3. On the **Add Tunnel** page, choose either a **GRE tunnel** or **IPsec tunnel**. `} diff --git a/src/content/partials/networking-services/sites/sites.mdx b/src/content/partials/networking-services/sites/sites.mdx index e49acf781ff..441e997d4c6 100644 --- a/src/content/partials/networking-services/sites/sites.mdx +++ b/src/content/partials/networking-services/sites/sites.mdx @@ -25,7 +25,7 @@ Before creating a site, ensure you have set up at least one on-ramp. Then, follo <> **Network visibility**. 3. In **Network overview**, select **Add site**. 4. Add a name and description for your new site. Optionally, you can also add the geographical coordinates for your site in **Latitude** and **Longitude**. If you add geographical coordinates, your site's location will appear in the map once created. @@ -98,7 +98,7 @@ Your site is now set up. If you have other sites you need to set up, repeat the <> **Network visibility**. 3. In **Network overview** > **Traffic overview**, find your site > select the three dots in front of it > **Edit**. 4. Select **On-ramps**. diff --git a/src/content/partials/networking-services/tunnel-health/check-tunnel-healthchecks-dash.mdx b/src/content/partials/networking-services/tunnel-health/check-tunnel-healthchecks-dash.mdx index 33f16ff7be3..2e6a42d7821 100644 --- a/src/content/partials/networking-services/tunnel-health/check-tunnel-healthchecks-dash.mdx +++ b/src/content/partials/networking-services/tunnel-health/check-tunnel-healthchecks-dash.mdx @@ -26,7 +26,7 @@ Not all data centers are relevant to you at all times. You can refer to the **Tr <> **WAN connector health**. 3. In this view you can access a list of your tunnels and their current health status. You can also check the amount of health checks passed in the last hour as well as traffic volume for each tunnel. 4. Find the tunnel you want to inspect, select the three dots next to it, and choose: @@ -72,7 +72,7 @@ You can drill down into a specific tunnel to check its health status and other i <> **WAN connector health**. `} inline={false} diff --git a/src/content/partials/networking-services/tunnel-health/update-tunnel-health-checks-frequency.mdx b/src/content/partials/networking-services/tunnel-health/update-tunnel-health-checks-frequency.mdx index 62940d5dfcc..45e6ed0561a 100644 --- a/src/content/partials/networking-services/tunnel-health/update-tunnel-health-checks-frequency.mdx +++ b/src/content/partials/networking-services/tunnel-health/update-tunnel-health-checks-frequency.mdx @@ -96,7 +96,7 @@ The following example adjusts tunnel health check frequency to `low`. Note that ) : ( **Networks**. +1. Log in to [Cloudflare One](https://dash.cloudflare.com/one/) > **Networks**. 2. Go to **Connectors** > **Appliances**. 3. In **Profiles**, find the Connector profile you want to edit > select the three dots > **Edit**. 4. In **Network Configuration** > **WAN configuration** > select your WAN > **Edit**.