Mass Edit

Select many entities, change one thing on all of them, review exactly what will happen per entity, and stage it. The console makes you open each object in turn; this makes a hundred-object campaign a single reviewed operation.

It is for the admin running a cleanup or a rollout: removing a posture profile from every policy that still references it, disabling a set of rules for a maintenance window, setting a flag across a fleet of application segments.

When to use it

• Maintenance windows: disable a set of rules and segments, then re-enable them afterwards.
• Criteria cleanup campaigns: remove a decommissioned posture profile from the policies that still name it.
• Standards rollouts: add a trusted network or platform condition to a class of access policies.
• Disaster-recovery posture: set the DR flag across the application segments that need it.

Where to find it in the UI

Open Dashboards → Entities, pick an entity type, filter down to what you need, select the rows with the checkboxes, and click Mass edit in the bulk action bar.

The button appears only when the selected entity type has editable fields.

What can be mass-edited

Entity type	Field	Operations
ZPA Application Segment	DR mode	Set enabled or disabled
ZPA Application Segment	State	Enable or disable
ZIA Firewall rule	State	Enable or disable
ZIA SSL Inspection rule	State	Enable or disable
ZIA URL Filtering rule	State	Enable or disable
ZPA Access Policy	Posture profile criterion	Add, remove
ZPA Access Policy	Trusted network criterion	Add, remove
ZPA Access Policy	Platform criterion	Add, remove

Only fields with a working write path are offered. Where Zscaler exposes no update path, the field is not in the list rather than failing at execution.

Step by step

1. Filter, then select. Narrow the Entities table to the objects you mean, then tick them. The selection is captured when the dialog opens, so later filter changes cannot alter what you are about to edit.

2. Open Mass edit and choose exactly one field, one operation and one value.

3. Read the preview. Every selected entity is listed with its current value and the value it will get. Rows fall into four states:

   Row state	Meaning
   Will change	Staged
   Already set / already matching, will be skipped	Greyed out, no change created
   Excluded	Cannot be edited, for example a policy the API will not accept
   Manually skipped	You unticked it in the preview

4. Skip anything you want to leave out, per row, from the preview itself.

5. Confirm. The footer counts what will happen: “N changes, M skipped”. Above 10 entities you are asked to confirm the count explicitly.

6. Review and execute in Pending Changes. Nothing reaches the tenant until you execute there.

What to watch

No-ops are not changes

An entity already at the target value produces no staged change at all. The preview says so and the count excludes it. A mass edit across 120 segments that stages 34 changes is telling you that 86 were already correct.

One group, not a hundred rows

Changes with the same field and value collapse into one group in the pending review, titled by the change and the entity count, for example “Set DR mode to enabled, 20 Application Segments”. Expand it for the individual items, or use group-level actions to remove all or retry the failures. The PDF export renders one element per group too.

If an entity later picks up a second, different staged change, it leaves the group automatically: grouping follows the content of the change set, not the operation that created it.

The conflict guard scales with you

Each staged change records the value it observed at staging time. At execution, if that field has moved in the console since, the item lands in conflict rather than overwriting, showing expected against found, with Apply anyway and Discard. On a 100-entity batch this is the difference between one careful decision and a hundred silent clobbers.

Execution touches only the field you chose

Each entity is re-read at execution and only the target field is modified. Names, actions, other criteria and every other setting are left exactly as they are.

Check the projected score before you commit

A bulk change is exactly where the projected posture score earns its keep: the pending drawer shows what the batch does to the number before you execute it.

Limits and notes

• One field per operation. A second field is a second mass edit.
• Up to 100 entities per operation, with an explicit confirmation above 10.
• Changes shared by a teammate are locked. An entity whose change is already in the team queue is skipped rather than duplicated.
• Execution is sequential, and the queue offers Execute First 50 so a large batch runs in controlled chunks instead of all or nothing.
• Mass edit is capability-gated. If the button never appears on any entity type, it is not enabled for your tenant.
• Criteria operations apply to ZPA Access Policies only, and only to the three criterion types listed above. The framework handles the others, but they are not enabled for production use.

FAQ

What happens to an entity that is already in the target state? Nothing. It is greyed out in the preview, excluded from staging, and counted as skipped.

Can I undo a mass edit? Before execution, yes: remove the group from the pending queue. After execution, no automatic rollback exists. Staging the inverse operation is the practical answer, which is why the preview is worth reading properly.

Why is one of my selected policies marked as excluded? It cannot be edited through the available write path. The dialog marks it rather than letting the whole batch fail at execution.

Does removing a posture criterion remove it everywhere, including failed verification states? Yes. The removal targets the profile on the policy regardless of the state of that occurrence.

Is there a limit to how many entities I can select in the table? The table selection is not capped, but a mass edit operation covers up to 100 entities. Work in batches above that.

Related pages

• Entities Table: where the selection is made
• Pending Changes: review, conflict resolution, execution
• Security Posture Dashboard: the projected impact of the batch
• Policy Reordering: the other bulk operation on policies

Next steps

1. Filter the Entities table to a small, safe set and run one mass edit end to end
2. Read the preview carefully, including the skipped rows
3. Check the projected score in the pending drawer before executing
4. Then scale the same operation to the campaign you actually came for