Bufdir Export
Feature Detail
Description
Bufdir Export is the file-generation and download step following Bufdir Report Generation. Once a report has been reviewed, the export produces a downloadable file in the format required for Bufdir submission. It delivers the one-click export experience all four organizations have requested, turning manual data consolidation into a single admin action. This feature is scoped exclusively to the Admin Web Portal; peer mentors and coordinators contribute data through activity registration only.
Sources & reasoning
The source frames Bufdir reporting as a one-button export (line 46). Line 342 places export in Phase 2 alongside generation. Line 144 marks it MUST HAVE Phase 2 (v1.0). Blueprint assigns v1.0, consistent with Phase 2. Export is architecturally distinct from generation to allow preview before commit and independent audit-trail entries.
-
docs/source/likeperson.md · line 46Alle fire organisasjoner mottar Bufdir-tilskudd og bruker mye tid på rapportering. Ønsket er det samme: trykk på én knapp og få ut det Bufdir trenger.
-
docs/source/likeperson.md · line 342Bufdir-rapportering og eksport med ett klikk (kun i Admin Web Portal; mobilen bidrar med selve aktivitetsregistreringen)
-
docs/source/likeperson.md · line 144Bufdir-rapportering (eksport, admin) | ✓ | ✓ | ✓ | ✓ | ✓ | MUST HAVE | 2
Analysis
Bufdir Export is the culminating action of the compliance reporting workflow and directly fulfills the most-cited need across all four organizations. Without reliable export, report generation has no practical value - the exported file is what organizations submit to Bufdir. An audited export mechanism eliminates compliance risk and frees admin staff for mission-critical work. Storing the file server-side creates an audit record of what was submitted, protecting organizations in case of future compliance questions from the funding agency.
Export is implemented as a Next.js API route streaming the generated report file to the browser. The file format must be confirmed with Bufdir during Phase 2 development. ExportFileStorageService stores a server-side copy for audit purposes. The route enforces org admin or global admin role checks and logs each export event with timestamp, user ID, org, and date range to the audit log. Rate limiting prevents accidental duplicate submissions. The export step should be visually distinct from the generation step in the UI to prevent user confusion between preview and final submission.
Components (7)
Shared Components
These components are reused across multiple features
User Stories
No user stories have been generated for this feature yet.