Modules — enabling and disabling

In one sentence

The Modules admin page lets you hide entire QMS modules from your sidebar — so a small fabricator that doesn't run audits or FMEAs sees a navigation built for what they actually do, while a large multi-site operation can keep everything turned on.

Three things to remember

It's a navigation toggle, not a license toggle. Disabling a module hides it from the sidebar and blocks fresh creates; existing records aren't deleted, and re-enabling restores them immediately.
The core is always on. Dashboard, Documents, Actions, and Approvals can't be disabled — they're load-bearing for the rest of the system. Everything else (MOC, NCR, Risk, FMEA, JHA, Audits, Meetings, Gap Analysis, Exemptions, Suppliers, Clients, Training) is optional.
Disabling runs a safety check. Before flipping a module off, the system counts live references in other modules. If there are any, you see a confirmation dialog with the breakdown — "NCR has 7 open links to MOC records; closing those first is recommended" — and you decide whether to proceed.

What disabling a module does

When a module is disabled:

It disappears from the sidebar for every user in the org.
Its routes still resolve at the URL level — bookmarked links keep working, and the route serves a "module disabled" notice rather than 404. This is deliberate so an audit link from six months ago doesn't dead-end.
Fresh creates from other modules stop offering it. A new MOC won't show Add Linked FMEA as an option if FMEA is off.
Existing records stay intact in the database. Cross-module links remain. The data isn't deleted; it's just out of sight.

Re-enabling is instant — the next page load restores the sidebar entry, and nothing has to be migrated.

The pre-disable safety check

When you click to disable a module, the system runs a quick scan against the other modules to count how many live links exist into the one you're about to disable:

"MOC records linked from this NCR module"
"Documents that reference an external standard via Compliance Mapping"
"Risks rolled up from open FMEAs"

If the count is zero, the disable is applied immediately. If it's non-zero, you see a confirmation dialog listing the breakdown so you can decide whether to:

Cancel and close the cross-module references first (the safer path for a regulated environment).
Disable anyway — the records keep their links, they just become harder to navigate because one end of the link no longer surfaces in the sidebar.

Neither outcome is destructive; the safety check exists to make the blast radius visible.

Who can change this

Gated on the admin role. There's no separate permission for the page today — it's tied to base-role admin.

Changes are recorded in the activity log on the organization entity, so an auditor asking "when did Aerospace turn off MOC?" gets a timestamped answer with the actor's name.

Why not just remove modules entirely?

A common ask is "can we permanently remove FMEA from our org?" The answer is no — and that's intentional. Disabling preserves the audit trail (the records that referenced FMEA can still cite it; deleted modules would orphan those references). The trade-off is a slightly heavier UI under the hood; you don't notice it in the sidebar because the module disappears, but database queries don't sprout new arms when you re-enable later.