View Organization-Specific Settings Sections
When an Organization Administrator opens the Settings screen, additional settings cards are shown based on the organization's feature flags loaded at session start via a Riverpod provider. These may include shortcuts to organization label configuration, integration status, and other admin-level preferences. Feature flags are loaded from the Supabase user profile at authentication time and stored in a Riverpod provider. The Preferences Service evaluates these flags when building the settings card list, ensuring that NHF, Blindeforbundet, and HLF each see only the settings sections enabled for their organization. Cards that are not enabled for an organization are not rendered at all, keeping the settings screen clean and focused.
User Story
Acceptance Criteria
- Given I am an Organization Administrator and my organization has org-label customization enabled, when I open Settings, then a settings card for organization labels is visible
- Given I am a Peer Mentor or Coordinator, when I open Settings, then organization-administration-specific settings cards (such as org labels, integration shortcuts) are not shown
- Given organization feature flags are loaded at session start, when the Settings screen renders, then the visible settings sections match the enabled features for my organization without any additional network request
- Given my organization's feature flags are updated by an administrator, when I next sign in, then the Settings screen reflects the updated set of visible sections
- Given an org-admin-specific settings card is shown, when I tap it, then I am navigated to the corresponding administration screen for that feature
Business Value
NHF, Blindeforbundet, and HLF each use different terminology and have different feature sets enabled. Organization Administrators need role-appropriate settings access without the cognitive overhead of navigating irrelevant sections. Feature-flag-driven settings visibility is the architectural mechanism that makes a single app serve all three organizations while appearing tailored to each, which is a core requirement of the multi-organization product strategy.
Components
- Settings Screen ui
- Settings Card Widget ui
- Preferences Service service
- Preferences Repository data