Feature flags and modules

Not every client wants every module. Keanan gates whole modules behind feature flags served by a self hosted Unleash instance that ships inside the stack.

The module flags

Flag	Gates
module.meetings	Monday meetings
module.benefits	Benefit plans and enrollments
module.referrals	The referral program
module.support	Support tickets and FAQs
module.documents	The document center in the app

Create a flag in the Unleash console at port 4242, name it after the module and leave it off. The dashboard hides that module from navigation, and its API answers with not found. Enable the flag and everything returns within thirty seconds, which is the cache window.

Checking state

GET /api/v1/modules/

{
  "meetings": true,
  "benefits": true,
  "referrals": false,
  "support": true,
  "documents": true
}

Failure behavior

If Unleash is unreachable, every flag reports enabled. A flag service outage can never take a client’s deployment down. Flags that were never created in Unleash also report enabled, so a fresh install works before anyone opens the console.

Beyond modules

The same client is available for finer grained flags. Call common.feature_flags.is_enabled with any flag name from backend code and manage it from the same console.