Bulk Operations on Users

Required permission: Running bulk operations on users requires the Administer Users or Own User role permission. Each selected user is also checked against your user-owner edit rights, so a user with only Own User can run bulk operations against the users they own. System users are always skipped. The Administer Bulk Operations role permission is not required to run bulk operations—it is only needed to view and stop operations started by other users from the Bulk Operations, where user bulk operations appear alongside secret operations.

Permissions are checked when the operation runs, not when it is submitted. A user without the required permission will see a bulk operation created that then fails with a "no permission" error on the task, rather than receiving an access-denied response.

Bulk operations on users can also be performed from the Users page. Select one or more users using the check boxes beside the Username column, or select all or none by toggling the check box in the header row. Once the appropriate users have been selected, use the Bulk Operation list at the top of the grid to select an action. Bulk operations on users currently include enabling or disabling user access, as well as configuring users for email or RADIUS two-factor authentication.