LicenPro
DocumentationPlatformActivations

Activations

Devices and environments that consumed a license seat. Global monitoring, per-license tab, block/unblock, node-locked approval, and Perpetual vs Concurrent behavior.

An activation records that a specific machine, user, or environment has claimed capacity on a license. Node-locked and concurrent models depend on activations; perpetual online tracks them for compliance and audit.

Combined walkthrough with sessions: Sessions & activations guide · Perpetual · Node-Locked.

Activation lifecycle

  1. Client activates — SDK validation or ActivationManager with hardware fingerprint / device id.
  2. Server records — activation row: license id, device info, timestamp, status (active, pending approval, blocked).
  3. Enforcement — seat limits block new activations when max reached.
  4. Node-Locked approval — pending row until product owner approves (when binding mode requires it).
  5. Block — operator blocks suspicious device; client fails on next online check.
  6. Deactivate — client or operator releases seat for reuse.

Global Activations page

Sidebar: Activations. Cross-product view when you do not yet know which license key is involved.

Click image to open full-resolution preview.
  • Search — license key, device fingerprint, user email, machine name.
  • Status filter — active, blocked, pending, deactivated.
  • Date presets — 7D / 30D / 90D / all / custom range for incident windows.
  • Block / unblock — force deny on next online check without deleting history.
  • Edit notes — support annotations visible to other operators.
  • Drill-down — open activation detail or jump to parent license.

API scopes list products you own or administer.

Per-license Activations tab

Faster path when support already has the license key. Same block/unblock and approve semantics as the global list but pre-filtered to one license.

Click image to open full-resolution preview.

By license model

ModelActivations roleTypical list display
Node-LockedPrimary enforcement — one bound device; approve pending binds1/1
ConcurrentSeat cap on registered devices3/5
Perpetual onlineAudit / optional max activations2/∞ or capped
FloatingDevice registry; seats often from sessionsVaries
Credit-Based / Usage-BasedDevice tracking optional; usage on Usage tab
Offline perpetual / trialMay not create online rows

Roles

  • Product owner / Admin — view global list, block/unblock, approve node-locked devices, per-license tab.
  • Member / Viewer — no activations management UI.

Activations & sessions API · SDK activation · Sessions