Domain model overview
The DonorIntel domain model is how the product represents your nonprofit in software: what exists, what belongs to whom, and which relationships must stay consistent as gifts, pledges, and donor profiles evolve. This page gives architects, admins, and integrators a map before they dive into API references or data-dictionary entries.
If you are wiring integrations or designing custom fields, start here so naming in the UI lines up with what you will see in logs and exports.
Overview
Section titled “Overview”Every production record ultimately lives inside a tenant—your organization’s boundary for data isolation. Users are people authenticated through WorkOS; their abilities inside a tenant come from roles, optional permission overrides, and membership conveyed through invitations.
Fundraising entities (donors, transactions, campaigns, and related objects) attach to that tenant spine, while custom fields and brand kits layer configuration without breaking core integrity. Activity logs capture auditable events across those domains so you can reconstruct change over time without guessing from snapshots.