Licensing & Module Activation
How are modules activated for an organization — and what happens when a license changes?
An organization’s license is an encrypted file uploaded into administration: it names the organization, its deployment type, its expiry, and the modules it may run. The platform validates it on upload and gates every application and permission grant against it.
Where the control sits
Outside the organization
Encrypted, validated on upload
The license file is checked against the organization and read for deployment type and expiry — activation without external calls.
Module gating per organization
Only the modules the license names exist for the organization; grants cannot exceed it.
Per-user application licenses
Each account carries its own licensed applications and privileges, enforced at sign-in.
Read-only at expiry
Expiry downgrades privileges to read-only — records stay visible, changes stop.
Request-based extension
More modules or seats are requested and then provisioned — a controlled path, not an instant toggle.
InsideThe record inside Admin
How it works
Activation is a file, not a phone-home. The encrypted license is uploaded and validated in place — the organization name must match, the deployment type and expiry are read from the file — which suits self-hosted deployments where the platform runs inside your own environment.
Once active, the license is structural. It defines which modules exist for the organization, permission groups can only grant what it includes, and each user’s own license record scopes the applications and privileges materialized into their session at sign-in. When a license expires, privileges downgrade to read-only rather than shutting access to existing records.
Growing is a controlled path. Additional licenses or modules are requested from administration and provisioned by the platform operator — a deliberate request-and-provision boundary rather than instant self-service activation, so what an organization runs is always something both sides agreed to.
See licensing & module activation running in continON.
A guided walkthrough on a sanitized demo tenant — this capability inside its module, on the shared platform.