Enforce Automatic Role-Based Data Scoping on All Report Queries

The Report Scope Resolver service reads the authenticated user's role and organizational memberships to derive a concrete scope key (local association ID, region ID, or national level) before any report query executes. This scoping is transparent to the user — they do not configure it. The Coordinator Report Service passes the resolved scope key to all aggregation queries and the Coordinator Stats Repository uses it as part of the cache key, ensuring cached results are never shared across scope boundaries. This mechanism integrates with the Role-Based Access Control system to enforce authorization at the data layer, not just the UI layer.

CRITICAL story-coordinator-reports-organization-administrator-004 5 pts

Story Points

Critical

Priority

Coordinator Reports & Dashboards

Feature

User Story

As a user

I want all report data I see to be automatically scoped to my authorized organizational level without requiring manual configuration

So that So that I can trust the data I see is accurate for my responsibilities and I cannot accidentally or intentionally access data outside my authorized scope, protecting peer mentor privacy and organizational data integrity

Acceptance Criteria

Given a coordinator authenticated under local association A, when they access any dashboard metric, then only data attributable to local association A is returned
Given an organization administrator, when they access dashboard metrics, then data from all associations and regions within the organization is included
Given a user's scope changes (e.g., role updated by admin), when they next load the dashboard, then the new scope is applied and previously cached data for the old scope is not served
Given a coordinator attempts to manipulate the filter widget to select an out-of-scope area, when the request is processed, then the Coordinator Report Service enforces the scope boundary and returns only authorized data
Given two coordinators with different scopes are logged in simultaneously, when each views the dashboard, then each sees exclusively their own scoped data with no cross-contamination
Given the scope key is computed, when the result is cached, then the cache key includes the scope identifier so different users with different scopes cannot access each other's cached results

Business Value

With 1,400 local associations and multiple coordinators, data isolation is a critical compliance and privacy requirement. A coordinator must never see peer mentor activity data from a competing local association. Automatic scoping enforced at the service layer — rather than relying on UI restrictions alone — ensures data integrity, builds user trust, and meets organizational data governance requirements. Failures here could expose sensitive peer mentor information and undermine confidence in the entire reporting system.

Components

Coordinator Reports & Dashboards

Related Feature

Organization Administrator

User Role