Skip to content
LLicentivo
Open console

Customer portal

Customers can check licenses, view devices and unbind them without entering the vendor console.

Vendor links the customer email first

Enter customer email on issuance or under Entitlements and customer. Send the Customer portal link to the customer. Entering that email sends a one-time login link, valid for 15 minutes. The login session lasts 24 hours.

Customers see only licenses linked to that email, not your product management, bills or other customers' data. Configure the email service in administrator settings first.

What if the customer lost their key when changing computers?

  1. The customer enters the license's linked email and opens the login link sent there. This link logs them in; it does not unbind a device.
  2. Under My devices / sessions, choose the old computer, Deactivate and transfer, then confirm.
  3. The page shows a temporary activation code, valid for at most 15 minutes and one successful activation. Customers can copy it or choose to email it to themselves.
  4. On the new computer, open your app and enter the temporary code on its activation screen. The SDK identifies the computer, binds the original license and saves device credentials. Restarts and heartbeats use those credentials; code expiration does not affect the activated computer.

This changes only the device binding. License ID, original expiration, features, customer and consumed usage remain; no new license is issued. The new device must meet the original policy and have an available device slot.

What does the software vendor need to change?

Upgrade to the current SDK. The field that accepts license keys can also accept lv_tmp_ temporary transfer codes; put one in the config's license_key is sufficient; Start, validation and heartbeat work as usual. The SDK saves the device credential in a private cache directory;cache_path can be empty. Keep this file in the current user's application data directory; never distribute it with the installer.

After successful redemption, the app can clear license_key blank; keep the same product, public keys and cache_path, the SDK restores device credentials on restart. Customers need not save or re-enter the temporary code. Until redemption succeeds, keep their input so it can be retried after a disconnection.

If the code expires or this page is closed

Log into the portal again to see unused codes. After an unused code expires, choose View/get activation code beside its released device to reissue it without another transfer count. Used codes cannot be redeemed again or repeatedly issued from old records to bypass limits. For another transfer, unbind the currently active device.

If the new computer is fully offline

Enter the temporary code on the new computer and export an activation request with the SDK. Before the code expires, take it to an online computer and get a portal response, then import it on the new computer. The policy must allow offline device-bound activation. The original license term remains; protect the response containing this machine's authorization and credentials.

Deactivation limits and the old computer

Set self-service release limits in the policy, per license per UTC month. Zero disables new portal unbindings. Repeated clicks, viewing codes and reissuing expired unused codes do not add counts. This limit covers the portal and customer offline release requests, not manual vendor releases or software release calls using the original license key.

Remote unbinding blocks the old device's next online check. Existing offline caches remain until checking online or expiring. Permanent offline caches cannot be stopped immediately remotely; use periodic online policies when prompt revocation matters. Ordinary copies of configuration, credentials and caches on another computer are rejected because its machine identity differs.

The customer portal manages license use. Vendor orders and software sales payments remain in the vendor's own system.

To connect post-purchase license delivery, customer self-service renewals and upgrades, use Licentivo Launch's purchase and customer-care workflow. Launch manages orders and purchase entitlements; the software still uses the SDK to check actual access.