Feature flags
What it does
Feature flags are switches that turn specific platform behaviors on or off without a code change. They let administrators enable, disable, or safely roll out a capability for their organization.
Where to find it
Administrators manage them under Admin → Platform → Feature flags
(/admin/platform/feature-flags).
📸 Screenshot: the Feature flags screen (
feature-flags).
Encryption status lives beside it under Admin → Platform → Security
(/admin/platform/security).
📸 Screenshot: the Platform security screen (
platform-security).
Common tasks
See which flags are set
Open Feature flags to view each flag, what it controls, and whether it's on.
Change a flag (administrators)
Toggle the flag and Save. The change takes effect for your organization. Some behaviors that protect data are designed to be enabled once and left on — read the flag's description before changing it.
Check how patient data is protected
Open Security to see whether PII encryption is on, which key records are currently written with, and which older keys this installation still holds.
⚠ A retired key is not a spare copy — it is still in use. Older records were encrypted with it and it is the only thing that can read them back. Removing one from the installation's configuration destroys the records it protects. Keep every key listed here for as long as any record may still need it.
The screen shows key names, never the keys themselves, and there is nothing to change here: keys are set up by whoever installs the platform, not from this screen.
Tips & limitations
- Flags control behavior; whole feature areas are turned on under Modules.
- Some flags (for example ones that protect sensitive data at rest) are intended to be turned on and kept on — changing them later can have important consequences, so check with your platform owner.
- The Security screen shows whether the one-off conversion of existing records is switched on, but it cannot tell you whether that conversion has finished. This matters: if encryption is turned on for an installation that already has patients and the conversion is not run, those existing patients stop appearing in name searches. Ask your platform owner to confirm it ran.
When something looks wrong
| What you see | What it usually is |
|---|---|
| A setting will not take effect | A narrower scope overrides it — check facility, then tenant, then platform |
| A feature flag is on but the feature is absent | The module itself is not enabled for the tenant |
| A currency looks wrong on one screen only | That record stored its own currency when it was created |
For the causes common to every screen — a missing menu item, an empty list, a refusal — see Why a screen will not work.