Skip to main content
Instead of managing pathway- or customer-specific details in external resources, teams can define custom fields on projects to store information such as verifiers, onsite equipment, 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.

​
How it works

Custom Fields are managed in two distinct areas of the Mangrove platform: Account Admin and Project Settings.

​
Account Admin: Defining Custom Fields

Before a custom field can be used in a project, it must first be defined at the account level. This is done in the Account Admin section under Project Custom Fields. Here, administrators can create a library of custom fields that will be available for use across all projects in the account. This ensures consistency and standardization of data fields across your organization’s projects.

​
Project Settings: Adding and Managing Custom Fields

Once a custom field has been defined in Account Admin, it can be added to a specific project and have its value set. This is done within the Settings tab of a project, under the Custom Fields section. This allows project managers to tailor the data they track for each project, selecting only the custom fields that are relevant.

​
Configuring and Using Custom Fields

Users with Admin privileges have the ability to configure and manage custom fields. To create and use a new custom field:
  1. Define the Custom Field: In Account Admin → Project Custom Fields, create a new custom field definition by specifying a Label (the name of the field) and its Type (e.g., text, number, date, URL).
  2. Add the Field to a Project: Navigate to the desired project and go to the Settings → Custom Fields section. Click + Add Field to select from the list of predefined custom fields.
  3. Set the Value: Once a field is added to a project, you can input its value. This value can be updated at any time by users with the appropriate permissions.

​
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 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. The GET /project and GET /projects endpoints will include any custom field key-value pairs associated with a project, allowing for seamless data synchronization and automation.