Reference

Release notes#

Every package version, newest first. A version marked pre-release is a build we install into our own test orgs; it has not been promoted, and it is not the one an AppExchange listing would install.

Upgrading from a build older than 1.0.0-1

Versions built before September 2026 used a throwaway namespace and cannot be upgraded from. Uninstall that package first, then install the current version. See Installation.

1.2.4-1 — 7 October 2026 · released#

A code-quality patch from our latest AppExchange security scan. Nothing you or your donors see changes.

The NPSP skipped-sync log entry names the first error, then a count. When a gift's NPSP allocation sync is skipped, its ERROR in Diagnostic Logs now reports the first reason followed by how many more there were, for example "(+2 more)". The remedy it names is unchanged.
The Contact and Recurring Donation triggers listen only for the events they handle. Saving, deleting and restoring contacts and recurring donations works as before, and the package still checks that the person doing it holds the matching permission.
Nothing to do after upgrading. No new fields, permissions or settings.
Everything in 1.2.3-1 below is included.

1.2.3-1 — 6 October 2026 · released#

A reliability and security-hardening patch. Nothing your donors see changes.

A gift that skips the NPSP allocation sync now says so. If the user your scheduled jobs run as holds neither the Fundraising Admin nor the Fundraising User permission set, a gift is still recorded, but its NPSP allocations are not created. Before this version that happened without a trace. Now each skipped gift or recurring installment leaves an ERROR in Diagnostic Logs against its Opportunity, naming the fix: re-own the jobs from Fundraising Settings → Health Check → Scheduled Jobs → Fix. See NPSP integration.
Saving ticket types creates their price-book entries in one step. Behaviour is unchanged for you; the save does less work per tier.
The Payment Accounts setup guide runs under the viewing admin's record sharing. It only reads setup information, so what it shows does not change.
After upgrading: if you use NPSP, open Health Check and confirm Scheduled Jobs is green. Otherwise there are no new fields, permissions or settings.
Everything in 1.2.2-1 below is included.

1.2.2-1 — 3 October 2026 · released#

The subscription links in the app now open the publisher's checkout.

Complete checkout and Manage subscription go to the checkout page. The trial banner on the staff consoles, the licence notice, and the Manage subscription button on the Settings console's Licence & Seats panel now open the checkout at billing.cloudalgo.com, pre-filled for your organisation, instead of the pricing page.
Nothing to do after upgrading. No new fields, permissions or settings.
Everything in 1.2.1-1 below is included.

1.2.1-1 — 1 October 2026 · released#

A security-hardening patch from our latest AppExchange security scan. Nothing you or your donors see changes.

Staff saves can only run under the staff member's own permissions. Saving a page design, a fundraiser, a post or a check-in already ran under the person's own object and field permissions. This version removes the unused setting that could have switched that check off for those saves.
The donor portal rejects a damaged or tampered sign-in session. If what the browser has stored doesn't look like a session the portal issued, it is discarded and the donor sees the sign-in form again, rather than a failed page.
Nothing to do after upgrading. No new fields, permissions or settings.
Everything in 1.2.0-7 below is included.

1.2.0-7 — 30 September 2026 · released#

A trial countdown on the staff consoles, sized for the 5-day trial. While your organisation is on a free trial, the Donation Monitor, Fundraisers, Donors, Diagnostic Logs and Settings tabs show a banner with the days left and a Complete checkout button that opens the subscription page in a new tab. The banner turns gold for the last two days and reads Trial ends today on the final day. It never shows on a paid licence, and it does not appear on donor-facing pages.
Nothing to do after upgrading. The trial length itself (5 days) is set on the licence, not in the app.
Replaces 1.2.0-6, which was built for a 30-day trial. Everything in 1.2.0-5 below is included.

1.2.0-6 — 29 September 2026 · pre-release (superseded by 1.2.0-7)#

Built for a 30-day trial, so its banner counts against 30 days and turns gold at 7. Do not install it; use 1.2.0-7.

A trial countdown on the staff consoles. While your organisation is on a free trial, the Donation Monitor, Fundraisers, Donors, Diagnostic Logs and Settings tabs show a banner with the days left and a Complete checkout button that opens the subscription page in a new tab. The banner turns gold for the last seven days. It never shows on a paid licence, and it does not appear on donor-facing pages.
Nothing to do after upgrading. The trial length itself (30 days) is set on the licence, not in the app.
Everything in 1.2.0-5 below is included.

1.2.0-5 — 29 September 2026 · pre-release#

