Enable / disable modules

Each of the four modules — Live Chat, Knowledge Base, Contact Pages, Tickets — can be toggled independently from Settings → Modules.

What "disabled" means

When you disable a module:

• The sidebar entry disappears for everyone in the workspace.
• Public URLs for that module return 404 (acme.nura24.com/help for KB, /contact for Contact, /tickets for the customer portal).
• The chat widget stops loading on the visitor's side if it was Chat that you turned off.
• The module's data stays in the database. No deletion, no migration loss.

When you re-enable, everything reappears exactly as you left it. There's no "restore" step.

When you might want to disable

• You only need one or two modules — keep the dashboard uncluttered.
• You're temporarily pausing customer-facing surfaces (holiday, maintenance, pre-launch). Disabling the Contact module is faster than removing all its blocks.
• You hit a plan limit and want to free a slot without deleting. Disabling a module doesn't usually affect limits, though — check your plan first.

Modules with dependencies

• The Customer Ticket Portal module is separate from the Tickets module. The customer-facing portal at /tickets only renders when Tickets Portal is on; the agent-side Tickets module can be on by itself if you're not surfacing tickets to customers yet.
• AI features are gated by their own toggles under Settings → AI — disabling Tickets disables ticket-AI features by association.

Permissions

Only Owners and Admins can change module settings. Agents see whatever modules are currently enabled.