Skip to main content

Platform Administration

Platform administrators create hosted tenants and manage their application activations. Open Settings ยท Admin ยท Tenants.

Platform administration overview: create a tenant, import its externally issued activation, and optionally forward an order. The receiving tenant can issue node-bound product licenses from the remaining balance without accessing the source signing key.

Forwarding an order is optional and is available to platform administrators in the main tenant.

๐Ÿ  Main tenantโ€‹

The first tenant created during setup is the main tenant. Its designation does not depend on its name, issuer, or signing key. The main tenant cannot be deleted. Every tenant starts without products and manages its own product catalog and keys.

๐Ÿข Manage tenantsโ€‹

Create a tenant with its name, code, and initial administrator credentials. The tenant list shows activation status, users, products, and active licenses. Edit tenant names, codes, and status as needed. Deletion is blocked for the current or main tenant, and when another tenant still references its records.

โœ… Activate a tenantโ€‹

Use the license action beside a tenant to copy its activation request, upload an externally issued .lic file, inspect validation status, or remove activation. Each tenant retains its own capabilities and limits. License Center validates application licenses but does not issue them. A product signing profile cannot activate a tenant by itself.

๐Ÿ“ค Forward an orderโ€‹

Platform administrators in the main tenant use Orders ยท Forward to tenant. Select the receiving tenant, its customer company, and optional purchaser. The original product identities and snapshots are retained. Remaining product and option balances can be consumed only by the recipient after forwarding.

Products and keys remain owned by the main tenant. The recipient sees received products as read-only and issues node-bound licenses using the owner's signing profile without accessing its private key. It cannot enlarge the allocation, forward it again, or delete licenses issued against received balances.

Historical licenses stay in the source tenant. Returns of their balances credit the recipient once. WooCommerce payment, status, and completion rules continue to apply. See Orders for details.

Secondary tenants can also create products and signing keys and issue their own licenses, subject to their application activation. Tenant ownership is enforced for products, profiles, keys, and ordinary orders.