Manage Platform-Wide Feature Flags and Rollout Configuration
The platform serves multiple organizations simultaneously, each with different readiness levels for new features. The Admin Settings Screen (scoped to Global Administrator) exposes feature flag management that controls which capabilities are enabled per organization context. This aligns with the workshop consensus on incremental rollout — existing systems must continue to function while the app is introduced as an option, not a mandate. Global Administrators can enable features for specific organizations ahead of general availability, supporting pilot testing with 5–8 person test groups as agreed with NHF, Blindeforbundet, and HLF. All flag changes are audited.
User Story
Acceptance Criteria
- Given I am a Global Administrator, when I open Admin Settings, then I see a feature flag management section listing all available feature flags
- Given I toggle a feature flag for a specific organization, when the change is saved, then users in that organization see the feature enabled or disabled on their next app load
- Given I toggle a feature flag, when the change is persisted, then the audit edge function records the actor, timestamp, flag name, previous value, new value, and targeted organization
- Given a feature is disabled for an organization, when a user from that organization attempts to access that feature's route, then they are redirected gracefully with an appropriate message
- Given I need to enable a feature for all organizations simultaneously, when I apply the flag globally, then the change propagates to all organizational scopes in a single operation
Business Value
Coordinating feature rollouts across multiple organizations with different terminology, workflows, and readiness levels without feature flags requires separate app builds per release — an unsustainable engineering overhead. Feature flags allow Norse Digital Products to ship continuously while controlling exposure per organization, enabling the incremental rollout strategy all workshop participants agreed was essential for adoption without disruption to existing workflows.
Components
- Admin Settings Screen ui
- Admin Management Service service
- Admin Repository data
- Admin Audit Edge Function infrastructure