Configure Organization Settings and Custom Terminology
Different member organizations use different terminology for the same concepts — NHF, Blindeforbundet, and HLF each have distinct names for roles, activities, and organizational units. The Admin Settings Screen allows Organization Administrators to configure these mappings through the organization labels system, which drives the Dynamic Label Widget throughout the app. Additionally, administrators can set integration parameters for accounting systems (Xledger, Dynamics), configure reimbursement approval thresholds, and toggle feature availability for their organizational scope. All changes are written to the audit log. National administrators see a broader configuration scope than local association administrators.
User Story
Acceptance Criteria
- Given I am an Organization Administrator, when I open Admin Settings, then I see only configuration options within my permitted scope (local vs. national level)
- Given I update a terminology label (e.g., rename 'peer mentor' to organization-specific term), when I save the change, then the Dynamic Label Widget reflects the new term throughout the entire app for my organization's users
- Given I configure an integration parameter, when I save, then the change is persisted to the integration config store and the audit edge function records the modification
- Given I toggle a feature on or off for my organization, when the toggle is saved, then users in my organization immediately see the feature enabled or disabled on next navigation
- Given I attempt to modify a setting outside my organizational scope, when the permission check runs, then the Permission Guard blocks the action and explains the scope restriction
Business Value
Different terminology used across organizations is a documented pain point that creates confusion when configuring shared tools. Custom terminology configuration eliminates this friction, increases end-user adoption rates, and allows Norse Digital Products to serve NHF, Blindeforbundet, and HLF with a single codebase without requiring separate builds per organization — a major cost and maintenance advantage.
Components
- Admin Settings Screen ui
- Admin Management Service service
- Admin Repository data
- Admin Audit Edge Function infrastructure