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

# Organization

> A company or firm in the directory that people can belong to.

An **organization** is a company or firm the platform knows about — a brokerage, a
law firm, a vendor. Organizations live in the **directory** alongside
[people](/entities/person), and they're what people can belong to: a broker
belongs to a brokerage, an attorney to a law firm.

<Frame caption="An organization in the app — the Law Firm type adds a Law Firm Info card, and the People field lists its linked people.">
  <img src="https://mintcdn.com/ai-insurance-fmv1/nmTQjI4bY9Oj6vrb/assets/entities/organization.png?fit=max&auto=format&n=nmTQjI4bY9Oj6vrb&q=85&s=3ebcc0011ceb19ab4828326324c7bcb1" alt="Organization detail page in the Directory showing type Law Firm, name, email, a People field listing a linked person, and a Law Firm Info card with a Managing Partner field." width="1853" height="904" data-path="assets/entities/organization.png" />
</Frame>

<Note>
  Working in the app? See the [Directory and contacts feature reference](/app/features/directory) for people, organizations, and the Contacts tab.
</Note>

## How its data works

An organization is a set of **fields configured per company**. Every organization
has a name, and every organization has a **type**.

**Types are configured per company, and you can create any number of them.** Out of
the box the directory ships with organization types like *law firm* and
*brokerage*, but your company defines its own list. As with people, an organization
has a **baseline** set of fields and the type **adds type-specific fields on top** —
a *law firm* surfaces law-firm details, a *brokerage* brokerage details. Because an
organization always has a type, it always shows that type's specific fields.

<Note>
  An organization's type is **required** — every organization must have one, in the
  app and in the data model alike. People are subtler: the app also makes you pick a
  type (with *Other* as the catch-all), but the data model leaves it **optional** — a
  typeless person can exist via the API. See [Person](/entities/person).
</Note>

## What it connects to

| Connects to                | How                                                                                                                                          |
| -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- |
| [People](/entities/person) | Many people can belong to one organization. The organization sees the list of its people; each person points back at their one organization. |

## Files, Notes & Contacts

In the app, an organization has a **Notes** tab only (no Files or Contacts tabs).
The API is broader than the in-app tabs — see the
[overview](/entities/overview#what-every-entity-has-in-common).

<Accordion title="Technical reference">
  **Where it lives.** Organizations are top-level entities surfaced through the
  **Directory** UI at `/directory/organization`. Through the API they're the
  `organization` entity on the unified CRUD surface — see the [Entities API
  overview](/api-reference/entities/overview).

  **Framework-required fields.**

  | Field    | Notes                                                                                                                |
  | -------- | -------------------------------------------------------------------------------------------------------------------- |
  | `name`   | Display name.                                                                                                        |
  | `type`   | Option Set ("Organization Type"). **Required.**                                                                      |
  | `people` | List join to the people in this organization (reverse-read; the link is written on each [Person](/entities/person)). |

  **Types and type-driven fields.** Organization types are values in the per-company
  "Organization Type" option set (part of the company's configuration).
  Type-specific fields are implemented as embedded objects revealed by display
  conditions on the type (e.g. law-firm details shown when `type == "lawFirm"`).

  **Type permissions.** Person and Organization reuse the
  `company.fmv1_custom_object:*` permission family.
</Accordion>