Activity Feed
Feature Detail
Description
The Activity Feed provides organization administrators with a chronological stream of recent activity registrations, user actions, and system events across their organization. The feed surfaces newly logged activities, pending approvals, and flagged entries in a scrollable view, enabling administrators to monitor organizational activity without running explicit reports. Each entry links directly to the relevant record for quick review and action. The feed serves coordinators reviewing recent peer mentor submissions and catching registration errors early before Bufdir reporting cycles close.
Sources & reasoning
admin-dashboard is always-on for Admin Web Portal and blueprint marks activity-feed as [MVP] (line 476). Fase 1 admin scope includes 'Aktivitetsoversikt og grunnleggende statistikk' (line 317) and the product description lists 'Activity oversight, approval workflows, and corrections' as a core Admin Web Portal capability (line 184). Activity Feed is the real-time surface for that oversight.
-
docs/source/likeperson.md · line 184Activity oversight, approval workflows, and corrections
-
docs/source/likeperson.md · line 317Aktivitetsoversikt og grunnleggende statistikk
-
docs/source/likeperson.md · line 476admin-dashboard | Admin Dashboard | Dashboard KPIs, Activity Feed
Analysis
Administrators currently lack real-time visibility into peer mentor activity - they receive batch reports that are days old. The Activity Feed closes this gap by surfacing recent registrations as they occur, enabling coordinators to catch errors, spot patterns, and follow up on flagged activities promptly. For NHF with 1400 lokallag, the feed is essential for managing large submission volumes. The feed also supports Bufdir audit requirements by making recent data immediately visible and actionable, reducing the risk of reporting gaps from unreviewed or duplicate submissions going unnoticed.
The Activity Feed Service queries the activities, events, and audit_logs tables with cursor-based pagination, returning entries sorted by created_at descending. Feed entries are polymorphic - supporting activity registrations, expense submissions, and system events - rendered through a unified card component with type-specific icons and action links. Tenant isolation is enforced at the query level via organization_id filters on every query. Server-sent events or 30-second polling provides live updates without full page reload. The feed widget is designed as a reusable component consumable both on the KPI dashboard and as a standalone admin page.
Components (46)
Shared Components
These components are reused across multiple features
Service Layer (11)
Data Layer (23)
Infrastructure (7)
User Stories
No user stories have been generated for this feature yet.