Module Licensing
Requires Basic
This is where plan, modules, and limits come together: under Administration → License you see your installation’s tier, limits, and active modules; under “Show/hide categories” you control which licensed modules appear in the navigation. The plans: Community (no license), Basic, Professional, Elite, Enterprise — each with a fixed set of modules and asset limits.
In this section
Section titled “In this section”- How do I activate or deactivate modules? — tidy up the navigation, per instance or tenant
- How do I install a license? — license key, instance binding, and plan per tenant
- How do the limits work? — asset/tenant boundaries and what happens when they’re reached
Prerequisites
Section titled “Prerequisites”The Administrator role manages the license status and module visibility; instance-wide module settings and installing the license are the operator’s responsibility (Super Admin or server access). Viewing it is itself part of the core (all plans).
Plans at a glance
Section titled “Plans at a glance”| Plan | Modules (feature scope) | Asset limit |
|---|---|---|
| Community (no license) | Core, Assets, Network | 30 (1 tenant) |
| Basic | Core, Assets, Network | 250 |
| Professional | + Software, License management, Certificates, Compliance, Operations, SSO, Infrastructure & multi-tenant, Discovery, Flexible data | 2,500 |
| Elite | + Provisioning, Webhooks | 5,000 |
| Enterprise | Same as Elite | Unlimited |
Related topics
Section titled “Related topics”- Tenants — each tenant additionally has its own plan
- Webhooks — an example of an Elite feature
- SSO / OIDC — an example of a Pro feature