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

# Manage project assets

> Track the physical equipment behind your production data — chargers, meters, wells, kilns, vehicles — as first-class assets.

Assets represent the physical equipment that generates or measures your production data. Each asset can belong to a location, to a project directly, or both, and carries its own typed metadata through [custom fields](/account-admin/custom-fields).

Manage a project's assets in **Settings → Assets**. From there you can create assets, edit their details and custom field values, and export the asset list.

### What an asset carries

* **Name** — how the asset appears across the platform.
* **Location and project** — an asset can be parented to a location (a site or facility), attached to a project, or both.
* **Coordinates** — per-asset latitude and longitude, independent of the parent location.
* **Custom field values** — typed attributes defined by your account's asset custom fields, such as a serial number, registration status, or registry-assigned ID. See [Custom Fields](/account-admin/custom-fields).

### Attaching events to assets

Events can be linked directly to the asset that produced them. When an event type has **Requires asset** enabled, every event of that type must reference an asset — so per-equipment data can't lose its linkage during ingestion.

Data feeds attach each event to its asset by the asset's friendly ID — incoming rows must carry that ID for the event to be linked.

### Per-asset batches

Models can partition batches by asset, producing one batch per piece of equipment in the generation window. This is the natural fit for programs that report per-unit — per-charger, per-meter, per-well — and each batch surfaces the asset it belongs to.

### API access

Assets are available through the API — see [List assets](/api-reference/assets/get-all) and related endpoints. Asset custom field values are readable and writable via the same endpoints, which lets external systems keep registration state in sync.