[CF1] Updating UI instructions for /cloudflare-one/connections/connect-devices/ (#26059)

Oxyjun · web-flow · commit bd451c801fe7 · 2025-10-24T18:24:10.000Z
* Adding files after ZT -&gt; CF1 UI instruction updates

* Adding more changes

* Minor fix

* More iterations
diff --git a/src/content/docs/cloudflare-one/team-and-resources/devices/agentless/dns/dns-over-tls.mdx b/src/content/docs/cloudflare-one/team-and-resources/devices/agentless/dns/dns-over-tls.mdx
@@ -15,8 +15,8 @@ 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 [Zero Trust](https://one.dash.cloudflare.com/), go to **Gateway** > **DNS locations**.
-2. [Add a new location](/cloudflare-one/team-and-resources/devices/agentless/dns/locations/) or select an existing location from the list.
+1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Networks** > **Resolvers & Proxies**.
+2. Under **DNS locations**, [add a new location](/cloudflare-one/team-and-resources/devices/agentless/dns/locations/) or select an existing location from the list.
 3. Under **DoT endpoint**, copy the value in **DoT addresses**.
 
 The DoT hostname contains your unique location name. For example, if the DoT hostname is `9y65g5srsm.cloudflare-gateway.com`, the location name is `9y65g5srsm`.
diff --git a/src/content/docs/cloudflare-one/team-and-resources/devices/agentless/dns/locations/dns-resolver-ips.mdx b/src/content/docs/cloudflare-one/team-and-resources/devices/agentless/dns/locations/dns-resolver-ips.mdx
@@ -9,8 +9,8 @@ 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 [Zero Trust](https://one.dash.cloudflare.com/), go to **Gateway** > **DNS locations**.
-2. Locate the DNS location, then select **Configure**.
+1. In [Cloudflare One](https://one.dash.cloudflare.com/), 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**.
 
 ## DNS query location matching
diff --git a/src/content/docs/cloudflare-one/team-and-resources/devices/agentless/pac-files.mdx b/src/content/docs/cloudflare-one/team-and-resources/devices/agentless/pac-files.mdx
@@ -29,7 +29,7 @@ Install a [Cloudflare certificate](/cloudflare-one/team-and-resources/devices/us
 
 ## 1. Generate a proxy endpoint
 
-You can generate a proxy endpoint on the Zero Trust dashboard or through the Cloudflare API.
+You can generate a proxy endpoint in Cloudflare One or through the Cloudflare API.
 
 :::caution
 All devices you add to the proxy endpoint will be able to access your Cloudflare Tunnel applications and services. If you only want to proxy web traffic, you can build a network policy that blocks those source IPs from connecting to your internal resources.
@@ -39,9 +39,9 @@ All devices you add to the proxy endpoint will be able to access your Cloudflare
 
 <TabItem label="Dashboard">
 
-1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **Gateway** > **Proxy endpoints**.
+1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Networks** > **Resolves & Proxies** > **Proxy endpoints**.
 
-2. Select **Create endpoint**.
+2. Select **Create proxy endpoint**.
 
 3. Give your endpoint any name.
 
@@ -116,7 +116,7 @@ https://<SUBDOMAIN>.proxy.cloudflare-gateway.com
 
 ## 2. Test your proxy server
 
-1. In [Zero Trust](https://one.dash.cloudflare.com/), create an [HTTP policy](/cloudflare-one/traffic-policies/http-policies/) for testing purposes. For example:
+1. In [Cloudflare One](https://one.dash.cloudflare.com/), create an [HTTP policy](/cloudflare-one/traffic-policies/http-policies/) for testing purposes. For example:
 
    | Selector | Operator | Value         | Action |
    | -------- | -------- | ------------- | ------ |
@@ -206,7 +206,7 @@ To get the domain of a proxy endpoint:
 
 <TabItem label="Dashboard">
 
-1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **Gateway** > **Proxy endpoints**.
+1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Networks** > **Resolves & Proxies** > **Proxy endpoints**.
 2. Choose the proxy endpoint. Select **Edit**.
 3. In **Proxy Endpoint**, copy the domain.
 
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
@@ -40,8 +40,8 @@ WARP versions prior to 2024.12.554.0 will only install the certificate set to **
 To configure WARP 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 [Zero Trust](https://one.dash.cloudflare.com/), go to **Settings** > **WARP Client**.
-3. Turn on [**Install CA to system certificate store**](/cloudflare-one/team-and-resources/devices/warp/configure-warp/warp-settings/#install-ca-to-system-certificate-store).
+2. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Team & Resources** > **Devices** > **Management**.
+3. Under **Global WARP settings**, turn on [**Install CA to system certificate store**](/cloudflare-one/team-and-resources/devices/warp/configure-warp/warp-settings/#install-ca-to-system-certificate-store).
 4. [Install](/cloudflare-one/team-and-resources/devices/warp/download-warp/) the WARP client on the device.
 5. [Enroll the device](/cloudflare-one/team-and-resources/devices/warp/deployment/manual-deployment/) in your Zero Trust organization.
 6. (Optional) If the device is running macOS Big Sur or newer, [manually trust the certificate](#manually-trust-the-certificate).
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
@@ -66,11 +66,12 @@ openssl x509 -in <CUSTOM-ROOT-CERT>.pem -text
 <Tabs syncKey="dashPlusAPI">
 
 <TabItem label="Dashboard">
-1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **Settings** > **Resources**.
-2. In **Certificates**, select **Manage**.
-3. Select **Upload certificate**.
-4. Enter the private key and SSL certificate you generated or select **Paste certificate from file** to upload them from a file.
-5. Select **Generate certificate**.
+1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Settings** > **Certificates and downloads**.
+2. Select **View**.
+3. In **Cloudflare certificates**, select **Manage**.
+4. Select **Upload certificate**.
+5. Enter the private key and SSL certificate you generated or select **Paste certificate from file** to upload them from a file.
+6. Select **Upload custom certificate**.
 
     You can now [use the generated custom root certificate](#use-a-custom-root-certificate) for inspection.
 
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
@@ -34,11 +34,12 @@ To generate a new Cloudflare root certificate for your Zero Trust organization:
 
 <Tabs syncKey="dashPlusAPI"> <TabItem label="Dashboard">
 
-1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **Settings** > **Resources**.
-2. In **Certificates**, select **Manage**.
-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.
-5. Select **Generate certificate**.
+1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Settings** > **Certificates and downloads**.
+2. Select **View**.
+3. In Cloudflare certificates, select **Manage**.
+4. Select **Generate certificate**.
+5. 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.
+6. Select **Generate certificate**.
 
 </TabItem>
 
@@ -68,10 +69,11 @@ To activate your root certificate:
 
 <Tabs syncKey="dashPlusAPI"> <TabItem label="Dashboard">
 
-1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **Settings** > **Resources**.
-2. In **Certificates**, select **Manage**.
-3. Select the certificate you want to activate.
-4. Select **Activate**.
+1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Settings** > **Certificates and downloads**.
+2. Select **View**.
+3. In Cloudflare certificates, select **Manage**.
+4. Select the certificate you want to activate.
+5. Select **Activate**.
 
 </TabItem>
 
@@ -92,10 +94,11 @@ Once you deploy and install your certificate, you can turn it on for use in insp
 
 <Tabs syncKey="dashPlusAPI"> <TabItem label="Dashboard">
 
-1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **Settings** > **Resources**.
-2. In **Certificates**, select **Manage**.
-3. Select the certificate you want to turn on.
-4. In **Basic information**, select **Confirm and turn on certificate**.
+1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Settings** > **Certificates and downloads**.
+2. Select **View**.
+3. In Cloudflare certificates, select **Manage**.
+4. Select the certificate you want to turn on.
+5. In **Basic information**, select **Confirm and turn on certificate**.
 
 </TabItem>
 
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
@@ -26,10 +26,12 @@ You can only download Cloudflare-generated certificates from the Zero Trust dash
 
 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 [Zero Trust](https://one.dash.cloudflare.com/), go to **Settings** > **Resources**.
-2. In **Certificates**, select **Manage**.
-3. Select the certificate you want to download.
-4. Depending on which format you want, choose **Download .pem** and/or **Download .crt**.
+1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Settings** > **Certificates and downloads**.
+2. Select **View**.
+3. In **Cloudflare certificates**, select **Manage**.
+4. Select the certificate you want to download.
+5. Select **More actions**.
+   - Depending on which format you want, choose **Download .pem** and/or **Download .crt**.
 
 Alternatively, you can download and install a certificate [using WARP](/cloudflare-one/team-and-resources/devices/user-side-certificates/automated-deployment/#install-a-certificate-using-warp). WARP will add the certificates to the device's system certificate store in `installed_certs/<certificate_id>.pem`.
 
diff --git a/src/content/docs/cloudflare-one/team-and-resources/devices/warp/configure-warp/device-profiles.mdx b/src/content/docs/cloudflare-one/team-and-resources/devices/warp/configure-warp/device-profiles.mdx
@@ -13,8 +13,8 @@ import { Render, TabItem, Tabs, APIRequest } from "~/components";
 
 <Tabs syncKey="dashPlusAPI"> <TabItem label="Dashboard">
 
-1. In [Zero Trust](https://one.dash.cloudflare.com), go to **Settings** > **WARP Client**.
-2. In the **Profile settings** card, select **Create profile**. This will make a copy of the **Default** profile.
+1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Team & Resources** > **Devices** > **Device profiles**.
+2. In the **Profile** card, 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).
 5. Configure [WARP settings](/cloudflare-one/team-and-resources/devices/warp/configure-warp/warp-settings/#device-settings) for these devices.
@@ -109,13 +109,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 [Zero Trust](https://one.dash.cloudflare.com/), go to **My Team** > **Devices**.
+1. In [Cloudflare One](https://one.dash.cloudflare.com/), 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:
+To verify the last active device profile for a user's devices:
 
-1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **My Team** > **Users**.
+1. In [Cloudflare One](https://one.dash.cloudflare.com/), 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/warp/configure-warp/managed-networks.mdx b/src/content/docs/cloudflare-one/team-and-resources/devices/warp/configure-warp/managed-networks.mdx
@@ -206,12 +206,12 @@ SHA256 Fingerprint=DD4F4806C57A5BBAF1AA5B080F0541DA75DB468D0A1FE731310149500CCD8
 
 </TabItem> </Tabs>
 
-## 3. Add managed network to Zero Trust
+## 3. Add managed network to Cloudflare One
 
 <Tabs syncKey="dashPlusAPI"> <TabItem label="Dashboard">
 
-1. In [Zero Trust](https://one.dash.cloudflare.com), go to **Settings** > **WARP Client**.
-2. Scroll down to **Network locations** and select **Add new**.
+1. In [Cloudflare One](https://one.dash.cloudflare.com), 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`).
 
@@ -220,6 +220,7 @@ SHA256 Fingerprint=DD4F4806C57A5BBAF1AA5B080F0541DA75DB468D0A1FE731310149500CCD8
    :::
 
 5. (Optional) In **TLS Cert SHA-256**, enter the [SHA-256 fingerprint](#2-extract-the-sha-256-fingerprint) of the TLS certificate. This field is only needed for self-signed certificates. If a TLS fingerprint is not supplied, WARP validates the certificate against the local certificate store and checks that it is signed by a public certificate authority.
+6. Select **Save**.
 
 </TabItem>
 <TabItem label="Terraform (v5)">
@@ -253,9 +254,9 @@ If a device profile uses [Split Tunnels](/cloudflare-one/team-and-resources/devi
 
 <Tabs syncKey="dashPlusAPI"> <TabItem label="Dashboard">
 
-1. In [Zero Trust](https://one.dash.cloudflare.com), go to **Settings** > **WARP Client**.
+1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Team & Resources** > **Devices** > **Device profiles**.
 
-2. Under **Profile settings**, create a new [settings profile](/cloudflare-one/team-and-resources/devices/warp/configure-warp/device-profiles/) or edit an existing profile.
+2. Under **Profiles**, create a new [profile](/cloudflare-one/team-and-resources/devices/warp/configure-warp/device-profiles/) or edit an existing profile.
 
 3. To apply this profile whenever a device connects to your network, add the following rule:
 
diff --git a/src/content/docs/cloudflare-one/team-and-resources/devices/warp/configure-warp/route-traffic/split-tunnels.mdx b/src/content/docs/cloudflare-one/team-and-resources/devices/warp/configure-warp/route-traffic/split-tunnels.mdx
@@ -99,10 +99,10 @@ 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 [Zero Trust](https://one.dash.cloudflare.com/), go to **Settings** > **WARP Client**.
-2. Under **Device settings**, locate the [device profile](/cloudflare-one/team-and-resources/devices/warp/configure-warp/device-profiles/) you would like to modify and select **Configure**.
+1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Team & Resources** > **Devices** > **Device profiles**.
+2. Under **Profiles**, locate the [device profile](/cloudflare-one/team-and-resources/devices/warp/configure-warp/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 **Delete**.
+4. Find the IP address or hostname in the list and select the **Action** button. From the dropdown, select _Delete_.
 
 <Render file="warp/client-notification-lag" product="cloudflare-one" />
 
diff --git a/src/content/docs/cloudflare-one/team-and-resources/devices/warp/configure-warp/warp-modes/device-information-only.mdx b/src/content/docs/cloudflare-one/team-and-resources/devices/warp/configure-warp/warp-modes/device-information-only.mdx
@@ -36,13 +36,15 @@ Using the API, enable client certificate provisioning for [your zone](/fundament
 
 ## 2. Configure the WARP client
 
-1. In [Zero Trust](https://one.dash.cloudflare.com), go to **Settings** > **WARP Client**.
+1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Team & Resources** > **Devices** > **Device profiles**.
 
-2. Under **Profile settings** card, choose a [device profile](/cloudflare-one/team-and-resources/devices/warp/configure-warp/device-profiles/) and select **Configure**.
+2. Under **Profiles**, choose a [device profile](/cloudflare-one/team-and-resources/devices/warp/configure-warp/device-profiles/) and select **Edit**.
 
 3. For **Service mode**, select **Device Information Only**.
 
-4. [Enroll your device](/cloudflare-one/team-and-resources/devices/warp/deployment/manual-deployment/) into your Zero Trust organization.
+4. Select **Save profile**.
+
+5. [Enroll your device](/cloudflare-one/team-and-resources/devices/warp/deployment/manual-deployment/) into your Zero Trust organization.
 
    When enrolled in Device Information Only mode, the WARP client will automatically generate a client certificate and install the certificate on the device. This certificate is necessary to confirm the source of outgoing traffic.
 
diff --git a/src/content/docs/cloudflare-one/team-and-resources/devices/warp/configure-warp/warp-sessions.mdx b/src/content/docs/cloudflare-one/team-and-resources/devices/warp/configure-warp/warp-sessions.mdx
@@ -30,7 +30,7 @@ You can allow users to log in to Access applications using their WARP session. W
 
 To configure WARP sessions for Access applications:
 
-1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **Settings** > **WARP Client**.
+1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Team & Resources** > **Devices** > **Management**.
 2. In **Device enrollment permissions**, select **Manage**.
 3. Go to the **Login methods** tab and enable **WARP authentication identity**.
 4. Under **Session duration**, choose a session timeout value. This timeout will apply to all Access applications that have WARP authentication enabled.
diff --git a/src/content/docs/cloudflare-one/team-and-resources/devices/warp/configure-warp/warp-settings/index.mdx b/src/content/docs/cloudflare-one/team-and-resources/devices/warp/configure-warp/warp-settings/index.mdx
@@ -56,7 +56,7 @@ If [Auto connect](#auto-connect) is enabled, WARP will automatically reconnect,
 To retrieve the one-time code for a user:
 
 1. Enable **Admin override**.
-2. Go to **My Team** > **Devices**.
+2. Go to **Team & Resources** > **Devices**.
 3. Select **View details** for a connected device.
 4. Scroll down to **User details** and select the user's name.
 5. Copy the 7-digit **Override code** shown in the side panel.
diff --git a/src/content/docs/cloudflare-one/team-and-resources/devices/warp/deployment/mdm-deployment/parameters.mdx b/src/content/docs/cloudflare-one/team-and-resources/devices/warp/deployment/mdm-deployment/parameters.mdx
@@ -13,7 +13,7 @@ Each client supports the following set of parameters as part of their deployment
 
 :::note
 
-Most of the parameters listed below are also configurable in Zero Trust under **Settings** > **Devices**. In the event of conflicting settings, the WARP client will always give precedence to settings on the local device (for example, in your `mdm.xml` or `com.cloudflare.warp.plist` files).
+Most of the parameters listed below are also configurable in Cloudflare One under **Team & Resources** > **Devices**. In the event of conflicting settings, the WARP client will always give precedence to settings on the local device (for example, in your `mdm.xml` or `com.cloudflare.warp.plist` files).
 
 :::
 
diff --git a/src/content/docs/cloudflare-one/team-and-resources/devices/warp/deployment/mdm-deployment/partners/intune.mdx b/src/content/docs/cloudflare-one/team-and-resources/devices/warp/deployment/mdm-deployment/partners/intune.mdx
diff --git a/src/content/docs/cloudflare-one/team-and-resources/devices/warp/deployment/mdm-deployment/partners/jamf.mdx b/src/content/docs/cloudflare-one/team-and-resources/devices/warp/deployment/mdm-deployment/partners/jamf.mdx
diff --git a/src/content/docs/cloudflare-one/team-and-resources/devices/warp/troubleshooting/common-issues.mdx b/src/content/docs/cloudflare-one/team-and-resources/devices/warp/troubleshooting/common-issues.mdx
diff --git a/src/content/docs/cloudflare-one/team-and-resources/devices/warp/troubleshooting/troubleshooting-guide.mdx b/src/content/docs/cloudflare-one/team-and-resources/devices/warp/troubleshooting/troubleshooting-guide.mdx
diff --git a/src/content/docs/fundamentals/manage-members/dashboard-sso.mdx b/src/content/docs/fundamentals/manage-members/dashboard-sso.mdx
