> ## 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.

# Organizations

> Define the top-level Organization that owns your Midaz Ledgers — represent banks, fintechs, and parent-child hierarchies for subsidiaries.

An **Organization** is the top-level entity in Midaz. It represents a financial institution, such as a bank or fintech. An Organization owns and governs the financial data of that institution. It is the primary container for all financial operations.

A bank or financial group registers as an Organization in Midaz. The Organization gives its operations a structured environment.

<Note>
  **SaaS and multi-tenant environments** — Midaz scopes every Organization to your tenant automatically. When you list Organizations, you see only the ones in your account. The platform enforces [tenant isolation](/en/multi-tenancy) for you. You do not filter by tenant or add a tenant identifier to your requests.
</Note>

### Sub-Organizations

Organizations support **parent-child hierarchies**. A bank uses them to represent subsidiaries, regional branches, or separate business units in one framework.

This structure fits financial groups that run several legal entities. Each entity owns its own [Ledgers](/en/midaz/ledgers) and stays operationally independent. The parent-child link records how the entities relate.

### Organization structure

* **Organization > Ledgers:** Every Organization owns one or more Ledgers. Each Ledger holds its financial records, such as accounts and transactions, and belongs to one Organization.

### Key characteristics

* Organizations are the highest level in the hierarchy.
* Each Organization governs its own Ledgers and sets their operational boundaries.

## Flexible hierarchies

***

Midaz supports organizational hierarchies for complex structures.

If your company has several locations or divisions, you can create **child organizations** for specific branches, offices, or subdivisions. Each child organization connects to a **parent organization**.

Each Organization keeps its own data. Records in one Organization do not cross into another.

<Note>
  If a single group manages several Organizations, use this hierarchy to set clear boundaries between them.
</Note>

### Example

**Company XPTO** is a Brazilian company with branches in São Paulo and New York. Its structure is as follows:

* **Parent Organization**: XPTO Ltda
* **Child Organizations**:
  * XPTO New York
  * XPTO São Paulo

With this structure, the company can:

* Set a distinct role for each branch.
* Track each branch separately.
* Adapt workflows to each branch.

## Benefits of organizational structuring

***

* **Scalability**: Add or change branches as the business grows.
* **Efficiency**: Manage all levels from one hierarchy.
* **Personalization**: Configure each branch on its own.

Midaz adapts to your company's structure, whether it is simple or complex.

<Tip>
  Need help with your Midaz setup? Our consulting service can help you design the structure for your organization, from scratch or from an existing setup.

  [Contact us](https://lerian.studio/contact) to learn more.
</Tip>

## Managing Organizations

***

You manage your Organization through the API or Lerian Console.

### Via API

* [Create an Organization](/en/reference/midaz/create-an-organization) — Register a new Organization.
* [List Organizations](/en/reference/midaz/list-organizations) — View all Organizations in your workspace.
* [Retrieve an Organization](/en/reference/midaz/retrieve-an-organization) — Get details of a specific Organization.
* [Update an Organization](/en/reference/midaz/update-an-organization) — Edit an existing Organization.
* [Delete an Organization](/en/reference/midaz/delete-an-organization) — Mark an Organization as deleted.

<Note>
  When you delete an Organization, Midaz does not remove it from the system.

  Midaz sets a `deletedAt` timestamp instead. The Organization is then excluded from every read and can no longer be used. Its `status.code` is left unchanged, which preserves historical data for audit trails.
</Note>

### Via Lerian Console

You view, create, edit, and delete Organizations from the **Organizations** page in the Midaz Module of Lerian Console.

[**Learn more in the Managing Organizations guide.**](/en/midaz/console/managing-organizations)

<Tip>
  When you create your **first Organization** in the Console, you do it as part of the onboarding flow. To learn more, see the [Midaz Module onboarding](/en/midaz/console/midaz-console-onboarding) guide.
</Tip>