> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lerian.studio/llms.txt
> Use this file to discover all available pages before exploring further.

# Initiating with Enterprise Model

> Set up Lerian Enterprise in the right order to onboard product, engineering, and ops teams across Midaz, Access Manager, and plugins.

<Note>
  This guide is for **Enterprise Model** users with access to **Midaz** and **Access Manager**. It also shows how to configure the **Fees Engine** and **CRM** capabilities that ship inside Midaz, and how to add **Reporter** — in the most effective order.
</Note>

## Getting started: Setup order

***

For clean, modular integrations, follow this setup order:

<Frame caption="Figure 1. Enterprise Model setup order.">
  <img src="https://mintcdn.com/lerian-49cb71fc/SEOef3JqTInYAAau/images/en/d2/enterprise-model.svg?fit=max&auto=format&n=SEOef3JqTInYAAau&q=85&s=862e4912bae2a93dac0be94753ea260a" alt="Recommended setup order for the Enterprise Model, sequencing Midaz, Access Manager, and the optional Fees, CRM, and Reporter capabilities" width="869" height="2056" data-path="images/en/d2/enterprise-model.svg" />
</Frame>

### Step 1: Configure Midaz Core

Start with the [Midaz recommended workflow](/en/midaz/recommended-workflow). It covers these tasks:

* Create your Organization and Ledger(s).
* Define assets and account types.
* Set up portfolios, accounts, and segments.
* Configure Accounting Routes for validation.
* Build double-entry transaction workflows.

### Step 2: Activate Access Manager

**Access Manager** centralizes authentication and role-based access control (RBAC) for Midaz and its plugins.

* Define user roles and scopes.
* Assign permissions to API keys or users.
* Control access to operations by role.

<Tip>
  Start with the [Access Manager Setup](/en/platform/access-manager/access-manager) page.
</Tip>

### Step 3: Configure CRM

**CRM** ships inside the Midaz ledger process and manages `Holder` and `Instrument` records. Instruments link Holders to ledger accounts, and accounts can optionally belong to portfolios.

* Register customers as `Holder` objects.
* Create Instruments to link Holders to ledger accounts, or use `POST /v1/organizations/{organization_id}/holders/{id}/accounts` to open a holder-owned account in one call.
* Add metadata for compliance, segmentation, and insights.

This links each customer to the right ledger accounts.

<Tip>
  Start with the [CRM Setup](/en/midaz/crm/crm-overview) page.
</Tip>

### Step 4: Configure Fees Engine

Use the **Fees Engine** to automate pricing and monetization rules across your operations.

* Define fee packages with flat or percentage calculations.
* Attach fees to operations like transfers or withdrawals.
* Control when and how the Fees Engine calculates and charges each fee.

<Tip>
  Start with the [Fees Engine Setup](/en/midaz/fees/fees-engine-overview) page.
</Tip>

### Step 5: Design with Reporter templates

Use **Reporter** and its template engine to generate dynamic, personalized content such as:

* Transaction summaries
* Regulatory documents
* Customer notifications

Use it to standardize documents and messages with context data from Midaz and CRM.

<Tip>
  Start with the [Reporter quick start](/en/reporter/reporter-quick-start) page.
</Tip>

## Final recommendations

***

After you set up all systems:

* Review the integration points between Midaz and each capability.
* Create automated workflows that combine ledger events, customer data, and fee logic.
* Apply permission rules with Access Manager to control access at scale.

<Tip>
  Lerian capabilities are modular. Activate and expand them progressively as your architecture matures.
</Tip>