Activity Review & Approval

medium complexity MVP extracted Activity Oversight Confidence: 100%

Components

Shared

User Stories

Yes

Analyzed

Description

The Activity Review & Approval feature provides coordinators and organization administrators with a structured oversight interface in the Admin Web Portal for reviewing submitted peer mentor activities. Administrators can inspect activity details, verify correctness, and formally approve or reject submissions before they count toward reporting metrics. This ensures data quality and accountability across all registered activities before they flow into Bufdir reports or organization statistics dashboards.

Sources & reasoning

The MVP scope for the Admin Web Portal explicitly lists "aktivitetsoversikt" as a launch requirement. An approval workflow is the minimum viable form of that oversight - without it, submitted activities cannot be quality-gated before feeding into the Bufdir export that all four organizations depend on. Blueprint marks this MVP.

No source references — this artifact was included based on reasoning alone (see above).

Analysis

Business Value

Accurate activity data underpins all downstream reporting - from Bufdir government grant submissions to internal coordinator dashboards. Without a review step, erroneous or incomplete registrations propagate into official reports, risking grant non-compliance. By giving coordinators and org admins a dedicated approval workflow, the platform ensures only verified activities contribute to statistics and exports. This also creates a clear accountability trail satisfying audit requirements and supports the parallel-systems transition period where new registrations must be spot-checked against existing manual records.

Implementation Notes

Built as a server-side-rendered Next.js page in the Admin Web Portal consuming the shared REST API. The backend exposes a paginated /api/v1/activities endpoint filterable by status (pending, approved, rejected), organization, date range, and peer mentor. Activity state is stored as an enum column on the activities table indexed by status and org_id. Approval actions require Coordinator or Org Admin role claims validated server-side. All approval and rejection events are written to audit_logs. The mobile app activity submission sets initial status to pending and does not expose approval state to peer mentors.