Skip to main content
Instead of managing pathway- or customer-specific details in external resources, teams can define custom fields to store information such as verifiers, serial numbers, registration statuses, or other operational and MRV-related attributes. This reduces fragmentation, prevents data from falling out of sync, and minimizes reporting errors and validation delays. Custom Fields are flexible and pathway-agnostic, ensuring Mangrove can support multiple project types without complicating the default user experience. Fields are only added where needed and can be accessed by the appropriate users, stakeholders, and systems. Custom Fields are available on two record types:
  • Projects — project-level attributes such as verifier, counterparty, or crediting period details.
  • Assets — per-equipment attributes such as serial number, registration status, registry-assigned ID, or nameplate capacity. See Manage assets.

​
How it works

Custom Fields are managed in two distinct areas of the Mangrove platform: definitions live in Account Admin; values are set on the individual record.

​
Account Admin: Defining Custom Fields

Before a custom field can be used, it must first be defined at the account level. This is done in Account Admin → Custom Fields, which has a tab for each record type (Projects, Assets). Here, administrators create a library of custom fields available across the account, ensuring consistency and standardization of data fields across your organization. Each definition specifies a Label (the field’s display name) and a Type:
  • Text, Number, Boolean, Date, URL — typed values validated on entry.
  • Select (enum) — a closed list of allowed values, useful for statuses and other controlled vocabularies.

​
Setting values

  • Projects — add a defined field to a project and set its value in the project’s Settings → Custom Fields section, selecting only the fields relevant to that project.
  • Assets — asset custom field values are set on the asset itself, in the project’s Settings → Assets page, either when creating the asset or by editing it later.

​
Permissions and Visibility

  • Admins: Can define, add, remove, and edit custom fields and their values.
  • Members: Can view the values of custom fields which are set as visible in the project overview.
Admins can also control the visibility of project custom fields, choosing whether they appear on the project’s main Overview page. This allows for information to be tracked without being exposed to all users with read-only access to a project.

​
API Access

For teams that need to integrate Mangrove with other systems, custom field data is accessible via the Mangrove API:
  • Definitions — full CRUD via the Custom Field Definitions endpoints.
  • Project values — included as key-value pairs on the project endpoints.
  • Asset values — readable and writable as custom_field_values on the asset endpoints, and filterable with filter[custom_field_values][{key}] when listing assets.