No change to how the app behaves. This build simplifies some of the package's more tangled code — donation, recurring-gift, payment-setup and Settings logic — and removes copy-pasted blocks, so the code is easier to review for the AppExchange security review. The screens, settings and data are the same, and each affected feature was re-checked in a browser.
Everything in 1.2.0-4 below is included. Nothing extra to do after upgrading.

1.2.0-4 — 28 September 2026 · pre-release#

No change to how the app behaves. This build tidies the package's code for the AppExchange security review: every class and method is documented, the bundled framework code follows the same formatting as the rest of the package, and unused code is removed. Code Analyzer findings fall from about 19,900 to 1,308.
Everything in 1.2.0-3 below is included. Nothing extra to do after upgrading.

1.2.0-3 — 28 September 2026 · pre-release#

A branded page for broken links. A mistyped campaign link or an old bookmark used to land on the site's one-line "Invalid Page" message, with no way back in. The new Page Not Found component shows your site's header and design, and links the donor to your open fundraisers and the donor portal. After upgrading: place it on your site's Error page once in Experience Builder, then publish. Salesforce does not package site pages, so the upgrade can't do this for you. See Replace the site's "Invalid Page" message.
Clearer pages when something can't be shown. The receipt, ticket, thank-you and donor portal pages, and a fundraiser page whose link is out of date, now fill the screen with a clear message and a way forward, in your site's own colours and fonts, instead of a small card.
Page designs open in a full-size editor. Editing a page design in Settings now opens the same large step-by-step window as creating a fundraiser, in place of the side drawer.
Everything in 1.2.0-2 below is included.

1.2.0-2 — 28 September 2026 · pre-release#

Donor portal sign-in works in Person Account orgs. Every person account carries a hidden contact with the same email address, and the portal used to find that contact instead of the account. A code sent from the Donors console was rejected, and a code the donor requested opened an empty dashboard. The portal now signs the donor in on their person account, so both kinds of code open the donor's own gifts. Standard Contact orgs are unaffected.
Everything in 1.2.0-1 below is included. Nothing extra to do after upgrading.

1.2.0-1 — 28 September 2026 · pre-release#

Hero images never leave a hole. When a campaign's hero image or an event page's banner cannot load — a host your org does not trust, or a link that has gone dead — the page now shows an illustration packaged for its theme (Harbor, Sunrise, Rosewater, Sanctuary, Marigold or Grove) instead of empty space. Settings → Get Started names every outside image host your published campaigns and active designs use that is not yet a CSP trusted site. See Write a campaign story.
Licence panel. Settings now shows your seat count, expiry date and a link to the subscription portal.
Changing org-wide settings needs the new Manage Fundraising Settings permission. The Fundraising Admin permission set already includes it. A staff member on Fundraising User can still open the Settings console but can no longer save org-wide settings — assign them Fundraising Admin if they should.
Staff edits respect record sharing. Saving a fundraiser, campaign post, story, question, FAQ, page design, payment account or event check-in now checks that the person saving can edit that record and its fields. Someone who could previously change a record they were not shared on will now see an error instead.
Check campaign access for staff who change fundraisers. Salesforce lets a user create or edit campaigns only with the Marketing User checkbox and Campaign Create and Edit. The Standard User profile only reads campaigns, and the packaged permission sets cannot grant a standard object, so give those staff a permission set of your own with Campaign Read, Create and Edit. See Give your team access.
Payments. A slow 3D Secure check keeps waiting instead of timing out; a refund retried after a network drop is recognised as the same refund; a renewal whose payment has not settled is no longer treated as failed.
Refund requests reach staff. The alert email for a donor's refund request is now sent reliably.
Smaller fixes. Event wizard saves the tax-deductible percentage and reports ticket-tier save failures; console dialogs close only from their own buttons; non-admin staff can see fund splits on a fundraiser and its receipt; guest-page headers scroll with the page.
The version number moves to 1.2.0 because this build adds new components (a patch version cannot). It upgrades from any 1.1.0 or 1.0.0 build.

1.1.0-1 — 18 September 2026 · released#

The public fundraising pages now load their typefaces through Salesforce's own resource loader instead of adding a stylesheet link to the page by hand. Donors see exactly the same fonts on the campaign gallery, the donation form, the thank-you page and the donor portal; the change exists so the package's security scan no longer reports those four page edits. Nothing to do after upgrading.
This is the first build after the 1.0.0 release, so the version number moves to 1.1.0. It upgrades from any 1.0.0 build.

1.0.0-8 — 8 September 2026 · released#

