Issue

Web Activity reporting does not always identify the specific custom configuration object responsible for an allow or block decision.

Administrators may see a generic result such as:

Access List

Custom List

Custom Category

without being shown the exact Access List or custom object that caused the decision.

This creates unnecessary ambiguity during troubleshooting and policy review.

Current Limitation

Web Activity already exposes useful decision information, including whether traffic was allowed or blocked by category or Access List.

However, the report does not consistently display the specific Access List name associated with the decision.

This means an administrator can know that an Access List affected the request without knowing which Access List was actually responsible.

Operational Impact

Generic attribution increases the time required to troubleshoot filtering behavior.

When reviewing a blocked or allowed request, administrators may need to:

search through multiple Access Lists;

review policy assignments manually;

compare several possible custom categories;

reconstruct the decision path outside the activity record.

This is especially inefficient in environments with many custom lists and policies.

The activity record should provide enough information to explain the filtering decision directly.

Requested Enhancement

Add explicit object-level attribution to Web Activity reporting.

Where a filtering decision is caused by a custom object, the report should identify the exact object name.

Examples:

Current

Blocked by: Access List

Preferred

Blocked by: Access List — Student Gaming Block

Current

Allowed by: Custom List

Preferred

Allowed by: Access List — Approved Instructional Resources

Current

Blocked by: Custom Category

Preferred

Blocked by: Custom Category — District Restricted Services

Reporting Fields

Where applicable, Web Activity should expose:

decision type;

exact Access List name;

exact Custom Category name;

applicable policy;

allow/block result;

other relevant policy object responsible for the final decision.

If multiple objects contributed to the result, the report should identify the final controlling object and, where practical, the relevant decision path.

Preferred UI Design

The exact object name should be visible directly in Web Activity without requiring administrators to navigate into multiple additional console areas.

This could be implemented as:

a dedicated Access List column;

a dedicated Decision Source column;

an expandable decision-details view;

clickable object names linking directly to the relevant configuration.

A dedicated Access List column would align well with the existing reporting model.

Export Requirement

The specific object name should also be included in exported Web Activity data.

If the console identifies the Access List or Custom Category responsible for a request, that information should remain available when the report is exported for troubleshooting, auditing, or analysis.

Requested Outcome

Provide clear attribution of the exact custom object responsible for an allow or block decision.

The desired behavior is:

Decision type + exact object name

rather than:

Generic object type only

Acceptance Criteria

This request would be considered addressed when:

Web Activity identifies the specific Access List responsible for an allow or block decision.

Custom Category names are displayed where applicable.

Generic labels such as “Custom List” are not used when the specific object is known.

The object name is visible directly in Web Activity or an immediately accessible details view.

The same attribution is preserved in exported Web Activity data.

Administrators can quickly identify which configuration object produced the reported result.

Business Value

This enhancement would:

reduce troubleshooting time;

improve policy transparency;

make Web Activity more useful as an administrative diagnostic tool;

reduce manual policy correlation;

improve auditing and reporting;

allow administrators to understand filtering decisions directly from the activity record.

The requested improvement is simple:

If Lightspeed knows which custom list or category made the decision, Web Activity should show its name.