Guides
Work the Donors console#
The **Donors** tab lists the people who have actually given — not every Contact in your org — and opens each one as a workspace tab where their whole giving relationship, and the things you do about it, sit on one page.
Find it#
Open the Pledgivo app from the App Launcher and pick the Donors tab. It is an ordinary Lightning tab, so it works in any Lightning app you add it to, and the browser Back button behaves the way it does everywhere else.
It looks and behaves like the Fundraisers console on purpose — same brand bar, same pinned home tab, same workspace strip — because they are two views of one job, not two apps.
Who counts as a donor#
The console lists a person if either of these is true:
- they have at least one won donation, or
- they have an Active recurring gift.
Nothing else puts someone on the list. A Contact you imported, a volunteer, a newsletter subscriber or a lapsed prospect will not appear until money — or a live commitment to give money — exists.
One definition, four places
The same test drives the list, the chip counts, the search and the paging, so the number on a chip always matches the rows you get when you click it. It also means a gift that is refunded or reversed does not remove someone from the console — they did give, and the record of it is what the console is for.
Person Account orgs are handled automatically. If your org uses Person Accounts, the console lists Person Accounts instead of Contacts, with the same columns and the same actions. The only visible difference is the Household column, which is dropped — a Person Account is its own household, so the column would only ever repeat the name.
The list#
| Column | What it holds |
|---|---|
| Donor | Name, with the donor's initials as an avatar |
| Household | Their household account — hidden in Person Account orgs |
| Lifetime | Total given, across every campaign |
| Gifts | How many gifts they have made |
| Last gift | When they last gave, in plain words ("12 days ago") |
| Recurring | A marker when they have an Active recurring commitment |
Donor, Lifetime, Gifts and Last gift are sortable — click a heading once to sort, again to reverse it.
Search#
The search box matches a donor's name and email. It searches the whole donor base on the server, not just the page you are looking at, so a name that is on page nine still comes back on the first keystroke.
Segments#
Five chips sit above the table, each carrying its own count:
- All donors
- Recurring — has an Active recurring gift
- Last 30 days — gave within the last 30 days
- Repeat — has given more than once
- Lapsed — has given, but not in the last 12 months
A segment narrows the list and the search, so you can look for a name inside Lapsed without first finding them among everyone.
Paging#
The pager under the table shows what you are looking at and lets you switch between 25, 50 and 100 rows.
Everything happens on the server
Searching, sorting, segmenting and paging are all done by the database, and only one page of rows is ever sent to the browser. That is what lets the console stay fast in an org with hundreds of thousands of donors — unlike the Fundraisers console, which can afford to load every campaign at once because there are only ever tens of them.
Open a donor#
Click a row. The donor opens as a tab in the strip along the top, and the list stays where it was — the All donors tab on the left is pinned and never closes.
Every open tab keeps its own state, so switching away and back does not reload the record or lose the section you had open. Close one with the × on the tab, or use Close all to get back to a clean list.
Share a link to one donor#
While a donor is open, the page URL carries their Id:
Send that link to a colleague and the console opens with that donor already selected. It is also
what a bookmark saves. The c__ in front of id is required — Lightning silently drops any query
parameter on a tab URL without a namespace prefix — and links copied from the address bar always
carry it.
Open tabs live in the page, not on your user record, so a browser refresh returns you to the list with the linked donor open and the rest closed.
Inside a donor#
Details is pinned and always shown: contact details, household, location, when they became a donor, and their Stripe customer reference. Beside it sits the giving summary — lifetime, gifts, average gift, largest gift, last gift, active recurring and committed per year.
Everything else is a section you add when you want it, from the strip under the header:
| Section | What it lists |
|---|---|
| Donations | Every gift, newest first, with its stage and payment status |
| Recurring | Their recurring commitments and where each one stands |
| Designations | Which funds their giving has gone to |
| Tickets | Event tickets they hold, and whether they attended |
| Guest requests | Anything they have asked for through the donor portal |
Each list is fetched the first time you open its section rather than up front, so opening a donor costs one read and not six. Long lists show the first page inline with a View all link that opens a paged sheet over the record.
Every row starts with an open-in-new-tab action that takes you to that donation, recurring gift or ticket on its own standard Salesforce record page, in a new browser tab, so the donor you were working stays exactly as you left it.
What you can do from here#
Send a donor portal access code#
Send portal access code opens a panel showing the donor's email, the portal address, and how long a code lasts. From there:
- Get a code issues one and shows it on screen, so you can read it out to a donor on the phone. A Copy button puts it on your clipboard.
- Email the code sends it to the donor's own email address.
If the donor has no email address, or something else stops a code being issued, the panel says so before you press anything rather than failing afterwards.
See Publish the donor portal for how the portal itself is set up.
Print or email a receipt#
Every gift that reached the bank carries Print and Email next to it in the Donations list — including a refunded one, because a donor who asks for that document is entitled to it, and the letter says plainly that the gift is no longer deductible. A gift that never settled has nothing to receipt, so neither link appears.
- Print opens the receipt in its own window and sends it to your printer or a PDF, without the console chrome around it. It is built from the same shared letter the Opportunity record page prints, so the two surfaces can never disagree about a tax document.
- Email shows you the gift, the receipt number, the address it will go to and the template it will use, and only sends once you confirm. If the donor has no email address, or the org has no receipt template configured, the panel says so instead of offering a button that would fail.
What the letter actually claims about deductibility — the full amount, the net of goods received, or nothing at all — is decided by the gift itself, not by where you printed it from. See What a receipt claims is deductible for how that is worked out.
Refund a gift#
Any refundable gift in the Donations list carries a Refund link. It asks for the amount and a reason, and shows what has already been refunded against that gift so you cannot accidentally send a second one. Gifts that cannot be refunded do not offer the link at all.
The full procedure, including what happens on the Stripe side, is in Process a refund.
Answer a guest request#
Requests the donor raised from the portal appear in Guest requests, each with its type, status and when it arrived. On one that is still open you can:
- Mark completed — with a note saying what you did, and
- Decline — with a reason the donor can be told.
Where a request is about a specific gift, Open the gift takes you straight to it.
If the console will not open#
If your org is licensed per user, the Donors tab needs a seat like every other part of the app. A donor with no seat sees a licence notice in place of the console rather than a half-working page. An error reading the licence, on the other hand, leaves the console open — a licence check that cannot answer should never lock an admin out of their own data.