This is a guide to the principal CRM records and their relationships, rather than a complete API schema. See the API reference for integration details. UI fields and availability depend on configuration and permissions.
Relationships
Contact
An individual person. The record includes identity, contact details, a structured address, classifications, contact types, lifecycle flags and connections to other records. It can also carry configured custom fields and communications consent. See Contact fields.
Consent storage
Consent is stored by purpose and channel: consent[purposeName][channelKey]. A channel record has a state (ok, no or unknown) and a history of changes. History entries record timestamp, changed-by identity, channel, old/new state and an optional note. Channel keys are lowercased with spaces removed.
A contact can therefore permit email for one purpose while refusing it for another. Archiving a configured purpose makes its existing preferences read-only; it does not erase them. See Relationships settings.
Organisation
An institutional body with a name, configured types, registered address, repeatable registration numbers and connected contacts. Custom fields and tags extend it. See Organisation fields.
Resource
A tracked item with description, available quantity, returnable flag, types and connected contacts. Check-out/return or send actions track distribution. A resource is distinct from a restricted fund, tribute fund or programme. See Resource fields.
Touchpoint
An interaction with a contact, organisation or resource. It records type, direction, time and notes, and may link to a fundraising activity. It can carry file attachments. See Touchpoint fields.
Payment
A financial record with amount, currency, reporting amount, payer, dates and status: Paid, Pledged or Invoiced. Coding can include payment method, bank account, team, activity, fundraising page, restricted-fund allocations and a tribute fund. Tax-relief exclusion is separate from proof of eligibility. Payments can carry attachments. See Payment fields.
Recurring payment
An arrangement for scheduled income. It records an amount/currency, frequency and collection-day rule, payer, coding defaults and collection-system information. Collections represent expected instalments; settlements can be matched to them. Creating an arrangement is not proof that money has arrived. See Recurring payments and Reconciliation.
Fundraising activity
A named appeal, event, third-party fundraiser or acquisition activity. It can group related payments, touchpoints, tasks, files and saved audience assignments, and supply payment defaults. See Fundraising activity fields.
Restricted fund
A spending allocation with description, notes, restricted/designated/unknown classification and optional programme link. Payments can split their value across funds. See Restricted funds.
Tribute fund
A memorial fund with name, optional date of death and contact links for the deceased person and next of kin. Payments link to it separately from spending restrictions. See Tribute funds.
Fundraising page
An individual or team page associated with an owner and activity, carrying platform, target, status and an optional external URL. See Fundraising pages.
File Attachments
File attachment
A file and its metadata linked to a supported record. User-facing metadata includes filename, content type, size and upload information; the attachment panel supports downloading and removal where permitted.
The current UI offers attachments on touchpoints, payments, organisations and fundraising activities. Case interactions provide an existing-document reference field, not an upload panel. Task detail/forms do not offer file upload. An attachment’s existence does not grant access to its linked record.