For: Operators using Monta Hub.

Where custom fields are available

Custom fields are supported on five record types in Hub Beta:

• EVSEs — on the EVSE detail page
• Charges — on the charge (session) detail page
• Locations — on the Location detail page
• Teams — on the team detail page
• Team members — on the team member settings page

On each record, the Custom fields card appears alongside the other record details.

How custom fields work

• Values are stored as key/value pairs. Both the key and the value are free-form text.
• Keys must be unique within a single record. You can use the same key on different records.
• Custom fields can be set in Hub Beta or through the API. Changes made in one place are visible in the other.
• There is no central settings page for custom fields. You add and edit them directly on each record.

How do I add a custom field?

1. Open the detail page for the record (charge point, charge, site, team, or team member).
2. Locate the Custom fields card.
3. Select Add field.
4. Enter a key and a value.
5. Select Save.

The new field appears in the Custom fields card.

How do I edit a custom field?

1. Open the record's detail page.
2. In the Custom fields card, select Edit.
3. Update any keys or values, or select the trash icon to remove a row.
4. To add another field while editing, select Add field.
5. Select Save to apply changes, or Cancel to discard them.

Note: if you enter the same key on more than one row, you see Keys must be unique. Save is disabled until you fix the duplicate.

How do I remove a custom field?

1. Select Edit on the Custom fields card.
2. Select the trash icon next to the row you want to remove.
3. Select Save.

Values and formatting

• Values are stored as text. Numbers and true/false values are kept as text and shown back as you entered them.
• Long values wrap inside the Custom fields card.
• Structured values written through the Partner API (for example, JavaScript Object Notation (JSON) objects) are shown read-only as formatted code in the card.

Custom fields and the Partner API

Custom fields are the same data exposed by the Partner API custom-fields payload on each supported entity. Anything you set in Hub is available through the API, and anything you write through the API appears in Hub.

If your integration is the source of truth for these values, edit them through the API and treat Hub as a viewer. If operators manage these values themselves, use the Hub.

FAQs

Can I define a list of allowed keys for my operator?

No. Custom fields are added ad-hoc on each record. There is no central list of keys, and no fixed schema.

Do custom fields support typed values such as numbers, dates, or dropdowns?

No. All values are stored as text. If you need a specific format, validate it in your own integration before writing the value.

Can I bulk-edit custom fields across many records?

Not from Hub. Use the Partner API to update custom fields in bulk.