Activation Options and Capabilities
The application license determines whether a tenant can change data and whether it can operate as a product owner. It is separate from the product licenses that License Center creates for customers.
⚖️ Compare the operating modes
| Application-license state | What the tenant can do | What remains unavailable |
|---|---|---|
| No valid license | Sign in, inspect existing records, download previously issued licenses, read public verification keys, and import a replacement application license. | Protected changes, including product, license, user, company, order, integration, and signing changes. The tenant is read-only. |
Valid license without tenant-products | Manage its customer/reseller workspace, users, companies, orders, settings, and integrations. Consume valid received-order balances and issue licenses for products owned by another tenant. | Creating or changing tenant-owned products, managing tenant signing profiles or keys, directly issuing licenses for tenant-owned products, and re-signing those licenses. |
Valid license with tenant-products | Everything allowed by a valid application license, plus the complete tenant-owned product and signing workflow. | Operations that exceed a configured limit or are forbidden by the user's role, order authority, or record ownership. |
An expired, malformed, incorrectly bound, or incorrectly signed application license is treated like no valid license. Existing product licenses are not invalidated when the application becomes read-only; their signatures and expiration dates remain unchanged.
🧩 The tenant-products capability
tenant-products allows an activated tenant to:
- create, import, edit, and delete its own products;
- create and manage signing profiles;
- generate, import, activate, retire, or mark signing keys as compromised;
- assign signing profiles to tenant-owned products;
- issue licenses directly for tenant-owned products; and
- re-sign those licenses when their node, options, or expiration changes.
Tenant-product signing is part of this capability. There is no separate custom signing capability.
🚫 Working without tenant-products
A tenant with a valid application license does not need tenant-products to
consume a product entitlement received from another tenant. A received order
keeps the product read-only and authorizes issuance only within its available
balance. License Center uses the product owner's signing profile and key without
revealing the private key to the receiving tenant.
This mode is suitable for a customer or reseller that issues purchased licenses but does not maintain its own product catalog or signing authority.
📏 Licensed limits
The application license can also carry numeric limits:
| Limit | Effect |
|---|---|
admins | Maximum number of active tenant administrators. |
users | Maximum number of tenant identities that have not been deleted. |
products | Maximum number of products owned by the tenant. |
activeLicenses | Maximum number of active, unexpired licenses for products owned by the tenant. |
A configured value of 0 prevents creating the corresponding record. An
omitted limit is unlimited. Received products and licenses issued from received
orders do not consume the tenant-owned products or activeLicenses limits.
🛡️ License Center product trust
The name LicenseCenter is ordinary product catalog data and does not grant
application-activation authority. A license for that product activates License
Center only when its signature validates against an embedded Impleo public key.
A tenant signing key cannot create a trusted License Center application license,
even when the token contains tenant-products and otherwise correct claims.
See Application Activation for installation and renewal instructions, and Products and Signing for the product-license workflow.