Skip to main content

First Run

The first person to open an unconfigured License Center creates the initial tenant and administrator account.

What is a tenant?

A tenant is an isolated workspace for one organization. It contains that organization's users, companies, products, orders, licenses, settings, and tenant-owned signing configuration. Users in one tenant cannot access another tenant's business records or private signing material.

Usage example: If Northwind Media and Contoso Broadcasting are separate customers, create a tenant for each organization. Their administrators manage their own users and licensing records independently. During first run, create only the tenant that will own the initial administrator account; a platform administrator can add other hosted tenants later from Settings ยท Admin ยท Tenants.

๐Ÿ—๏ธ Create the workspaceโ€‹

Enter the tenant name, a lowercase tenant code, and the initial administrator's credentials. Tenant codes may contain lowercase letters, numbers, and hyphens. The code identifies the tenant in administration, access requests, integrations, and public tenant endpoints. Users do not enter it during routine sign-in.

The first workspace is the main tenant and its initial administrator has platform administration permission. This designation does not depend on the organization name or signing key. All tenants start with an empty product catalog.

๐Ÿ—๏ธ Choose a signing-key optionโ€‹

The setup wizard offers three choices:

  • Generate a key creates a new tenant signing key. Supply a strong export passphrase and save the encrypted private-key export when it is shown.
  • Import a key accepts an existing private key and optional public key for verification. Supply the private-key password when the PEM is encrypted.
  • Configure later creates the workspace without a tenant signing key. An administrator can add a signing profile and key from Settings later.

When generating or importing a key, select Vendor RS256 v1 or Legacy License Manager RS256 to match the applications that verify your licenses. Importing a key does not install products or grant additional authority.

The one-time encrypted private-key export cannot be reopened after its dialog is closed. Store it in an approved secret-management or offline backup system.

โœ… Activate the applicationโ€‹

After setup, the initial platform administrator can open Settings ยท License and copy the activation request. Send that request to the external activation issuer. Upload the returned .lic file using Upload license on the same page.

Without a valid activation, the application is read-only. Activation limits can govern administrators, users, products, and active licenses.

๐Ÿ“‹ First operational recordsโ€‹

Create companies before users when you want to associate people with customer organizations. Then create or import products and create orders before issuing an entitlement-backed license. Existing product JSON files remain supported.

The main tenant can forward an order from Orders to another tenant. The recipient uses the original owner's signing authority within the received balance, without access to the private key. Secondary tenants with the tenant-products application-license capability may also create their own products and keys and issue licenses independently.