Activating your license key
Published:
Updated:
This article explains how to activate your MobilityManager license key for the first time, so your fleet, users, and modules are unlocked according to your purchased plan.
Before you begin
- You need the signed license key issued to your organization. It is a long, signed token (an RSA-signed JWT), not a short serial number.
- Activation is validated offline (air-gapped): the system checks the cryptographic signature locally, so no outbound call to a license server is required.
- Each installation holds exactly one active license. First-time activation only succeeds when no license is present yet.
Note: The very first activation happens inside the onboarding wizard, on the license step, before any account exists. Activating a replacement license later is done from the License management area and requires the softwareLicense:manage permission (held by SystemAdmin, or any custom role you grant it to).
Activate during onboarding (first run)
- Start the onboarding wizard on a fresh installation and continue to the license step.
- Choose the full-license option (as opposed to the 30-day demo).
- Paste your complete signed license key into the license key field.
- Submit the step. The system verifies the signature and expiry, then records the activation.
- On success you see the entitlements the key grants: expiry date and the seat limits for companies (tenants), vehicles, and users.
What activation records
When the key is accepted, the platform stores the license and binds it to this installation:
| Recorded value | Purpose |
|---|---|
| First activation date | Marks when this key was first activated on this system. |
| Activation fingerprint | A hash of machine characteristics used to detect a later database clone or restore onto a different host. |
| Last seen date | Updated hourly by the heartbeat to support clock-tamper detection. |
| Seat limits and module flags | Copied from the signed key so the UI and enforcement can read them quickly. |
If activation fails
- "Invalid license signature" — the key was altered, truncated on paste, or signed with the wrong key. Re-copy the full token from the original source.
- "License expired" — the key's expiry date has already passed. Request a current key.
- "License public key not configured" — the server has no verification key installed; contact your platform administrator.
- "A license is already activated" — a license exists. Use the update/replace flow instead of first-time activation.
Tip: If you only want to check a key without committing it, an administrator with softwareLicense:manage can validate a key first; validation reports the expiry and seat limits without installing anything.
After activation
Once active, the license immediately governs what you can create and which modules appear. You can review the current expiry date, seat limits, and enabled modules at any time from the license status view.
Related
- Activating a 30-day demo license and its limits
- Updating or replacing a license
- Viewing current license status and usage
- License expiry and renewal
AH
