Activate licensing and understand entitlement status

Open the status screen#

Open Licensing from System, Settings or the command palette. It is an app screen over the current canvas. The page reports product/edition, activation state, offline lease, machine binding, build integrity and entitled features. Use this actual status to determine what your installation can do; a saved chart, installed plugin or reachable broker does not itself grant a protected workload entitlement.

The displayed limits can include Concurrent sessions and Optimization population. The platform enforces admission for protected work. An optimisation request that exceeds a licensed population cap is different from a failed algorithm or missing market data. A successful past run does not prove a new request is within the current licence.

Activate an installation#

1. Confirm the app is connected to the intended AMM API server.
2. Open Licensing and wait for status to load.
3. Enter your Licence key and optionally an Installation name meaningful to you.
4. Choose Activate.
5. Read the action result and updated status, including entitled features and lease dates.
6. Use Refresh status if you need to read the current server state again.

A blank key produces an inline error without an activation request. If the page is already activated, New licence key and Activate with new key are the route for replacing its entitlement. Check the intended installation before applying another key. Do not publish licence keys or screenshots containing sensitive identifiers.

Status refresh and lease refresh are different#

Refresh status reads the backend's current licensing state. Refresh lease contacts the configured licensing service to renew the entitlement lease. Reloading the page does not necessarily renew an expiring lease. The offline timeline identifies Issued, Refresh required, Grace and Expires · protected work stops where supplied.

Refresh before leaving the installation offline, and verify the new dates after a successful lease action. Offline use depends on the actual signed lease and conditions; a network outage does not grant an unlimited extension. An amber rail status can indicate refresh is approaching. The page's dates include local timezone; retain the zone when recording a deadline.

Interpret the checks#

Machine binding compares the current installation's available hardware components with its entitlement's requirements. A hardware change can invalidate the expected match. Build integrity reports whether the host/native components satisfy the installation's integrity policy. Entitled features lists enabled/blocked capabilities separately from connection status.

Unknown values display as unavailable rather than zero. A failed status request is not evidence that the licence has expired; it can mean the API is unreachable. A loaded explicit expired/binding/integrity failure is different. Preserve the exact failure wording and status so the corrective action addresses the actual cause.

A development override, if displayed by a development installation, is environment evidence only. It is not a customer activation method or proof that a released protected build will admit the same workload. Use the entitled state of the actual installation you intend to run.

Diagnose activation or refresh failure#

First distinguish a page load error from an action error. Check Server connection and response time if status will not load. If activation/refresh returns “Licensing server not configured”, “Lease refresh unavailable”, “Activation failed” or another server message, use that detail rather than repeatedly changing the key.

Check the intended server/installation, network availability and whether the key belongs to the expected product/seat. For machine-binding or integrity failures, use the supported installation/update path and support channel. Copy the licence summary and sanitized diagnostics; do not bypass validation or edit cached signed entitlement files.

A backend action can return a response while reporting failure. Read its actual success/error status and updated entitlement, rather than assuming the absence of a transport exception means activation succeeded. After a successful action, check that the relevant feature and limit changed as expected before starting a large workload.

Deactivate deliberately#

Deactivate… opens Deactivate this installation?. Review the seat and running-work warning. Deactivation releases the seat through the licence service and clears the installation's cached entitlement; protected native execution requires a fresh valid entitlement afterwards. Running live sessions or optimisation can be affected, and the dialog lists relevant work it can identify.

Stop or safely manage that work before deactivating. Deactivation is not a broker flatten command and does not establish that broker exposure has closed. Do not deactivate merely to refresh the status or fix a chart display issue. Cancel leaves the installation active; confirm only when you intend the licence/seat change.

Share useful support evidence#

Use Copy licence summary from the Licensing rail menu where available. It includes edition, status, installation/lease identifiers and dates. Add the exact action attempted, sanitized error, app build and whether status/refresh could reach the server. Keep your secret licence key out of public bug reports.

If a protected operation is refused despite a valid licence, compare its requested sessions/population/features with the displayed caps, and inspect the workload's own error. Licensing, broker permissions, data entitlements and plugin availability are separate prerequisites; satisfying one does not resolve the others.

Continue with related tasks#

Configure appearance, safety and saved preferences, Save, share and organise workspaces.