Modules

Tenvara is one product, but you do not have to take all of it on at once. Settings > Modules (in the Data and platform group) lists every module your licence includes and lets an administrator switch each one on when the team is ready for it, and off again. Only administrators can open it.

A new install starts with the service desk#

A new Tenvara starts small:

• Customers and devices is always on: customers, sites, contacts, devices and alerts are the records everything else hangs off.
• Tickets is on: the service desk, with tickets by email and the portal, queues, time and the people you support.
• Automation is on, because the service desk needs it: notifications by email, Teams and text, SLA escalations that page someone, and the on-call rota.
• In the Company edition, Monitoring is on as well, because an IT team's first job is its own devices.

Everything else your licence includes is there and switched off, one click away. An install that already ran an earlier version keeps every module it had on: upgrading never switches anything off.

The Modules page#

The page groups the modules:

Each module has a line on what it gives you, Needs: for the modules it cannot work without (for example Needs: Monitoring) and Used by: for the modules that rely on it. A module that is on shows Disable, and Set up when it has setup steps; a module that is off shows Enable.

The usual order, which Suggested next follows, is Monitoring, Remote access, Patch management, Backup, Documentation, Security, Microsoft 365, Scripts, Software, Scheduling, Projects, Reports, Chat, Device hardening, Printers, Infrastructure, Telephony and connectivity, and AI assist.

Switch a module on#

1. Go to Settings > Modules.
2. Press Enable on the module.
3. If it needs modules that are off, Tenvara says so first, for example "Patch management needs Monitoring, so it turns on too." Confirm to turn them all on.
4. When the module has setup steps, the setup assistant opens on them, so you can set it up straight away. A module with no steps just says it is on.

The module appears for everyone at once: its area or its menu items on the rail and the sidebars, its tabs and cards on customer and device pages, its results in search, and its blocks on Home. Its background work starts, and nothing has to be installed on devices: the agent already carries every module.

Tip: Switch modules on one at a time, as you move each job across from your old tools. Your team only sees areas that are ready, and the setup assistant walks you through each new one. See The setup helper.

Switch a module off#

1. Press Disable on the module.
2. Read what stops while it is off. If modules that are on need it, they are named ("Patch management needs Monitoring, so it turns off too.") and go off with it.
3. Confirm.

Nothing is deleted. Switch it back on and everything is where you left it.

Off really means off#

A module that is off is gone for everyone, whatever their role:

• from the rail, the sidebars, customer and device pages, search and the command menu;
• from Home and from Customise Home, and from the customer portal where it had a part there;
• its background work stops: scheduled jobs, syncs, checks and anything queued for it;
• it raises no alerts and sends no notifications;
• the agent's matching features stop on every device, whatever the device's own choice. The device page says the agent module is off on every device while its module is switched off.

Saved views on its data say the module is off. Alerts that were already open stay open, and records keep their links: a device on a ticket still opens, read only. When you switch the module on again, its work picks up at its next run and the agents get their features back as they were.

For example, while Monitoring is off the Devices area is hidden, and offline detection, checks, metrics and monitoring alerts stop. While Tickets is off, tickets from email and the portal, their SLA timers and service desk notifications stop.

The modules#

You can rename modules in Settings > Terminology; the Modules page and its messages use your names.

Turn on more of Tenvara on Home#

On an install that started small, administrators see a Turn on more of Tenvara card on Home while any module the licence includes is off. It names the next suggested module, what it gives and what turns on with it, with Enable (the same as on the Modules page), See all for the Modules page, and a button to dismiss it.

Dismissing it hides the card for every administrator on the install. Settings > Modules offers to show it on Home again while modules are still off, and the card goes by itself once everything is on.

Modules and your licence#

A module that is not in your licence shows under Not in your licence with no button, and stays off for everyone. Settings > Licence shows which modules your licence covers. See Licence and updates.

Modules and permissions#

Modules and permissions work together:

• A module that is off is hidden for everyone, whatever their permissions.
• A module that is on is shown to each person according to their level in Roles and permissions: None hides it, View shows it, Manage lets them change things.

So to hide an area from one group of people, leave the module on and set their level to None. To hide it from everyone, switch the module off.

Modules and the agent's own modules#

Devices and agent has a second list: the agent modules that run on devices, such as Patch management or Remote control, with a default for every device and a choice per device. While a Tenvara module is off, its agent features are off on every device anyway. While it is on, the agent modules decide which devices run them, so you can, for example, keep remote control off on one server.

Every switch on this page is recorded in the audit log.