Licenses

Access Prerequisites

• Permission (module): viewLicenses
• License/Feature: None
• Menu container: GENERAL → Audit group

What it is / when to use

The Licenses screen (/licenses) lists all platform features and indicates whether each one is enabled or disabled for the current tenant. Features are defined by contract and centrally controlled (ConfigurationReaderService / Vault).

Use this screen to quickly verify which features are enabled — useful for diagnosing "why a given menu/resource is not showing up for me". If a feature is disabled, the menu items and screens that depend on it do not appear at all for any operator.

Prerequisites

• Permission: module viewLicenses. Permission is dual — CPM enum on the backend + dynamic module in the DB.
• License/Feature: none.
• Dependencies on other screens: statuses are read in real time from the configuration service; there is no registration on this screen (it is read-only).

Step by step

1. Open the menu GENERAL → Audit → Licenses.
2. The screen queries the status of each feature from the FeatureNames enum, one by one, and builds the table.
3. Check the Status column to see whether the feature is enabled.

Filters and columns

Column	What it shows	Data source
Name	Feature name (e.g.: DIGITAL_BANKING, CREDIT_INVESTMENTS, MANAGE_TOKENS)	FeatureNames enum
Status	Enabled/disabled for the tenant	FeaturesStatusService.getFeatureStatus(feature) (reads from ConfigurationReader/Vault)

Actions and modals

• Open documentation: the documentation button opens the external documentation portal (window.open) — general reference, does not change anything.

Business rules / important notes

Attention

• This screen is read-only: the operator cannot enable/disable features here. Configuration is done centrally (contract + Vault). Changes require action from the team responsible for the tenant's license.
• A disabled feature = menu item disappears. Before opening a ticket about a "missing screen", confirm here whether the corresponding feature is enabled (e.g.: DIGITAL_BANKING for digital banking, CREDIT_INVESTMENTS for tokenised credit).
• The permission × license relationship is independent: even with the feature enabled, the operator needs the corresponding permission module to view/use the screen (permission is dual).

Related screens

• Digital Banking creation failures (depends on DIGITAL_BANKING)
• Audit (overview)