Feature · Team Collaboration

Team Collaboration Turn Zscaler administration into a team sport.

Zscaler environments are managed by teams, yet critical context often lives in one admin's head. ZHERO adds shared context on every entity, shared to-do lists that live next to your policies, a real-time synchronized queue of pending changes, and a complete audit trail. Individual work becomes governed team work.

Start Free Trial ▶ Watch Demo

ZHERO Collaboration panel with the shared to-do board in kanban view: To-do, Doing, Waiting, Blocked and Done columns, cards with assignees, due dates, priorities and blocked-by dependencies

Individual work becomes governed team work.

Why it matters

Team intelligence, layer by layer

Feature

Entity tags and threaded comments

Benefit

Tag any Zscaler entity and discuss it in threaded comments with author attribution, displayed inline in the console

Outcome

The "why" behind every configuration lives on the entity itself, not in someone's head or a forgotten ticket

Feature

Shared to-do lists linked to entities

Benefit

Track remediation as to-dos that reference the exact policies and entities, assigned to admins or external people, organized in lists with priorities, due dates and recurring checks, with a kanban view and blocker tracking

Outcome

The work owed on your tenant stays visible between calls, not lost in a spreadsheet three tools away from the configuration

Feature

Shared pending changes

Benefit

A personal staging area for work in progress and a shared team queue, synchronized in real time via WebSocket

Outcome

Every admin sees what is about to change before it changes, so nobody steps on a colleague's work

Feature

Collaboration Dashboard

Benefit

Team activity grouped by entity, with filters by author, date, entity type or action, plus tenant-wide data health monitoring

Outcome

One central hub to review what everyone is working on instead of asking around

Feature

Audit trail with before and after snapshots

Benefit

Collaboration audit and Zscaler change audit side by side, filterable by date range and action, exportable to Excel

Outcome

Compliance evidence in one export, not an archaeology project through old emails

Feature

PDF change documentation

Benefit

One-click export of proposed changes as a professional PDF with visual before and after diff cards, author and timestamp

Outcome

Change reviews your managers can actually read, generated in seconds

Team Collaboration turns ZHERO from an individual productivity tool into a governance platform for the whole team. Context lives on the entity instead of in someone’s head, changes are visible to everyone before they happen, and the audit trail with before and after snapshots makes compliance evidence one export away.

Shared to-do lists

The next best thing to a project manager, inside the console

Remediation stalls when nobody tracks who owns what between calls. ZHERO puts shared to-do lists where the work actually happens: every to-do links the exact policies and entities it is about, and those entities show a badge wherever they appear in the console, so the right context is right there. Assign work to console admins or to external people by name, organize lists by workstream, set priorities, due dates and recurring checks, and switch to a kanban board with blocker tracking when you need the big picture. A finding from Smart Analysis becomes a to-do with one click, so remediation you spot turns straight into tracked work.

ZHERO shared to-do list in list view with natural-language quick-add, multiple lists, assignees, priorities, due dates, recurrence and links to Zscaler entities

Shared context

The "why" lives on the entity

Open the Collaboration tab on any Zscaler entity to tag it, discuss it in threaded comments with author attribution, and pin a to-do to it, all inline in the console. The reasoning behind every configuration, and the work still owed on it, stays on the entity itself, not in someone's head or a forgotten ticket.

Collaboration tab on the SSL_Apple_Pinned URL category in ZHERO: tags, threaded comments and a To-dos section with per-entity quick-add and a linked to-do carrying an assignee and due date

How it works

From private note to tracked, documented change

Step 1

Annotate and assign

Add tags, threaded comments and to-dos directly on any Zscaler entity: policies, locations, segments and more. Assign the work to console admins or external people, set priorities and due dates, and every note carries its author.

Step 2

Stage changes in your personal queue, then promote them to the shared team queue with one click. Real-time synchronization keeps every admin's view current.

Step 3

Review together

The Collaboration Dashboard shows team activity grouped by entity, alongside the shared to-do board. Filter by author, date or action, monitor data health, and jump straight to any entity with open work or pending changes.

