Issue

The Leadership Dashboard is currently tied to the Owner role.

This creates an unnecessary privilege requirement for a feature whose primary purpose is visibility and executive-level reporting.

Leadership users may have a legitimate need to view district-level filtering trends and summary information without needing administrative control of Lightspeed Filter.

Requiring the Owner role for dashboard access conflicts with Least Privilege Access principles.

Current Limitation

The dashboard cannot be independently assigned through Admin Roles.

As a result, organizations must choose between:

granting Owner-level access to leadership users;

withholding direct access to the dashboard; or

manually exporting and distributing information.

The export option is inefficient and does not provide the same value as direct access to a current dashboard.

Dashboards are intended to provide accessible, current visibility. Requiring another administrator to repeatedly export the information defeats much of that purpose.

Requested Enhancement

Add the Leadership Dashboard as an independently assignable permission within Admin Roles.

At minimum, administrators should be able to grant:

Leadership Dashboard

View

Not Allowed

A user assigned View access should be able to see the dashboard without receiving unrelated administrative privileges.

Least Privilege Access Design

The preferred model is:

Leadership user

Leadership Dashboard: View

Policy Administration: None

Access Lists: None

User Administration: None

Filter Configuration: None

Other unrelated administrative functions: None

Dashboard visibility should not require Owner-level access.

This would allow organizations to provide leadership with the information they need while preserving clear security boundaries.

Scope Control

Where practical, dashboard access should also respect the user's organizational scope.

For example, Lightspeed could support:

district-wide dashboard access;

school-specific dashboard access;

group-based dashboard access;

other scoped views where organizational permissions already exist.

This would allow the same dashboard capability to serve both central leadership and appropriately scoped local administrators.

Scheduled Export as a Secondary Option

Scheduled export or scheduled report delivery would still be useful as an additional capability.

Examples:

weekly leadership summary;

monthly executive report;

scheduled PDF or CSV delivery.

However, scheduled export should complement direct dashboard access rather than serve as the only alternative to Owner-level permissions.

The preferred solution remains role-based, view-only dashboard access.

Requested Outcome

Allow the Leadership Dashboard to be assigned independently through Admin Roles without requiring the Owner role.

The desired model is:

View-only dashboard access through Least Privilege Access

rather than:

Owner access or manual export

Acceptance Criteria

This request would be considered addressed when:

Leadership Dashboard access is available as an independent Admin Role permission.

View access does not require the Owner role.

Users with dashboard access do not receive unrelated administrative permissions.

Dashboard access respects organizational scope where applicable.

Administrators can revoke dashboard access independently of other permissions.

Scheduled reporting/export is available as an optional secondary delivery method where supported.

Business Value

This enhancement would:

support Least Privilege Access;

provide leadership with direct access to current information;

reduce unnecessary Owner-level permissions;

reduce manual report generation;

improve executive visibility;

make better use of a dashboard designed specifically for leadership reporting.

The requested principle is straightforward:

A dashboard intended for leadership visibility should be shareable as view-only access without requiring ownership of the entire platform.