Modules
What it does
Modules are the optional capabilities of the platform. An administrator switches modules on or off so each organization gets only the features it needs. Activating a module makes its area appear in the navigation for users who have permission.
Where to find it
Administrators manage modules under Admin → Modules (/admin/modules), with screens for
tenant activation (/admin/modules/tenant-activation) and facility activation
(/admin/modules/facility-activation).
📸 Screenshot: the Modules admin list (
modules-list).
Common tasks
See what's active
Open Admin → Modules to view the available modules and whether each is on.
Turn a module on or off (administrators)
- Open Tenant activation to enable a module for a whole organization, or Facility activation to enable it for a specific site.
- Toggle the module and Save. Its features appear (or disappear) for users who have access.
Tips & limitations
- Turning a module off hides its features but does not delete existing data.
- A module can be enabled per tenant and, more narrowly, per facility — so a capability can be available at one site but not another.
- Fine-grained on/off switches within a feature are handled by Feature flags.
When something looks wrong
| What you see | What it usually is |
|---|---|
| Enabling a module changes nothing for a user | They still need the permissions; enabling only makes them grantable and the menu possible |
| A module cannot be disabled | Something in it is in use; disabling would strand records |
| A module is enabled but its menu is missing for everyone | The screen's route is not registered — a build-level fix |
For the causes common to every screen — a missing menu item, an empty list, a refusal — see Why a screen will not work.