Skip to main content
A license is a key that authorizes access to Lerian features or services under specific contractual conditions, typically aligned with billing cycles (e.g., monthly, annual). This mechanism is similar to how software products like Microsoft Office or GitHub Enterprise manage access through activation keys. In Lerian’s ecosystem, licenses play a critical role in:
  • Ensuring customers are in good standing before accessing paid features, such as products, plugins or enterprise features.
  • Managing which features are available per client.
  • Enabling Lerian to scale support and sales operations securely and efficiently.
In short, only clients with valid licenses, as defined in their contracts, can access specific software components.
A valid license must be associated with the organization making the request. Otherwise, access will be denied.

​
License types

In Lerian’s ecosystem, licenses can have two different scopes, depending on the plugin:

​
Organization-specific licenses (non-global)

Applies to a single organization. Example: Fees Engine, CRM, Reporter.
You can use the license with any number of ledgers inside that organization.

​
Global licenses

Valid for multiple organizations. Example: Access Manager.

​
License usage workflow

The steps below apply to both license types:
1

Submit a license request to Lerian.

  • For organization-specific plugins: provide the organization_id that will use the license.
  • For global plugins: inform Lerian that you need a global license; no organization_id is required.
2

License generation and activation by Lerian

Lerian’s team follows the internal process to create and activate the license using the provided details.
3

License key delivery

Lerian sends the License Key (LICENSE_KEY) to the client.
4

Environment configuration

Once you receive your license key, you must configure your .env file so the system knows which license to validate and which organizations it applies to.
Always configure the correct environment variables before using a plugin. Incorrect or missing values will result in license validation errors.
Organization-specific licenses (non-global) These licenses apply to one organization only.
  • LICENSE_KEY: The key provided by Lerian.
  • ORGANIZATION_IDS: The ID of the organization linked to the license.
Global licenses These licenses have a global scope and must always use the value global in the ORGANIZATION_IDS variable.
  • LICENSE_KEY: The key provided by Lerian.
  • ORGANIZATION_IDS: Must be set to global for global licenses.
When a license is invalid or expired, API responses or plugin behaviors may return one of the specific error messages:
For more information about your license or to request an upgrade, please contact the Lerian commercial team.