Monitor Vipps SSO Personnummer Enrichment
When members authenticate via Vipps SSO, the returned personnummer is automatically written back to the member record in the source system via the Member System API Gateway. The admin UI surfaces enrichment statistics: total members missing personnummer before enrichment started, number enriched to date, percentage complete, and a timeline chart showing enrichment rate per week. This data is sourced from the member sync repository which records each enrichment event. Organization Administrators see stats for their organization; Global Administrators see aggregated stats across all organizations.
User Story
Acceptance Criteria
- Given a member successfully authenticates via Vipps SSO, when the authentication flow completes, then the Vipps Member ID Sync Service writes the returned personnummer to the member's source system record within 30 seconds
- Given personnummer enrichment has occurred, when I view the enrichment statistics panel, then I see total members enriched, percentage of previously missing personnummer now filled, and the date of the most recent enrichment
- Given I view the enrichment timeline chart, when I look at the weekly breakdown, then I see the number of new enrichments per week since the feature was activated
- Given a personnummer write-back to the source system fails (e.g., API error), when the failure occurs, then it is logged in the sync repository with the member ID, error reason, and timestamp for manual follow-up
- Given an Organization Administrator views enrichment stats, when they are scoped to their organization, then they cannot see other organizations' enrichment data
Business Value
Many member records lack personnummer, which is required for Bufdir reporting and honorarium processing. The Vipps SSO flow provides a zero-marginal-cost mechanism to fill this gap organically as members authenticate. Tracking the enrichment rate allows organizations to assess whether the passive enrichment approach is sufficient or whether a targeted outreach campaign is needed to reach members who have not yet logged in via Vipps.
Components
- Vipps Member ID Sync Service service
- Member Sync Repository data
- Member System API Gateway infrastructure
- Member Sync Status Widget ui