Custom Terminology

Terminology customization is a key differentiator that lets a single codebase serve organizations with distinct vocabularies without per-tenant code branches. NHF, HLF, Blindeforbundet, and Barnekreftforeningen all use different terms for the people they serve and the roles in their organizations. Forcing a fixed vocabulary would create friction and reduce adoption - volunteers who see unfamiliar labels are more likely to disengage. The labels system also future-proofs onboarding: new tenants configure their vocabulary at setup rather than filing change requests with Norse. This directly supports the incremental rollout strategy (§1.5) where the app must feel native to each organization.

Labels are stored in the organization_labels table (one-to-many from organizations). The backend exposes the full label map as part of the session bootstrap response so the mobile app and admin portal can apply overrides at startup. The Flutter app stores labels in the Drift offline database and falls back to hardcoded defaults if the network fetch has not yet succeeded. The Next.js admin portal reads labels server-side and injects them into the React context. The editor UI is a simple key-value table restricted to Org Admin; adding new label keys requires a backend schema change, so the UI only exposes keys already registered in the system. Current registered keys: contacts, my_contacts, peer_mentors, peer_mentor, coordinator, contact.