Overview
Requesting a change to how Performance Report Subscriptions handle user filters. Currently, saving a report subscription triggers an "Implicit Filter Lock," which snapshots the current user list and excludes any future users added to the account.

The Problem: "Implicit Filter Locking"
When a user creates a Performance Report subscription:

Even if "All Users" are intended to be included, the system saves the specific IDs of users active at that moment.

The New User Gap: Any user added to the system after the subscription is saved is automatically excluded from the emailed report.

Manual Maintenance: To include new hires, an admin must manually enter the Subscription Report editor, "Deselect All" to clear the implicit filter, and resave—a process that must be repeated every time the headcount changes.

The Discrepancy
This behavior creates a "data ghosting" effect where the Live Web Dashboard (which often defaults to all users) shows different totals than the Emailed Subscription (which is stuck on an old user list), leading to confusion and perceived data inaccuracies.

Proposed Enhancement
Dynamic "All Users" Flag: Implement a specific "Include All Current and Future Users" toggle that does not snapshot specific IDs.

Filter Persistence: If no specific users are selected, the report should default to the current state of the account at the time the report is generated, not when it was created.

Inheritance Logic: Allow subscriptions to follow "Site" or "Department" logic so that any user assigned to those groups is automatically inherited by the report.

Business Justification
Eliminates Discrepancies: Ensures emailed reports match the Live Web Dashboard totals.

Reduces Admin Burden: Eliminates the need for manual report audits every time a new extension is provisioned.

Data Accuracy: Prevents management from making decisions based on incomplete data sets that accidentally exclude new team members.

Technical Reference
Support Case: Dev Case 31260157

Observed Behavior: Filters are implicitly set/locked upon saving the subscription instance, failing to recognize account-level additions post-save.