Step 4

Document

Export proposed changes as a PDF with visual diff cards, or pull the full audit trail to Excel with before and after snapshots for compliance documentation.

From individual tool to team platform

ZHERO moves Zscaler administration beyond individual silos to a unified, governed platform.

Entity Tags & Comments

Annotate any Zscaler entity with context-rich tags and threaded comments.

Shared To-do Lists

To-dos linked to entities, assigned to admins or external people, with due dates, recurrence and a kanban board.

Shared Pending Changes

A dual-queue system with real-time sync and conflict resolution.¹

Collaboration Dashboard

A central hub for team activity, open work, and recent changes.

Audit Trail

A complete log with before-and-after snapshots, exportable for compliance.

PDF Export

Branded reports for approval workflows and compliance.

Without ZHERO vs With ZHERO

Without ZHERO

With ZHERO

Entity context

A single description field, the rest lives in people's heads

Tags and threaded comments with author attribution, inline on any entity

Tracking remediation work

To-do lists in a spreadsheet or an external board, disconnected from the config

Shared to-do lists linked to the exact entities, with a badge on them in the console

Reviewing proposed changes

Screenshots pasted into email threads

A shared pending changes queue, synchronized in real time

Team coordination

Overlapping work discovered after the fact

Everyone sees who is changing what, before it happens

Audit trail

Modifications logged, reasoning lost

Collaboration context plus before and after snapshots on every change

Change documentation

Manual write-ups assembled for every review

One-click PDF with visual diff cards, author and timestamp

FAQ

Questions, answered

How do shared to-do lists work?

Each to-do can link the exact policies and entities it concerns, and those entities show a badge wherever they appear in the console, so the right context is one click away. Assign work to console admins, who see their own to-dos at login, or to external people added by name. Organize multiple lists by workstream, set priorities, due dates and recurring checks, and switch to a kanban board with blocker tracking when you need the big picture. It does not replace a project manager; it is the next best thing, right where the configuration lives.

Do to-dos send email notifications or connect to Jira, ServiceNow, Slack or Teams?

Not today. Notifications are in-app: admins see their assigned to-dos when they log in, and entities carry a badge in the console. There is no email notification and no external integration yet. If your team needs one, tell us and we can look at it together.

Where are tags and comments saved?

Tags, comments, to-dos and change metadata are ZHERO collaboration data: they sync through ZHERO so your whole team sees them in real time, isolated per tenant, and collaboration features are opt-in for each team. The only time actual configuration syncs is a shared pending change, and only while it stays in the shared queue (see below).

Does my Zscaler configuration leave the browser?

Analysis stays 100% in your browser: your configuration is not transmitted to ZHERO servers. Two kinds of data do sync, both isolated per tenant: collaboration metadata (tags, comments, to-dos, change metadata) and licensing data. There is one scoped exception for configuration itself. When you share a pending change to the team queue, the affected configuration is necessarily synchronized through ZHERO servers, only for the duration of the sharing, so the rest of the team can see it. Once that change is applied or removed from the shared queue, it is no longer stored there.

How does the shared pending changes queue work?

Each admin has a personal staging area for work in progress. When a change is ready for the team, promote it to the shared queue with one click (and demote it just as easily). The shared queue syncs in real time via WebSocket, with author attribution on every change. For that shared change to be visible to everyone, its configuration is synchronized through ZHERO servers only while it stays in the shared queue; once it is applied or removed, it is no longer stored there.

Can comments be moderated?

Yes. Every admin can edit or delete their own comments, and TenantAdmins have moderation rights for governance across the tenant.

Can I use this for compliance or management reviews?

Yes. The audit trail combines collaboration events with Zscaler change history, includes before and after entity snapshots, and exports to Excel. Proposed changes export as a PDF with visual diff cards you can share with managers and stakeholders for review.

Team Collaboration in action

Watch a 4-minute demo.

Ready to see Team Collaboration in your tenant?

Start Your Transformation!

Install in two minutes. No servers, no migration, no training.

Start Free Trial Schedule a Demo