13. Licensing & updates¶

Licensing¶

Licenses gate capacity/features per tenant. The Settings → License area shows current capacity and lets you configure license‑group prefixes used during onboarding.
In SaaS, licensing is tied to the tenant’s plan; in Self‑Hosted it is configured locally with a license key (see Installation).

Group‑based licensing & seat usage¶

When you assign Microsoft licenses through groups (group‑based licensing), Scalio Nexus surfaces live seat usage so you don't over‑commit:

The dashboard Seat usage card lists each licensing group's SKU(s) with used / total / free seats (member counts read live from Graph), colour‑coded by scarcity.
A low‑seat threshold drives an on‑screen banner and an optional Teams/email alert when a group runs low.
Onboarding is guarded: choosing a licensing group with no free seats blocks the create, so you never provision a user who can't actually be licensed.

Update manager¶

Settings → Updates surfaces available releases and “What’s new”.
When a release is detected, the Updates page indicates whether it is covered by your current license.
On Self‑Hosted, one click installs a covered release (or you can enable automatic updates); on SaaS, updates are applied centrally by the vendor.

Automated provisioning¶

For managed and automated rollouts, Scalio Nexus can be set up programmatically (creating the first admin, applying a license, and toggling sign‑in options) instead of clicking through the wizard. This is used by the SaaS platform and by scripted Self‑Hosted deployments; ask your vendor if you need it.