Team Reports
Feature Detail
Description
Team Reports gives coordinators and org admins structured views of team-level activity data for peer mentor oversight. It aggregates logged activities, participation rates, and engagement metrics into report formats in the Admin Web Portal. Admins monitor operational health and identify gaps while coordinators track peer mentor networks. The feature provides the activity data foundation that Bufdir Report Generation depends on, making accurate team-level visibility essential from MVP.
Sources & reasoning
Line 326 places activity oversight and basic statistics in the Admin MVP scope. Line 195 lists coordinator and org-level dashboards as a core admin portal capability. Team Reports is the direct realization of these requirements. Blueprint assigns MVP, consistent with the Phase 1 admin scope in the source doc.
-
docs/source/likeperson.md · line 326Aktivitetsoversikt og grunnleggende statistikk
-
docs/source/likeperson.md · line 195Coordinator and organization-level dashboards and KPIs
Analysis
Team Reports replaces manual aggregation from spreadsheets and Word documents, a pain point across all four organizations. Coordinators gain real-time visibility into peer mentor engagement without offline consolidation, and org admins can identify underperforming local associations earlier. The feature also underpins Bufdir Report Generation: solid team-level data directly reduces compliance effort. For NHF with 1,400 local associations, scalable team reporting is operationally critical and protects grant funding for all participating organizations.
Team Reports are generated server-side in Next.js using SQL aggregation over activities, users, and organizations tables with date-range and association-scoped filters. The aggregation layer must be shared with Bufdir Report Generation to avoid logic duplication. Server-side rendering ensures fast initial loads. Role-based access control restricts coordinators to their association's data and org admins to their org scope. Pagination and printable output should be built in from the start. Queries must be indexed for large orgs with hundreds of peer mentors.
Components (7)
Shared Components
These components are reused across multiple features
User Stories
No user stories have been generated for this feature yet.