The Site & Domain panel in the fundraising Settings console now draws the Setup screens it is asking you to fill in, the way the Payments panel already did. Turning on Digital Experiences, choosing your domain, creating the site, assigning the guest permission set, granting the guest user Read on Campaign, and activating the site are each shown as the screen you are about to see, with the fields marked up — what to type, which default is wrong, what to leave alone.
Each of those screens is drawn at the state that completes the step, not the state Salesforce hands you: checkboxes already ticked, your own domain already filled in, permission sets already moved into Enabled Permission Sets. What you are looking at is the screen you are trying to reach, so you can tell at a glance whether you are done. The one exception is the site activation screen, which is drawn before you click Activate — the button is the step.
Nothing to do after upgrading. See Experience Cloud setup.

1.0.0-7 — 8 September 2026 · pre-release#

The Payments panel in the fundraising Settings console is now a ten-step guide that draws the Setup screen it is asking you to fill in. Each step shows the dialog you are about to see with its fields marked up — what to type, which default is wrong, what to leave alone — and every value it asks for is one click to copy. Both Stripe credentials are written out in full at every step, so there is no step that says "now do all of that again for the other one".
Step 7 of that guide now names both permission sets the credentials need: one for the site's guest user, and one for the staff and scheduled jobs that call Stripe with the admin key. Step 8 checks the guest user's Campaign read alongside the connection test and says which of the two is missing.
The packaged permission set for guest donors no longer lists grants on standard objects such as Campaign. Salesforce removes those from a managed package during the build, so the file was describing access no org ever received. Nothing that worked before stops working — but granting the guest user Read on Campaign is a manual step, as it always was in practice. Do it in a permission set of your own: Experience Cloud setup, step 5. The Settings console's Site & Domain panel checks that grant and tells you if it is missing.

1.0.0-6 — 5 September 2026 · pre-release#

Nothing changes in the app. This build exists so the package's security scan runs on every change to the code rather than on request, and so every finding the scanner reports carries a written verdict. Nothing to do after upgrading. See Security & code quality.

1.0.0-5 — 5 September 2026 · pre-release#

The staff consoles now check for a package licence seat. A user who holds the permission set but no seat sees a notice in place of the console; assign seats under Setup → Installed Packages → Manage Licenses. Donor and guest pages never check for a seat.
Donor portal sign-in is now a two-step emailed code instead of an emailed link. The donor types their email, receives an eight-character code that is good for 15 minutes and works once, and types it on the next screen. Sessions end after a period of inactivity and after a fixed maximum, the donor can sign out, and staff can end one by setting the donor's Portal Access Token record to Revoked. Links sent before the upgrade stop working; donors simply request a code. The wording on both sign-in screens comes from your Donor Portal settings — review it after upgrading. See Donor portal and Publish the donor portal.
The Fundraisers console is rebuilt as a tabbed workspace, and a new Donors console tab joins it in the app: find any donor, open them as a tab, send a portal code, print or email a receipt, refund a gift, or answer a request. See Donors console.
Dialogs on record pages (refunds, campaign updates, documents, FAQs, custom questions, event tickets) use the platform's standard modal. Appearance only; nothing to configure.
Security-review readiness: every open finding in the package's AppExchange readiness audit is closed, and the inventory is re-checked on every change. See Security & code quality.

1.0.0-4 — 2 September 2026 · pre-release#

Stripe credential fields are now named for what they must hold: a restricted key. A Payment Account that points at an unrestricted secret key is rejected with a message that says what to change. Existing accounts keep working; re-open Payments in the Settings console to see the new names.
The Settings console tells you which credential names are yours to choose and which are fixed by the platform.
The Code Analyzer findings the package carries are published with a verdict on each one, under Security & code quality.

1.0.0-3 — 1 September 2026 · pre-release#

Every scratch and test org is pinned to the US locale so currency behaviour is predictable. The product supports US and UK orgs only.
A Goal Amount on an Ongoing fundraiser is rejected at save time instead of being ignored.
Internal clean-up across most Apex and Lightning components after a full Code Analyzer pass. No behaviour change is expected; the suite runs at 95% coverage.

1.0.0-2 — 1 September 2026 · pre-release#

First build with every pull request gated on Code Analyzer and on 90% Apex coverage.
The Settings console's Site & Domain step no longer lists an Event Registration page that the package does not ship.

1.0.0-1 — 1 September 2026 · pre-release#

First version under the pledgivo namespace. Everything shipped in the earlier test builds is here: campaigns, one-off and recurring giving through Stripe, ticketed events, the donor portal, receipts, refunds, reconciliation jobs, the embeddable donate widget, and optional NPSP sync.
After installing, follow After you install. The package seeds what it is allowed to seed; the rest is a short checklist in the Get Started panel inside the app.