Organization Settings & Terminology Configuration - Likepersonsapp – Peer Mentor Activity Platform | Generated by Eircodex v3.0

Scope

medium complexity extracted Admin Panel Confidence: 100%

6

Components

58

Shared

0

User Stories

Yes

Analyzed

Description

This feature enables each organization to customize the terminology and labels used throughout the mobile app and admin panel, reflecting the fact that different organizations use different words for the same concepts (e.g., 'likeperson' vs 'frivillig', 'oppdrag' vs 'aktivitet'). Administrators can edit string labels via a terminology editor screen, with changes propagating to all users in that organization in real time. The feature also covers broader organization settings such as contact details, logo, and configuration flags that control which optional features are enabled for that organization's deployment.

User Flow

Organization Settings & Terminology Configuration user flow

Click to expand

Analysis

Business Value

Each of the four partner organizations (NHF, Blindeforbundet, HLF, Barnekreftforeningen) uses distinct terminology rooted in their culture and history. Forcing a single vocabulary onto all organizations would create friction, reduce adoption, and undermine trust. A dynamic terminology system allows the platform to serve as a white-label foundation where each organization sees their own language, increasing the sense of ownership and reducing training overhead. This also future-proofs the platform for onboarding additional organizations with their own vocabularies without requiring code changes, which is a key commercial differentiator for Norse Digital Products.

Implementation Notes

The organization_labels table stores key-value pairs per organization, loaded server-side and injected into the Flutter app at login or organization-switch time. The mobile app references label keys rather than hardcoded strings, resolving them from the loaded label map. The Next.js admin panel provides a terminology editor UI that fetches current labels via /api/v1/admin/organizations/{id}/labels and patches changes via PUT. Labels are cached on the client with cache invalidation on organization switch. For the Flutter side, a Riverpod provider manages the labels state and exposes a helper method for resolving any label key. Settings flags (feature toggles per organization) are stored as JSONB in the organizations table and validated against a known schema to prevent invalid configurations.

Components (64)

User Interface (2)

ui Organization Settings Screen medium ui Terminology Editor Screen medium

Service Layer (1)

service Organization Settings Service medium

Data Layer (1)

data Organization Labels Repository low

Infrastructure (2)

infrastructure Labels Cache Infrastructure low infrastructure Settings Schema Validator low

Shared Components

These components are reused across multiple features

User Interface (16)

ui Accessible Picker Widget medium Shared ui Speech Input Widget medium Shared ui Contact Card Widget low Shared ui Contact Search Bar Widget low Shared ui View Switcher Widget low Shared ui Activity Summary Widget low Shared ui Approval Status Badge Widget low Shared ui Bottom Navigation Bar Widget low Shared ui Duplicate Warning Badge Widget low Shared ui Receipt Viewer Widget medium Shared ui Benefit Breakdown Chart Widget medium Shared ui AppButton Widget medium Shared ui AppTextField Widget medium Shared ui Modal Navigation Helpers medium Shared ui Page Header Widget low Shared ui Sync Status Indicator Widget low Shared

Service Layer (13)

service Auth Service medium Shared service Role Guard Service medium Shared service Activity Service medium Shared service Role Guard Service low Shared service Contact Service medium Shared service Email Invitation Service medium Shared service Oversight Audit Log Service medium Shared service Reimbursement Approval Audit Logger low Shared service Context Management Service medium Shared service Statistics Service medium Shared service REST API Client high Shared service Accessibility Service high Shared service Encryption Service high Shared

Data Layer (9)

data Token Storage low Shared data Auth Token Repository medium Shared data Activity Repository medium Shared data Contact Repository Cache low Shared data Contact Repository medium Shared data Reimbursement Admin Repository medium Shared data Organization Repository high Shared data Local Cache Repository medium Shared data Audit Log Repository medium Shared

Infrastructure (20)

infrastructure JWT Infrastructure medium Shared infrastructure JWT Infrastructure low Shared infrastructure Auth Middleware medium Shared infrastructure Report API Middleware low Shared infrastructure Report Access Guard low Shared infrastructure Approval Audit Logger low Shared infrastructure End-to-End Encryption Infrastructure high Shared infrastructure Email Delivery Infrastructure low Shared infrastructure Invitation Token Infrastructure medium Shared infrastructure Signed URL Provider low Shared infrastructure Multi-Tenancy Infrastructure high Shared infrastructure Calculator Export Infrastructure medium Shared infrastructure Request & Response Interceptors high Shared infrastructure Design Token System medium Shared infrastructure Semantic Labels Infrastructure medium Shared infrastructure Connectivity Infrastructure low Shared infrastructure Local Database Infrastructure high Shared infrastructure Secure Storage Infrastructure medium Shared infrastructure Connection Pool Infrastructure medium Shared infrastructure Database Migration Infrastructure medium Shared

User Stories

No user stories have been generated for this feature yet.