What is the Zscaler Experience Center?
The Zscaler Experience Center is Zscaler's unified admin console, often called ZEC for short. It brings together the management of internet and SaaS access (ZIA), Private Access (ZPA), Digital Experience Monitoring (ZDX) and Client Connector under one interface, which Zscaler calls the Zscaler Admin Console. Instead of several separate portals with their own logins, there is now a single sign-on through console.zscaler.com, independent of the tenant's Zscaler cloud. Existing configurations, reports and dashboards are retained during the switch. For admins and the helpdesk, what changes is mainly the day-to-day navigation, not the rule set.
Zscaler Experience Center in detail
The console brings together four previously separate management worlds: internet and SaaS policy, private applications, Digital Experience Monitoring, and the management of endpoint agents, meaning the Zscaler Client Connector. It also adds unified reporting that shows events across these areas in consolidated views, plus a guided onboarding flow for new tenants.
The technical prerequisite is the central Zscaler sign-on service (Authentication Service): after migration, admins sign in to the new console with one identity that spans all portals, instead of maintaining separate access per portal. Zscaler migrates tenants in stages and announces each one through a migration notification. According to the documentation, the previous individual portals remain supported and reachable as things stand.
Why the Experience Center matters in Zscaler operations
For day-to-day operations, the switch is mainly a question of work routines. Long-established bookmarks, helpdesk runbooks with screenshots, training material and documented click paths all point to the previous portals. After the switch, the same functions sit in new places within a reorganised navigation. Anyone who only notices this during an incident loses time exactly when it is scarcest.
At the same time, the switch is an opportunity: one console with a single sign-on cuts down on portal switching and context breaks, and cross-service reporting makes it easier to make sense of incidents. A planned transition pays off: inform the team, walk through the new navigation during a quiet period, update runbooks and internal guides, and keep an eye on the official migration notices.
Common sources of error
- Runbooks and training material still point to the old portals; the helpdesk has to piece functions together again during an incident.
- Migration of admin accounts to the central sign-on service is incomplete; some admins cannot sign in to the new console.
- Bookmarks and password manager entries point to old portal URLs instead of console.zscaler.com.
- The switch is done on the side, with no test run and no defined contact person for questions from the team.
Experience Center in practice: what CentaurNexus contributes
CentaurNexus is an operations cockpit that looks at the tenant through the official Zscaler OneAPI, so it works independently of whichever console interface is currently in use. The helpdesk keeps using 360-degree user search exactly as before: enter a name or email address and see a user's status across ZIA, ZPA and ZDX on one page, with no Zscaler admin rights and no new click paths to learn. That takes the pressure off the switch, because standard cases stay in the cockpit and the console is reserved for special cases. The article below explains why the helpdesk stays productive regardless of changes to the views: Zscaler support without admin rights.
Related terms
Frequently asked questions about the Zscaler Experience Center
Previously, each Zscaler service had its own admin portal with its own login: ZIA, ZPA, ZDX and Client Connector were managed separately. The Experience Center brings this management together in one console with unified navigation and cross-service reporting. Sign-in runs centrally through console.zscaler.com, regardless of which Zscaler cloud the tenant sits in.
No. According to Zscaler's documentation, all existing configurations, reports and dashboards are retained and continue to be managed through the new interface. The switch affects the user interface and sign-in, not the policies themselves. Even so, a configuration snapshot before the cutover is worthwhile, to have proof of the exact state on record.
Administrators must have migrated to the central Zscaler sign-on service (Authentication Service), which provides one identity spanning all Zscaler portals. Zscaler also recommends moving end users to this sign-on service. After the migration notification, admins sign in to the new console directly with their existing credentials.
Yes, they remain reachable. Zscaler has since published a timeline: migration to the Experience Center was to be complete by March 2026, new features have appeared there exclusively since April 2026, and as of September 2026 the previous admin interfaces are officially deprecated. The documentation still does not name a shutdown date, because deprecated does not mean switched off. For operations, this means updating runbooks, training material and bookmarks now, rather than waiting for an end date.
Familiar click paths, bookmarks and guides change because menus and the navigation structure are reorganised. Helpdesk teams should update their runbooks and screenshots before the switch and walk through the new paths once. Teams that use an operations cockpit for standard cases, without working directly in the views, are less affected by the switch in daily business.
- Zscaler Help Portal: Upgrading to Zscaler Experience Center - help.zscaler.com
- Zscaler: Experience Center product page - zscaler.com
Note: CentaurNexus is an independent product of SourcingBlox GmbH and not an offering of Zscaler, Inc. Product and brand names belong to their respective owners.