Feature Flags
Toggling features on and off via database fields
Feature Flags
Feature toggling is done with database fields — there is no third-party flagging
service in the project. A record's isActive (or equivalent) column is the switch,
which means a flag change is an admin action rather than a deploy.
Database Feature Flags
| Model | Field | Purpose |
|---|---|---|
Fundraiser | enableSocialFeatures | Toggle social features per fundraiser |
EmailConfiguration | isActive | Enable/disable email configurations |
ServiceKey | isActive | Enable/disable service integrations |
PartnerApiKey | isActive | Enable/disable partner API access |
Product | isActive | Show/hide products |
EmailTemplate | isActive | Enable/disable email templates |
GrowthBook was previously carried as a dependency for flagging and A/B testing but was never wired into the app, and has been removed. If percentage rollouts or experiments are needed later, that is a fresh integration decision rather than re-enabling dormant code.
How is this guide?
Edit on GitHub
Last updated on