Portail ZAPP

Manage licenses, the catalog and keys

Available in en es fr

Updated on 10/25/2026

The Licenses menu (/licences) is ZAPP's license server. It is reserved for administrators and the LICENCE_MANAGERS group.

Licenses

The list can be filtered by organization and status. Creating a license takes two steps: the organization, the product and the instance (required, the ID shown on the instance's license screen), then the content:

  • the subscribed offer, or a custom license, with modules added or removed;
  • follows the offer (the license takes the latest offer version at each issuance) or frozen (it keeps the subscribed version);
  • features added to those of the offer, for example sla-multi-policy when the multi-policy SLA option is sold on its own;
  • production or non-production; named user pools (code;quota;Modules;label;features, one line per pool; a pool may cite the esm-work scope, ESM work; the pool features, optional, apply only to its seat holders, for example the options of the CRM Advanced tier, and are chosen from the list shown under the field); limits (warn or block); enforcement level (Off, Warn, Enforce);
  • contract start and end, and the payment line that covers it, if any.

The license page shows the resolved modules and every issuance. Revoke withdraws the license: it is no longer issued and appears in the instance's revocation list. A license created from an activated quote carries a firm commitment: until its end, no fewer seats, no module removed, no offer change.

A license covered by a suspended payment line is revoked automatically ("Suspended for non-payment") and restored when the line is paid.

Customer codes

Customer codes (/licences/customers): each organization receives a CLI-00001 code, on request or with its first license. This is the customer ID an instance administrator enters. It is never changed or reassigned.

Catalog

Catalog (/licences/catalog): products (their code is the one in license tokens and can no longer be changed), their sellable modules and their offers. Changing an offer's content creates a new version: frozen licenses keep the old one. A module installed at a client and unknown to the catalog is added as discovered, not sellable.

Keys

Keys (/licences/keys): the support's signing and encryption keys. Only the public parts are shown. You can create a key, activate it, back it up and restore it.

See also

  • "Track instances, activation codes and files".
Applies from version 0.1 Verified for version 0.1

Was this article helpful?

Still need help? Create a request