Module Management
Turn QuantumOps modules on or off for your organisation, see what each one needs, open its own page and run the identity verification checks.
Written By Chris Scaminaci
Last updated About 2 hours ago
QuantumOps is a set of modules, and each one can be on or off for your organisation. Module Management is where an administrator decides which are on. If a screen described in this documentation is missing from your sidebar, the usual reason is that its module is off here.
Before you start: only the Administrator role can open this screen. Select Module Management in the System group of the sidebar, or go to /admin/modules. The Modules reference lists every module with what it switches on.
Read the page
The header reads Module Management with the line "Enable and configure system modules for your organization". Refresh reloads the modules.
Modules appear as cards under five headings, called bundles: Core, Dispatch, Insights, Automation and Add-on. Each card shows the module's name and a switch. The switch reads one of:
When a module is on and has recorded a health state, a badge on the card shows Healthy, Degraded or Unhealthy. Degraded means the module works but something needs your attention. Unhealthy means it cannot work until a problem is fixed. Today the identity verification preflight is what records a health state, so other modules show no badge.
Hover over a card to open its detail panel: the description, its category and bundle, and the sections below.
Turn a module on or off
- Open Module Management.
- Select the switch on the module's card.
- Wait for the message. A successful change reads, for example, "Module Documentation enabled successfully". A refusal reads "Failed to enable module" or "Failed to disable module" followed by the module's name.
Sidebar links and header buttons that belong to the module appear or disappear to match. If one does not change, reload the page.
A module that has no saved choice starts on. The exceptions are Call Recording & Transcription and Timeclock & Payroll, which start off until you turn them on, and the two white-label modules, which stay LOCKED until TechPulse grants them. Turning a module on is the first step, not the only one: many modules need their own setup before they do anything, so also check the Configuration Required note on the card.
Open a module's own page
When a module with its own page is on, its detail panel has an Open Module button.
Check identity verification
The Identity Verification card has two buttons in its Health section when the module is on:
- Run preflight checks that identity verification is set up completely. It lists what it found, blocking problems first, with a suggested fix and a link where there is one, and it updates the card's health badge. A message summarises the result: how many checks passed, how many warnings, or how many blocking issues.
- Verify audit chain checks that the identity verification audit log has not been altered, and reports the result in a message and under the button. It needs an active identity verification configuration; without one it tells you there is nothing to verify.
Identity verification explains setup, and Credentials and the verification log explains the log these checks read.
StackJack Integration
StackJack Integration also needs server-side setup that TechPulse completes for you. Turn the module on here, then contact TechPulse to finish the setup; StackJack explains what it adds. When the module is on, a StackJack integration button appears in the header.
While the module is on, its card shows Configuration Required. The setup behind it is completed by TechPulse and not on this screen, and the card has no Open Module button.
What your team sees when a module is off
- The module's sidebar links and header buttons disappear. For example, an off Documentation module hides Documentation Admin, an off Timeclock & Payroll module hides Payroll Management and the Employee timeclock button, and an off Call Center Operations module hides the New call button.
- In Q-Director Settings, the Web Search, Guides and Call Taking tabs appear only while the Web Search, Interactive Guide and Call Center Operations modules are on.
- A few screens still open by address and explain why they are empty. The Customer Success dashboard shows "The Customer Success module is turned off for this tenant." and the QBR Studio pages show QBR Studio is turned off.
- Documentation sources do not sync while the Documentation module is off, and Qubit and the research notes do not search your documentation.
Modules that switch nothing today
Seven modules are listed here but switch nothing today: six in the Core bundle (Stale Analysis, Sentiment Analysis, Incremental Refresh, Sanity Scoring, 1M Context Window and Ticket Categorization) and Q-Notice Engine in the Automation bundle. Turning one of them off does not change what QuantumOps does. The matching capabilities are controlled elsewhere; the Modules reference says where for each one.
Related pages
- Modules reference: the full catalogue of modules.
- Roles and access: who can open each screen once its module is on.
Was this helpful?
Still need help? Ask the team