Custom Fields — Overview

Custom fields extend DonorPoint’s standard record types with your organisation’s own data fields. They are defined in the admin application and take effect immediately — no code change, no deployment.

Custom fields collect, store, and surface data that DonorPoint doesn’t capture by default. Every entity-specific section in this documentation has a Customization sub-topic that covers what can be extended there and links back here for the full reference.

Two Kinds of Custom Field

Custom Properties — visible fields collected from donors on forms or entered by staff in the admin. They appear on edit views and can be shown on confirmation pages and in emails.

Integration Codes — hidden fields not shown to donors and not displayed in standard admin list views. They carry back-office data: GL account codes, external system identifiers, and configuration values read by scripts and reports.

Both types are accessible in scripts and available as report columns.

Where to Define Custom Fields

Custom fields are defined in different places depending on which record type they extend:

• Contacts / Organizations — Configuration → Custom Properties (select Contact or Organization type)
• Funds — on the Fund record itself
• Campaigns (forms) — on the Campaign’s Custom Fields tab
• Items — on the Item’s Custom Fields tab
• Employee Relationships — on the Organization that employs them

See Where Custom Fields Live for the complete data flow map.

Reuse

A custom field definition is reusable — the same field can be added to multiple campaigns or multiple items. Changing the definition (prompt, type, options) affects all places it is used. DonorPoint shows a usage count warning when you edit a field that is in use in multiple places.