Cloudflare has changed how its dashboard is organised for Zero Trust customers. According to the company's developer changelog, the Cloudflare dashboard now combines Zero Trust navigation with the main dashboard navigation, so users can move between Cloudflare products from a single navigation structure rather than switching between separate ones.
The changelog states that all customers can browse Zero Trust products from the primary navigation. For Zero Trust customers specifically, the same navigation also provides access to other services, which the entry lists as the developer platform, account memberships and resource tagging.
The change is not purely additive. Cloudflare says the Zero Trust Network items were removed, replaced by experiences now available under the Networking navigation. Separately, Resolvers & Proxies was moved under Traffic Controls, which the changelog notes was previously called Traffic Policies.
Cloudflare describes the update as available to all customers starting the day the entry was published, and points readers to the Cloudflare One documentation for further detail. The changelog does not describe a staged rollout, a beta period or an opt-in process.
For developers and technical freelancers who administer Cloudflare accounts, the practical effect is navigational rather than functional in the sense described: the entry documents where items live, not new capabilities. Anyone following written runbooks, internal onboarding docs or client handover notes that reference the old Zero Trust Network menu path or the Traffic Policies label will need to update those references.
The rename of Traffic Policies to Traffic Controls is the kind of detail that quietly breaks documentation. A freelancer handing a project to a client, or a studio maintaining a shared internal wiki, may find that instructions pointing at the previous label no longer match what appears in the interface, even though the underlying configuration is unchanged as far as the changelog indicates.
The consolidation also has a plausible workflow benefit that the source implies rather than states: because Zero Trust customers can reach the developer platform, account memberships and resource tagging from the same navigation, account-level tasks that previously sat in a different navigation context are now reachable from one place. The changelog does not quantify how many clicks or steps this saves, and no measurements are provided.
It is worth being precise about what the evidence does and does not cover. The changelog is a short product note. It does not explain whether any Zero Trust Network functionality was deprecated, only that those navigation items were removed in favour of experiences under Networking. Removal of a menu entry is not the same as removal of a feature, and the entry does not claim otherwise.
Similarly, the entry does not state whether the old navigation paths redirect, whether bookmarks to previous dashboard URLs still resolve, or whether any API endpoints or configuration identifiers changed. Those are open questions for anyone whose tooling or documentation depends on the previous structure.
The changelog also does not address permissions. It says Zero Trust customers can access other services from the navigation, but it does not describe whether role-based access controls, seat types or plan tiers affect what appears in the merged navigation. Administrators managing multiple client accounts should verify visibility per account rather than assume uniformity.
There is no pricing information in the entry, and no indication that the change affects billing, plan entitlements or contract terms. The update is presented as a dashboard navigation change available to all customers, not as a new product or a paid tier.
For this audience, the sensible response is documentation hygiene. If you maintain setup guides, screen-recording walkthroughs or client-facing handover documents that name Zero Trust Network or Traffic Policies, treat those references as stale and check them against the current interface. Screenshots in particular age badly after a navigation merge.
A second, more cautious implication concerns support and troubleshooting. When a client reports that they cannot find a setting, the first question may now be which navigation they are looking at, since the entry indicates Zero Trust and main dashboard navigation have been combined rather than kept separate. That is editorial interpretation, not a claim from the source.
The limits of this report are the limits of the source. Cloudflare's changelog entry is brief, undated in its extracted text beyond the publication timestamp, and does not include screenshots, a migration guide, a deprecation timeline or a list of affected URLs. It also does not say whether the change is reversible or whether any legacy navigation remains available.
The concrete, narrow points that can be stated with confidence are these: main dashboard navigation and Zero Trust have been merged; from the primary navigation, Zero Trust products are now browsable by every customer; the developer platform, resource tagging and account memberships are likewise reachable by Zero Trust customers there; Networking experiences have taken the place of the Zero Trust Network items that were removed; and under Traffic Controls — previously called Traffic Policies — Resolvers & Proxies now sit.
Anything beyond those points, including whether the change improves or complicates day-to-day administration, is a judgement individual teams will have to make against their own workflows. The changelog offers no user research, no adoption data and no stated rationale for the reorganisation.
The most useful next step for a freelancer or small studio is to open the dashboard, confirm where the items you rely on now live, and update your own written references accordingly. Cloudflare directs readers to its Cloudflare One documentation for more information, which is the appropriate place to check specifics the changelog omits.