Managing Existing Licenses
Administrators see tenant licenses. Regular users see licenses they issued or that are assigned to them. The Imported badge identifies a preserved external JWT rather than a license issued from this installation.
👁️ Preview and download
Choose Preview license and JWT to inspect the license and decoded token.
Decoding displays the stored claims; it is not a substitute for signature
verification in the consuming application. Download license saves the signed
token as a .lic file, using the display title as the filename.
📤 Send a license
Choose Send license to customer. The To address is the assigned user's email and is read-only. Optional CC, BCC, and Additional message fields supplement the active Send license template. Separate multiple addresses with commas, semicolons, or whitespace. The signed file is attached.
The action requires configured tenant email settings and a recipient email. When sending is disabled in Settings, it displays a preview without sending. Successful deliveries appear in Emails. Sending an existing license does not issue a new one or spend another order unit.
➕ Add purchased options
Regular users and administrators can choose Add Options, immediately before Download license, on a license they can access. This opens Modify license.
- Select a Processing order whose balance you may use for the license recipient. The product is fixed to the existing license and its matching balance is selected automatically. Choose a balance if the order contains several matching lines.
- Keep or change the license title and select additional purchased options. Existing options stay selected and cannot be removed. Node information, QR scanning, recipient, expiration, notes, and restrictions cannot be edited here.
- Review the additions and resulting balances, then choose Modify & sign. You can optionally email the updated license to the customer.
Each addition consumes one unit of that option from the selected order. No base product unit is consumed, so orders with exhausted base balances can still supply options. Repeat the operation to use options from another eligible order. Download or send the updated file; customer copies of the earlier file are not replaced. Expired licenses keep their existing expiration. Revoked licenses cannot be modified. If someone else changes the license, reopen the dialog to load its current version.
📥 Imported licenses
An administrator first uses Link product to associate an imported license with its catalog product. The product must have an authorized signing profile that can verify the original signature and an active private key for signing updates. A matching product name alone is insufficient. The link cannot change after the first option purchase. Once linked, regular users can add options themselves using their authorized order balances.
The original imported token and verification evidence are retained. The current signed token receives the additional options while its other claims remain fixed. If the original signing authority is unavailable, Add Options is unavailable.
✏️ Edit a license
Administrators can select Edit license to change the display title and notes. These changes do not alter the signed token. For licenses issued by License Center, administrators can also edit node information, options, and expiration:
- A signed-claim change re-signs the license with the profile's current active key. Download and deliver the updated file afterward.
- Adding order-backed options consumes their remaining quantities; removing options returns those quantities. Adding options or extending expiration requires an eligible Processing order.
- Tenant-owned signed changes require the
tenant-productscapability. Received-product licenses must remain node-bound and use the owner's signing authority. - This editor permits only title and notes changes for imported licenses. Use Add Options for purchased additions after linking a product.
The recipient, product, and original issue time are not editable here. Existing copies of an earlier token are not remotely replaced when an edit is saved.
🕘 License version history
Regular users and administrators can choose View history on any license they can access that has saved previous versions. The button is hidden when there is no history. Every successful Add Options or Edit license operation saves the previous title, options, license details, and exact signed file before replacing that version. A title-only or notes-only edit also preserves the previous record.
History shows the previous version number and title, when it was saved and
replaced, and who made the change. Select View version to inspect its details
and signed JWT, or Download previous version to save its unchanged .lic file.
The download name includes the old title and version number. The current license
continues to appear as a single record on the Licenses page, under its latest title.
Previous versions are read-only references. They cannot be edited, restored as the current version, or deleted separately. Viewing and downloading them does not consume or return balances. Deleting the parent license removes its history and returns only the license's outstanding purchased entitlements once.
History starts with edits made after this feature is installed; it cannot recover files overwritten before then. Product linking and revocation are operational changes, not archived edits, so history version numbers can have gaps. Original imported-token evidence is still preserved separately. Saving a new version or revoking a record does not invalidate an older signed file already downloaded by a customer; validity depends on the consuming application's verification rules.
🗑️ Delete licenses
Administrators can delete one license or select several and choose Delete selected licenses. Deletion is permanent and returns outstanding order entitlements to the orders that supplied them. For imports, only options purchased through Add Options are returned; options present in the original import are not credited. Licenses issued using received orders, including imported licenses upgraded with received balances, cannot be deleted; if any selected license is protected, the whole bulk deletion fails without deleting the others.
If a source order has since been forwarded, returned historical entitlements credit its receiving tenant. Returning balance does not reopen a Completed WooCommerce order. Deleting a record does not invalidate copies of its signed file already held by customers.
⛔ Revocation is an API operation
The backend supports license revocation, optionally returning consumed balances, but the current Licenses page has no Revoke action. Revocation records a status change; it does not rewrite the customer's signed token. Imported licenses can optionally restore options purchased through Add Options when revoked. A consuming product must implement its own revocation checks for that operational status to affect use.