Skip to main content

Foundation module

Fundraising suite — campaigns, donations, donor CRM, recurring pledges, bulletins, tax receipts, and Stripe webhooks.

Optional module Enable in Settings → Modules

Foundation is GreekManage's fundraising module — campaigns, public donate pages, a donor CRM, recurring pledges, donor bulletins, and IRS-style tax receipts. It is designed for the tax-exempt foundation arm that often sits alongside a national org and collects gifts to a separate bank account.

Foundation uses Stripe only as its payment processor. This is a deliberate split from dues billing — dues supports four payment processors so chapters can keep their existing vendor, but Foundation is Stripe-exclusive, with its own connected account and its own webhook configuration. The two never share processor credentials.

Audience​

  • Members of the org can donate from a pre-filled internal flow once Foundation is enabled.
  • Public donors (alumni, parents, friends) can donate from public campaign URLs without an account.
  • Foundation Admins are top-level operators of the foundation — they configure settings, payment processor, bulletins, and have full read/write across donors and donations.
  • Foundation Editors can create and edit campaigns, donations, donors, and bulletins but cannot change settings or payment-processor configuration.

The Foundation Admin / Editor split is a separate role assignment from the national org admin role. A national admin is not automatically a Foundation Admin.

What gets enabled​

When Foundation is licensed:

  • A Foundation sidebar group appears for users with Foundation roles.
  • Campaigns get a public donate URL that anyone can hit without signing in.
  • Members of the org see a dashboard and an internal donate flow.
  • Donors are de-duplicated and linked to member accounts automatically when emails match.
  • Recurring pledges run as Stripe Subscriptions; failed-payment retries are handled by Stripe.
  • Per-donation receipts go out automatically; an annual statement runs in mid-January.
  • A Stripe webhook endpoint with signature verification and idempotency processes payment events.
  • An expired-campaign daily task closes campaigns past their close date.

Foundation sidebar group with Campaigns, Donations, Donors, Reports, and Bulletins. Foundation sidebar group with Campaigns, Donations, Donors, Reports, and Bulletins.

Common workflows​

For members​

For public donors​

  • Open a public campaign URL and donate by card → no account needed; the URL is shared via email, social, QR code, or website embed.

For Foundation Admins​

For Foundation Admins and Editors​

What's NOT in this module​

  • No donor-facing portal. The donor self-service portal (history, manage pledges, re-download receipts) is scaffolded in the backend but has no UI in v0.62.1 — it is on the documentation backlog.
  • No dedicated recurring-pledges admin page. Pledges live inside the donations and donor surfaces; a stand-alone management page is on the backlog.
  • No Stripe webhook event log UI. Webhook events are persisted and idempotency is enforced server-side, but there is no admin page to inspect the event ledger in v0.62.1 — also on the backlog.
  • Not the same as Operations dues. Foundation is Stripe-only and uses a separate Stripe Connect account from dues; the two payment paths never share credentials or banking.
  • Foundation bulletins use a plain text editor, not the rich-text editor used for org bulletins in Community.

Where to go deeper​

Last verified against v0.62.1 (2026-05-11).