---
title: "ZScaler Setup"
slug: "managing-a-zscalar-pop-1"
updated: 2025-07-28T12:53:18Z
published: 2025-07-28T12:53:18Z
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.plainid.io/llms.txt
> Use this file to discover all available pages before exploring further.

# ZScaler Setup

Ensure that you have an [Orchestration Workspace](/v1/docs/managing-workspaces){target=`_blank`} before continuing. You can learn how to **create a Zscaler** in [Managing POPs](/v1/docs/managing-pops){target=`_blank`} and how to **switch between modes** in [Orchestration Workspace](/v1/docs/orchestration-workspace){target=`_blank`}.

### Zscaler Connection Fields
To connect Zscaler with PlainID, enter the following **Connection Fields**. These credentials enable authentication and communication between Zscaler and the Policy Orchestration Point (POP). 
*Note: If multiple IDPs are defined, the one with the enabled scheme is selected. If more than one scheme-enabled IDP exists, one will be automatically selected.*

### Required Credential Fields

| Connection Field         | Description |
|--------------------------|-------------|
| Authentication Method    | Use `client_credentials` to authenticate using the Zscaler API. |
| API Key                  | The API key provided by Zscaler for your account. |
| API Key Secret           | The API secret corresponding to the API key. |
| Customer ID              | The Customer ID associated with your Zscaler tenant. |
| Customer Based URI       | The Zscaler API URI specific to your tenant (e.g., `https://config.zpabeta.net`). |


This initial discovery discovers all of the access policies managed within ZPA, as well as the Application segments and the Application segment groups. The access policies will appear in the Authorization Workspace as {{variable.PlatformName}} Policies. 

When you click on a Policy, as with Policies created within the {{variable.PlatformName}}, you can view the Policy in structured Rego (click **Code**), or as a visual representation of the Policy (click **Map**).

In addition, the Identity Workspace and the Authorization Workspaces are populated with the mapped objects and Policies discovered in ZPA.
