April 16, 2026 Documentation update Review recommendedDocumentation Index
Fetch the complete documentation index at: https://docs.lerian.studio/llms.txt
Use this file to discover all available pages before exploring further.
Affects
Teams configuring Ledger Settings in Midaz. This update applies to the public documentation portal. It does not change the runtime API behavior unless the linked product documentation says otherwise.
What changed
You can now manage validation rules for individual Ledgers directly from the Console—no environment variables or config files required. A new Settings tab is available when editing a Ledger, allowing you to control two validation rules:
Validate Account Type
Restricts account creation to previously registered Account Types. When enabled, the Account Types menu becomes available in the sidebar.Validate Routes
Ensures all transactions follow predefined routing rules. When enabled, the Transaction Routes and Operation Routes menus are activated. A dedicated documentation page has been added, covering access, available settings, warnings, and API references. This content is available in English, Portuguese, and Spanish.Updated
Editing a Ledger
The Ledger editing sidebar now documents all available tabs—Details, Metadata, and Settings—and includes a direct link to the new Ledger Settings documentation.Managing Account Types
Account Type validation is now configured through the Console UI instead of environment variables.- Removed
.envconfigurations (MIDAZ_ACCOUNT_TYPE_VALIDATION_ENABLED,MIDAZ_ACCOUNT_TYPE_VALIDATION) - Added step-by-step instructions for enabling validation via the Settings tab
- Fixed terminology: “Asset Types” → “Account Types”
Transaction Routes & Operation Routes
Both pages now include a prerequisite: Validate Routes must be enabled in Ledger Settings for the corresponding menus to appear in the sidebar.Managing Ledgers
The Ledgers overview page now includes a dedicated card linking to the new Ledger Settings documentation.Impact
This is a documentation update. Existing integrations do not need a migration from this release note alone.

