feature-toggle

Feature flags enable per-customer toggling by storing flags on the Organization model and exposing them through the subscription service as SubscriptionFeature objects. This allows you to gate UI behavior by checking the active status of specific features for individual customers.

An admin override pathway for feature toggles allows global admins to bypass per-customer gating using a subscription debugger. This enables administrators to manually enable or disable features for specific customers regardless of their standard subscription configuration.

To wire backend enums and subscription data for feature gating, create a FeatureFlags entry, add a has_my_feature field, and connect the subscription service logic. This ensures the backend properly evaluates active and inactive feature states per customer.

The frontend accesses per-customer feature flag states via the customer.subscription.has_my_feature.active path. This exposes the toggle status directly to UI components, allowing them to conditionally render features based on the customer's subscription data.

Tests covering both active and inactive feature flag states are required. Verifying both states ensures the per-customer gating logic functions correctly across backend service wiring and frontend consumption, preventing unintended feature access.