MEDIUM story-driver-administration-and-confidentiality-declarations-coordinator-006 3 pts

User Story

As a Coordinator
I want to see driver administration features only when my organization has the driver module enabled so that organizations that do not use drivers are not presented with irrelevant functionality
So that the app remains clean and focused for each organization, and the driver workflow is only accessible where it is configured and appropriate

Acceptance Criteria

  • Given the coordinator's organization has the driver feature flag enabled, when they open the app, then the driver assignment section appears in the home screen and in the relevant navigation areas
  • Given the coordinator's organization has the driver feature flag disabled, when they open the app, then no driver assignment list, declaration controls, or honorarium form are visible anywhere in the UI
  • Given the feature flag value changes in the backend configuration, when the coordinator restarts the app or the session refreshes, then the UI reflects the updated flag value without requiring an app store update
  • Given the coordinator attempts to deep-link into a driver assignment screen when the flag is disabled, when the route is resolved, then the driver feature flag guard redirects them to the home screen with no error
  • Given a system administrator changes the feature flag for an organization, when the coordinator's next session starts, then the flag evaluation uses the latest configuration from the repository

Business Value

The driver module is not relevant to all organizations using the platform. Exposing it universally would create confusion and additional cognitive load for coordinators at NHF or HLF who have no driver workflows. Feature flag gating allows a single app binary to serve multiple organizations cleanly, reduces support requests about irrelevant features, and enables Blindeforbundet to get their specific driver workflow without impacting other organizations' user experience.