Module toggles
For adminsModule toggles
Section titled “Module toggles”A workspace doesn’t need to use every product. A primary school running Keystone for helpdesk and SCR only doesn’t want Estates and Assets cluttering the navigation. The modules page lets a trust admin toggle each product on or off per workspace.
What you can toggle
Section titled “What you can toggle”Whichever modules the install has registered. Out of the box:
- Helpdesk — tickets, changes, problems, projects.
- Assets — IT asset register, stocktake, discovery.
- Estates — buildings, compliance, visitor management.
- Governance — risk, policy, meetings, declarations.
- SCR — Single Central Record.
- People — employee records, engagements.
- Health & Safety — RAs, checklists, incidents.
The list is driven by what each module’s WorkspaceProduct registers in its ServiceProvider — adding a new product to the platform automatically surfaces a switch here.
What “disabled” does
Section titled “What “disabled” does”Disabling a product:
- Hides it from the agent shell, the
/meportal, and the command palette. - Leaves routes reachable — deep-links don’t 404. The product just doesn’t surface in navigation.
- Leaves data intact — assets, tickets, policies stay in the database. Nothing is deleted or archived.
Re-enabling restores access immediately. There’s no rebuild step.
When to disable
Section titled “When to disable”- The trust isn’t using the product. Hide it to reduce noise for staff.
- A pilot period is over and the trust decided not to adopt — disable, leave data for audit, prevent further use.
- Temporarily during a migration where the data needs to be untouched.
When not to disable
Section titled “When not to disable”- Don’t disable for “data cleanup” reasons. Disabling doesn’t clean anything — it just hides.
- Don’t disable mid-incident. If staff are actively using a product to report something, hiding it removes their access.
Gotchas
Section titled “Gotchas”- Disabling a product doesn’t revoke any user’s role for it. A staff member with
assets::agentwho works in a workspace where Assets is disabled still has the permission — they just can’t see it in the rail. - Routes stay served — a bookmarked direct link
/agent/assets/dashboardstill works. If you need to fully prevent access, change the permission, not the module toggle. - Toggles are per-workspace. Multi-tenant installs need to toggle in each workspace.