Modules

Admin, Features (/admin/features), gated by the feature.manage permission.

Every feature in Plugboard is a module. Turning one off hides its navigation and stops its endpoints answering, so a school that never runs inductions or a printer fleet does not see either.

This is the master switch list. Every environment is different, and the honest default is to enable only what you use.

Using the screen

Each module shows its name, a one-line description and an Enabled or Disabled pill. Click the pill to toggle it. Some modules expand to show a link to their configuration page.

Changes take effect immediately. A technician with the console open will see the navigation change on their next page load.

The modules

Core work

Module	Key	What it gives you
Submissions	module.repairs	The repair queue: lodge and track repairs, loans on repair, outcomes and costs
Tickets	module.tickets	The built-in service desk queue for work that is not a device repair. Switch it off if you use an external ticketing system
Loans	module.loans	Issue loan laptops and iPads, and track who has what
Stock	module.stock	Sell and track consumables: cables, adapters, bags
Cost analytics	module.costs	Break repair spending down by type, term and coverage

People and devices

Module	Key	What it gives you
Device inductions	module.inductions	Start-of-year handout checklists, with roster import and tracking
Card checker	module.cardChecker	Tap-to-verify student and staff cards against the directory
Asset lifecycle and stocktake	module.assets	Device lifecycle fields, warranty tracking and scan-the-room audits
Directory management	module.directory	Manage Entra, Google and AD users: licences, lock, inbox delegation, password reset

Infrastructure

Module	Key	What it gives you
Printers	module.printers	Live printer fleet: toner levels, status and errors over SNMP
Services monitor	module.monitors	Uptime-style monitoring of internal services with severity-based alerts
Security	module.security	ThreatLocker approval requests, ticket-linked, with per-device history

Service quality

Module	Key	What it gives you
Service levels	module.sla	Resolution targets per priority, with overdue flagging and alerts
Satisfaction	module.csat	Post-repair star rating on the tracking page, summarised on the dashboard
Reports	module.reports	Operational reports with CSV export and scheduled email delivery
Automation rules	module.automation	When a new submission matches conditions, auto-assign, set priority or notify
Knowledge base	module.knowledgeBase	Self-help articles surfaced on the public help page
Public status page	module.statusPage	Community-facing uptime page driven by your monitors

Platform

Module	Key	What it gives you
API and webhooks	module.integrations	Public API keys, signed outbound event webhooks, and the MCP endpoint
Backups	module.backups	Encrypted scheduled backups and portable per-tenant export

Portals

Module	Key	What it gives you
Student portal	portal.client	Let students look up their own repairs, loans and purchases, and lodge new ones
Parent portal	portal.parent	Let parents view their child’s repairs and, optionally, costs

What depends on what

Modules are mostly independent. The exceptions:

• Cost analytics is fed by outcomes recorded on submissions. With module.repairs off, there is nothing to analyse.
• Satisfaction ratings are collected on the repair tracking page, which exists because a submission exists.
• Public status page shows monitors marked public, so it needs module.monitors to have anything on it.
• Knowledge base articles appear on the public help centre. The help centre is public and does not need a module of its own, but with no published articles it is empty.
• Stocktake and disposals both live under module.assets.
• The MCP endpoint is part of module.integrations. With that module off, /api/mcp returns 404.
• Automation rules run on submission creation, so they need module.repairs.

Configuration links

Several modules expand to a link to their settings:

Module	Configuration
Tickets	Categories, queues, canned responses, reopen window
Loans	Loan groups
Service levels	Response and resolution times per priority
Reports	Run reports or schedule emails
Automation	The when-then rules
Knowledge base	Write and publish articles
Public status page	View it, and mark monitors public on the Monitors page
Asset lifecycle	Stocktake, audit devices by location
Directory	Search and manage accounts
API and webhooks	Issue keys, add webhooks
Backups	Schedule, run and verify

Modules and your licence

Your plan determines which modules you are entitled to. A module you are not licensed for cannot be enabled, and the Features screen says so rather than letting you switch on something that will not work.

Tier	Adds
Core	Submissions, tickets, loans, assets, directory, knowledge base
Standard	Stock, costs, card checker, inductions, both portals, SLA, satisfaction, reports, status page, API and webhooks
Advanced	Automation, monitors, printers, security, backups
Enterprise	Everything, and negotiated additions

Full detail in plans and licence and plan.

Disabling a module at the deployment level

A self-hosted deployment can hide modules for everyone, regardless of what a tenant administrator does:

DISABLED_MODULES=module.cardChecker,module.inductions

Useful when a school has decided centrally that a feature is not to be used. It is a blunt instrument: the module cannot be re-enabled from the interface while the variable is set.

What happens to the data

Disabling a module hides it. It does not delete anything. Turn it back on and everything is where you left it.

The one thing to think about before switching something off in a live system is whether people are relying on it right now. Turning off Loans while devices are out means nobody can return them until you turn it back on.