How do I activate or deactivate modules?

Requires Basic

Short answer

Under Administration → Show/hide categories you hide modules your team doesn’t use — they then disappear from the navigation. The Scope toggle chooses between “This tenant” and “Whole instance” (the latter only as Super Admin). Important: this is purely about visibility. Modules your plan doesn’t include are locked (“from Pro” / “from Elite”) and can’t be unlocked by showing them — that requires a license.

Prerequisites

All modules except the core can be hidden: Assets, Network, Software, License management, Certificates, Compliance, Operations, Flexible data (custom fields), Network discovery, Provisioning, Webhooks, Single sign-on, Infrastructure & multi-tenant.

Open module management. Administration → Show/hide categories (“Turn off modules you don’t use - hidden ones disappear from the navigation. Modules not included in your plan are locked.”).

Screenshot pending admin-module-lizenz-01 The 'Show/hide categories' module management with toggles per module and a scope selector

One toggle per module; plan-locked modules show 'from Pro' or 'from Elite'.
Choose the scope. “This tenant” affects only your tenant’s users; “Whole instance” (Super Admin) hides the module for all tenants.
Toggle modules. Turn off, for example, Certificates and Compliance if you don’t use them — the navigation immediately becomes leaner. Locked modules carry the note “from <plan>” and can’t be activated.

Visibility is controlled by /api/v1/admin/modules with the query parameter scope=tenant|instance:

curl -H "Authorization: Bearer inv_dein_token" \
  "https://demo.notory.io/api/v1/admin/modules?scope=tenant"

{
  "scope": "tenant",
  "hidden": ["certificates"],
  "modules": [
    { "key": "assets",       "entitled": true,  "hidden": false },
    { "key": "certificates", "entitled": true,  "hidden": true },
    { "key": "webhooks",     "entitled": false, "hidden": false }
  ]
}

curl -X PUT "https://demo.notory.io/api/v1/admin/modules?scope=tenant" \
  -H "Authorization: Bearer inv_dein_token" \
  -H "Content-Type: application/json" \
  -d '{ "hidden": ["certificates", "compliance"] }'

Instance-wide, analogously, with scope=instance (Super Admin only).

Possible errors: 403 (“Only a super-admin can change instance-wide module visibility”), 422 (invalid scope). Unknown module keys in hidden are cleaned up.

What happens behind the scenes?

Three conditions for visibility. A module appears in the navigation if it (1) is included in the plan (entitled), (2) is not hidden instance-wide, and (3) is not hidden for the tenant. Plan-locked modules stay hidden or marked as locked regardless of the toggles.
Visibility ≠ permission. Hiding a module tidies up the UI, but it is not a security measure: the module’s API endpoints remain usable for authorized users. You control access via Roles & Permissions; you control the feature scope via the license.
The frontend reads entitlements. The UI queries GET /api/v1/entitlements once and locks navigation and buttons in advance — instead of letting users run into 403 errors. Locked modules show the upgrade hint (“The {module} module is not included in your current plan ({tier})”).
Two levels, clear precedence. The instance-wide list (Super Admin) overrides the tenant list: what the instance hides, a tenant cannot show again.
The core always stays on. Dashboard/core functions cannot be turned off.