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

# Investors

> Investors — types, management model, and lifecycle states.

An **investor** represents one end user's investing relationship. It is the root object that connects to wallets, orders, positions, documents, and funding sources. Every investor belongs to your tenant and carries a prefixed `inv_` id. You create one with `POST /v1/investors`.

## Investor types

The `account_type` field sets the kind of investor:

| `account_type` | Use case                                 |
| -------------- | ---------------------------------------- |
| `individual`   | Personal investor — the most common type |
| `joint`        | Shared by two or more individuals        |
| `corporate`    | Business or corporate investor           |

## Management type

`management_type` selects how the investor is run:

| Value           | Description                                           | Wealth product                        |
| --------------- | ----------------------------------------------------- | ------------------------------------- |
| `self_directed` | The user decides what to buy and sell (default)       | Not required                          |
| `advised`       | Managed portfolios, financial planning, robo-advisory | Requires the [Wealth](/wealth) add-on |

A self-directed personal investor is `account_type: "individual"` with `management_type: "self_directed"`. Setting `management_type: "advised"` unlocks the managed-investing surface for tenants that have the Wealth product enabled.

## Lifecycle

An investor moves through compliance before it can trade. The external status vocabulary:

| Status               | Meaning                                          |
| -------------------- | ------------------------------------------------ |
| `onboarding`         | Investor created, verification not yet complete  |
| `under_review`       | Compliance checks running or in manual review    |
| `awaiting_documents` | Additional documents requested from the user     |
| `active`             | Verified and able to fund and trade              |
| `suspended`          | Temporarily blocked from activity                |
| `closed`             | Investor closed                                  |
| `declined`           | Verification failed; the investor cannot proceed |
| `setup_failed`       | Provisioning error during setup                  |

In sandbox, investors reach `active` immediately after creation. In production, the investor advances as compliance completes.

<Frame>
  <img src="https://mintcdn.com/bluumfinance/L5Dm3BN-WAZqlyQf/images/diagrams/account-lifecycle.svg?fit=max&auto=format&n=L5Dm3BN-WAZqlyQf&q=85&s=a7cb956d512c58863cc0c12caf2d0a45" alt="Investor lifecycle" width="1200" height="440" data-path="images/diagrams/account-lifecycle.svg" />
</Frame>

## Related objects

Once an investor is active it anchors the rest of the platform:

<CardGroup cols={2}>
  <Card title="Wallets" icon="wallet" href="/concepts/wallets">
    Cash balances the investor funds and trades from.
  </Card>

  <Card title="Compliance & KYC" icon="shield-check" href="/concepts/compliance-kyc">
    Identity verification that gates activation.
  </Card>

  <Card title="Trading" icon="chart-line" href="/concepts/trading">
    Orders placed against the investor.
  </Card>

  <Card title="Positions" icon="layer-group" href="/concepts/positions">
    Holdings created as orders fill.
  </Card>
</CardGroup>

<Note>
  For the step-by-step create-investor request and body, see the journey guide:
  [Create an investor](/get-started/journey/create-investor). Full request and response
  schemas live in the [API reference](/api-reference/introduction).
</Note>