Tenants and organizations
In DonorIntel, a tenant is your nonprofit’s dedicated space: donor records, configuration, branding, and audit history that belong to one legal or operational entity in the product. This page explains how tenancy affects isolation, admin workflows, and what “multi-tenant SaaS” means for your staff day to day.
Finance leaders, executive directors, and IT partners should read this before discussing separate instances for chapters, foundations, or fiscal sponsors.
Overview
Section titled “Overview”Tenants are the hard boundary for data visibility—users do not browse across tenants unless your business model explicitly spans multiple instances with integration. Within a tenant, tenant settings control operational defaults, while brand kits carry visual identity for communications and surfaces that should feel unmistakably yours.
Scaling organizations sometimes map affiliates to separate tenants or to shared tenants with strict RBAC; the right pattern depends on reporting, autonomy, and compliance. Later guides cover settings and branding in detail; this concept page anchors the vocabulary you will see everywhere else in the docs.