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

# Organizations

> Top-level entities that contain members and FBO accounts

An **organization** is the top-level entity in Beach Depositories. It represents a business or institution that uses vault storage services. All FBO accounts, members, and inventory are scoped to an organization.

## Structure

```
Organization
├── Members (admin or member role)
├── FBO Accounts
│   ├── Inventory Items
│   ├── Addresses
│   └── Portal Access
└── Configuration
    ├── Max Insured Value
    └── Risk Score
```

## Properties

| Property              | Description                                                                               |
| --------------------- | ----------------------------------------------------------------------------------------- |
| **Name**              | The name of the organization                                                              |
| **Max Insured Value** | The maximum total insured value for all inventory held under this organization (in cents) |
| **Risk Score**        | An internal risk assessment score assigned by Beach Depositories staff                    |

## Member roles

Organizations have members with one of two roles:

<CardGroup cols={2}>
  <Card title="Admin" icon="shield">
    Can manage FBO accounts, initiate transfers, invite new members, and update the organization name.
  </Card>

  <Card title="Member" icon="user">
    Can view organization inventory, shipments, and FBO account information.
  </Card>
</CardGroup>

<Warning>
  Only Beach Depositories staff can modify an organization's **max insured value** and **risk score**. Organization admins can update the organization name.
</Warning>

## Audit trail

Every change to an organization is recorded in the organization history, including:

* Organization creation
* Name changes
* Max insured value changes
* Risk score changes
* Soft deletion

Each history entry tracks:

* **Who** made the change (staff member or organization member)
* **When** the change was made
* **What** changed (previous and new values)
* **Why** (optional reason)

## Limits

* Each FBO account belongs to exactly one organization
* Members can belong to multiple organizations
* There is no hard limit on the number of FBO accounts per organization