- Confirm that customers remain in good standing before they access paid features, such as products, plugins or enterprise features.
- Manage which features are available per client.
- Let Lerian scale support and sales operations.
The organization that makes the request must have a valid license. 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, Reporter.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_idthat will use the license. - For global plugins: inform Lerian that you need a global license. You do not need an
organization_id.
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.- LICENSE_KEY: The key provided by Lerian.
- ORGANIZATION_IDS: The ID of the organization linked to the license.
global in the ORGANIZATION_IDS variable.
- LICENSE_KEY: The key provided by Lerian.
- ORGANIZATION_IDS: Use the value
globalfor global licenses.
License-related errors
For an invalid or expired license, API responses or plugin behaviors may return one of these error messages:

