Access control for Batch Changes
Granular controls for who can access Batch Changes can be configured by site admins by tuning the roles assigned to users and the permissions granted to those roles. This page describes the permission types available for Batch Changes, and whether they are granted by default to the User system role. All permissions are granted to the Site Administrator system role by default.
| Name | Description | Granted to User by default? |
|---|---|---|
batch_changes:read |
| ✓ |
batch_changes:write |
| ✓ |
batch_changes:agent_read |
| ✓ |
batch_changes:agent_write |
| ✓ |
These permissions gate access to the Batch Changes feature as a whole. Within a batch change, what a user can see and do is further limited by the batch change's permission levels and by their repository permissions. Merging changesets can additionally be restricted to site admins with the batchChanges.restrictMergeToAdmins site configuration property.
The site configuration property batchChanges.restrictToAdmins is deprecated and has no effect.
To restrict Batch Changes to site admins, remove the batch_changes:read and batch_changes:write permissions from the User role instead.