Feature Request: Bulk Administrative Actions Across Filter Configuration
under review
T
Timothy Cogar
Issue
Many Lightspeed administrative workflows are optimized around managing individual objects.
That becomes inefficient in a large district when administrators need to make the same controlled change across dozens or hundreds of records.
Enterprise administration should allow repetitive operations to be performed safely in bulk without forcing administrators to repeat the same manual action object by object.
Requested Enhancement
Introduce bulk administrative actions across appropriate Lightspeed Filter configuration areas.
Applicable functions could include:
Access Lists;
Custom Categories;
SSL List entries;
administrative assignments;
reporting selections;
other list-based configuration objects.
Example Bulk Actions
Depending on the object type, administrators should be able to:
select multiple entries;
delete multiple entries;
move entries;
apply or change notes;
assign ownership;
add review dates;
extend expiration dates;
export selected records;
import structured records;
enable/disable entries;
assign or remove collaborators;
apply common configuration changes.
Not every bulk function must apply to every object.
The request is for a consistent bulk-management framework where the operation is logically safe.
Selection Options
Administrators should be able to select:
individual records;
all records on the current page;
all records matching the current filter;
an imported list of identifiers where supported.
For example:
Filter: SSL entries created before 2025
Select: All 82 matching records
Action: Assign Review Date
Safety Controls
Bulk actions should include safeguards proportional to their impact.
For destructive or high-impact changes, Lightspeed should provide:
preview of affected objects;
record count;
confirmation;
clear description of the action;
audit record;
error reporting for partially completed operations.
Example:
You are about to disable 147 SSL exceptions.
147 Selected
142 Eligible
5 Cannot Be Modified
This is preferable to either blindly executing the action or forcing 147 individual updates.
Import Capability
Where practical, bulk management should support structured CSV import for applicable object types.
The import process should:
validate records before committing;
identify duplicates;
identify invalid values;
show proposed changes;
allow administrators to reject or correct problematic entries.
Least Privilege Access
Bulk operations must respect Admin Role permissions.
A user should not gain broader rights merely because a bulk tool exists.
If a user can edit only certain objects, bulk actions should operate only within that authorized scope.
Requested Outcome
Provide efficient bulk-management capabilities for repetitive administrative operations.
The goal is:
One controlled action across many authorized objects
instead of:
The same administrative action repeated manually dozens or hundreds of times.
Acceptance Criteria
Applicable configuration areas support multi-select.
Common administrative actions can be applied in bulk.
Bulk actions respect existing role permissions.
High-impact actions include preview and confirmation.
Partial failures are clearly reported.
Bulk operations generate appropriate audit records.
CSV import/export is available where appropriate.
Business Value
This enhancement would:
reduce administrative workload;
reduce repetitive-entry errors;
make large-scale cleanup practical;
improve governance;
speed configuration changes;
make Lightspeed administration more appropriate for large enterprise environments.
Matthew Burg
updated the status to
under review
Matthew Burg
Thank you for the thorough feedback and feature ideas! This is a great set of submissions and clearly comes from a LOT of experience using the product day to day.
A couple of these touch on areas we're already looking closely at:
Agent diagnostics: The comparison to Zscaler's supportability model is a useful reference point, and the broader theme, that routine troubleshooting shouldn't require manual, low-level intervention, is something we're actively thinking about.
Bulk administrative actions: The way you laid out selection options across other areas (Lists, etc) for high-impact bulk changes reflects the same problem space we've had our eye on and want to improve.
We appreciate the time and detail put into all of these submissions. It's clear a lot of thought went into each one, and that context is genuinely valuable as we continue shaping the roadmap.
Autopilot
Merged in a post:
Bulk Administrative Actions Across Filter Configuration
T
Timothy Cogar
Issue
Many Lightspeed administrative workflows are optimized around editing individual objects.
That becomes inefficient in a large district when administrators need to perform the same legitimate operation across dozens or hundreds of records.
Enterprise administration should allow repetitive configuration changes to be performed safely in bulk rather than requiring the same action to be repeated manually.
Requested Enhancement
Introduce bulk administrative actions across appropriate Lightspeed Filter configuration areas.
Potential areas include:
Access Lists;
Custom Categories;
SSL List entries;
role/object assignments;
report selections;
other list-based administrative objects.
Example Bulk Actions
Where appropriate, administrators should be able to:
select multiple entries;
enable or disable entries;
delete entries;
move entries;
apply notes;
assign ownership;
assign review dates;
extend expiration dates;
export selected records;
import structured records;
assign or remove collaborators;
apply common configuration changes.
Not every bulk action needs to apply to every object type.
The request is for a consistent bulk-management framework wherever an operation can be performed safely.
Selection Methods
Administrators should be able to select:
individual records;
all records on the page;
all records matching the current filter;
imported identifiers where appropriate.
Example:
Filter: SSL entries created before 2025
Results: 82
Select All Matching
Action: Assign Review Date
Safety Controls
High-impact bulk actions should include safeguards.
Before execution, show:
affected object count;
proposed action;
eligible records;
records that cannot be modified;
clear confirmation.
Example:
147 records selected
142 eligible
5 cannot be modified
The administrator should know exactly what will happen before committing the change.
Partial Failure Handling
Bulk actions should not fail silently.
If some records cannot be updated, Lightspeed should report:
which records succeeded;
which failed;
reason for failure;
whether retry is appropriate.
Import Capability
Where appropriate, structured CSV import should support:
pre-validation;
duplicate detection;
invalid-value detection;
preview of proposed changes;
ability to reject or correct invalid rows before commit.
Audit Requirements
Bulk operations should generate audit records sufficient to identify:
administrator;
action;
time;
affected objects;
overall result.
Least Privilege Access
Bulk actions must respect existing administrative permissions.
A bulk tool should never expand the user's authority.
If the user can modify only certain objects, the bulk action should apply only to those authorized objects.
Requested Outcome
Allow one controlled action to be performed across many authorized objects.
The desired model is:
One governed action across the selected scope
rather than:
The same administrative action repeated manually dozens or hundreds of times.
Acceptance Criteria
Applicable areas support multi-select.
Common actions can be applied in bulk.
Bulk operations respect role permissions.
High-impact actions provide preview and confirmation.
Partial failures are clearly reported.
Bulk changes are auditable.
Structured import/export is supported where appropriate.
Business Value
This would:
reduce administrative workload;
reduce repetitive-entry mistakes;
make cleanup practical;
improve governance;
accelerate configuration changes;
make Lightspeed administration more scalable for large environments.