Driver Feature Flag Configuration
Component Detail
Description
Database-backed configuration record controlling the availability of the driver administration and confidentiality declaration feature per organization. Supports runtime toggling without redeployment.
driver-feature-flag-config
Summaries
The Driver Feature Flag Configuration component gives the business the ability to control which organizations have access to the driver administration and confidentiality declaration features without requiring a software deployment. This is strategically valuable during phased rollouts, allowing the product team to onboard pilot customers, respond to support issues by temporarily disabling the feature for a specific organization, or gate access for organizations on specific subscription tiers. It reduces go-to-market friction, supports controlled feature releases, and protects the broader platform from issues affecting a single organization's configuration — all without engineering intervention for each change.
This is a low-complexity backend configuration component that can be delivered quickly, but its delivery timing is critical — it gates access to the entire driver feature set and must be completed before any driver or declaration feature can be made available in production. The component has no external dependencies and relies only on the `org_configuration` data model, making it straightforward to test in isolation. Ensure that the default-disabled behavior for new organizations is explicitly tested to prevent accidental feature exposure during onboarding. Admin tooling to toggle the flag (likely a settings screen or internal admin panel endpoint) should be scoped into the same delivery window to avoid the flag being set-only via direct database access.
Driver Feature Flag Configuration is a backend data component backed by the `org_configuration` data model, exposing three interface methods. `getDriverFeatureFlag(orgId)` should be a fast, cacheable read — consider an in-process TTL cache (e.g., 60 seconds) to avoid per-request DB hits on high-traffic paths that check this flag as a gate. `setDriverFeatureFlag(orgId, enabled)` performs an upsert on the configuration record, and should be restricted to admin-level callers via middleware authorization checks. `listOrgsWithDriverFeature()` supports operational reporting and should be available to internal admin tooling only.
The flag value must be checked by the `org-feature-flag-service` before any driver or declaration route is served. New organization provisioning code must explicitly default this flag to `false` — validate this in integration tests covering the org creation flow.
Responsibilities
- Store driver feature flag state per organization in the database
- Expose flag value to org-feature-flag-service
- Allow admin toggling of the flag via organization settings
- Default to disabled for new organizations
Interfaces
getDriverFeatureFlag(orgId)
setDriverFeatureFlag(orgId, enabled)
listOrgsWithDriverFeature()
Related Data Entities (2)
Data entities managed by this component