A donor wants last year's giving history, so she emails the fundraising team. A volunteer needs to swap a shift, so he calls the coordinator. A program participant wants to update a phone number, so she mails in a paper form. Each interaction pulls a staff member off other work, and together they add up to a real administrative burden. It is a technology gap with a known fix.
Salesforce Experience Cloud is the platform nonprofits use to build branded digital portals that give external users (donors, volunteers, beneficiaries, grantees, and members) authenticated access to the data already in Nonprofit Cloud. One org, one set of records, and the portal is a window into the same Salesforce data your nonprofit team works in every day. It gives the donors, volunteers, and clients you serve a single self-service digital experience, so they stop waiting on staff for answers they could find themselves.
This article covers what a well-built nonprofit portal on Experience Cloud actually does, the four portal types MagicFuse builds most often, the licensing decision that quietly determines whether a portal works, and what we find when we take over portals that were scoped wrong. We build Experience Cloud portals for nonprofit organizations across the UK, US, Europe, and Africa, from volunteer portals and donor portals to grantee portals and resident self-service platforms.
What Salesforce Experience Cloud Actually Does for Nonprofits
Experience Cloud (previously called Community Cloud, the same product renamed) gives external users authenticated access to your organization's Salesforce data through branded, secure portals. It sits on top of your Nonprofit Cloud org, so a donor's portal login reads from the same Contact record that holds their fundraising data. Because the portal writes back, two-way data integration keeps the central CRM up to date in real time, and staff see live data on the record.
What each user sees is governed by the license type, the profile and permission set behind their login, and the sharing model in the build. Role-based permissions keep sensitive information visible only to the right users. That is why the architecture decisions made before configuration matter: the license choice sets the ceiling on what external users can see, and changing it after go-live means reworking profiles, permissions, and sharing.
The platform ships with ready-to-use templates and drag-and-drop tools in Experience Builder, so nonprofits can create branded portal pages and personalized websites for stakeholders, shaping a consistent digital experience and digital presence without heavy development. Experience Cloud is a separate Salesforce product with its own licensing, so it is not part of the 10 donated Nonprofit Cloud licenses from the Power of Us Program. Eligible nonprofits can access discounted pricing, covered below.
The Four Nonprofit Portal Types MagicFuse Builds Most
Experience Cloud supports many use cases. Four portal types come up again and again for nonprofits, and each one is grounded in work we have delivered.
Donor Portals
Nonprofits can create personalized donor portals that remove the manual processes around giving history, gift receipts, and recurring donation changes, freeing fundraising staff for relationship work. Donors log in to see their full donation history, active recurring gifts, tax receipts, and fund statements, then update contact details or manage recurring donations on their own.
Since Salesforce's Spring 2024 release, nonprofits can expose Nonprofit Cloud fundraising objects (GiftTransaction, GiftCommitment, GiftSoftCredit, GiftRefund, and GiftTribute) to a donor portal through the FundraisingExperienceCloudAccessPsl permission set license, so donors review their giving to the last detail. Portals can also process secure debit and credit card payments through Salesforce's payment infrastructure for one-time or recurring donations, which adds transparency and trust.
Nonprofits can track donor engagement and key metrics through reports and personalized dashboards, so leadership can measure impact and feed it into strategic planning. Where donor portals fail is connection: when the fundraising objects are not wired up correctly, a donor logs in, finds no giving history, and emails the team anyway. Your fundraising connection gets configured as a core part of every donor portal build.
Volunteer Portals
A volunteer portal takes the coordinator out of the middle of every shift signup, onboarding step, and document request, which is most of the work in volunteer management. Volunteers browse opportunities, sign up for volunteer shifts online, view their history, upload documents like background checks and training certificates, and receive automated communications that inform volunteers about their impact, while service hours log automatically against their Salesforce Contact record.
Salesforce lists Experience Cloud as the way to share volunteer opportunities and simplify sign-up and onboarding through a branded volunteer portal, connected to Volunteers for Salesforce or the native volunteer objects. Automated workflows handle repeat tasks like volunteer onboarding and event registration, and nonprofits can create dedicated spaces for volunteer engagement.
Participant and Beneficiary Portals
A participant or beneficiary portal gives program participants and clients a secure, self-service way to interact directly, whether that means submitting information, viewing a care plan, accessing resources, or updating details, without staff handling every exchange by hand.
Program participants log in to see their program enrollment, care plan goals, resources, and referrals, and staff see each interaction on the participant's Nonprofit Cloud record in real time. This is where program managers get value: live data flowing back feeds the customizable dashboards they use to track program performance across multiple programs, and personalized dashboards give each stakeholder a view of what matters to them.
Nonprofits can also create separate communities for different programs, so each program gets its own space. Features like the Actionable Relationship Center help staff visualize how people, organizations, and gifts connect.
We built a portal like this for an African social enterprise working in affordable housing, where residents, applicants, and clients now apply for housing, pay bills, report repairs, and manage property details through a single platform connected to the Salesforce org. When these portals go wrong, it is usually because the participant data model in Nonprofit Cloud (person accounts, care plans, service deliveries, and custom objects) was not exposed correctly, and people from protected groups end up visible to the wrong staff. Getting the sharing model right is the whole job.
Member, Grantee, and Stakeholder Portals
Membership networks, grantmaking foundations, and standards bodies need a portal where external organizations and stakeholder groups manage a relationship across multiple channels. Members update details, view membership status, register for events, and stay connected through targeted communications; grantees submit applications, track status through the application process, and file reports, so grant management happens in Salesforce and every submission lands on one record staff can see.
Nonprofits can create branded member communities and grantee portals as distinct digital experiences, each tuned to a different audience. Community forums add peer-to-peer communication, giving community members and clients a space to collaborate and share knowledge, alongside a library of how-to articles for enhanced self-service.
We unified this for a global humanitarian standards network with more than 200 member organizations, whose stakeholder, membership, and verification data was scattered across several systems. We brought it together on Sales Cloud and Experience Cloud with events management, invoice generation, and third-party integrations like Zoom and Mailchimp, so the team runs member communications, billing, and events from one place with more transparency for members. The classic failure is silent duplication: an application form that creates a second Contact record every time, or an events tool that never syncs attendance back to the member's record.
The portal type matters less than the quality of the build. A donor portal that does not connect to Nonprofit Cloud fundraising objects, or a volunteer portal with the wrong sharing model, creates new work for staff and erodes trust with the people it should serve. If you are weighing up whether a portal fits your organization's mission, talk to MagicFuse first.
Talk to MagicFuse about building your nonprofit portal on Experience Cloud. Book a scoping call.
The Licensing Decision and What It Actually Means
Experience Cloud uses external user licenses, separate from the internal Salesforce licenses your staff hold, and the license you choose shapes the whole portal's architecture.
Salesforce offers a dedicated Experience Cloud for Nonprofits license, a nonprofit-priced version of its Partner Community license that brings partner relationship management level functionality to eligible organizations at a discount.
Its advantage is native access to objects in Nonprofit Cloud products, including the Nonprofit Success Pack, Volunteers for Salesforce, and Nonprofit Cloud Case Management, which suits portals that connect deeply to your program, fundraising, and case data. Through the Power of Us Program, eligible nonprofits reach core Salesforce products at reduced rates, and Experience Cloud licenses vary in user capacity and data management.
For simpler or very high volume portals, two other tiers come up. Customer Community is the lighter option: it supports sharing sets (record access based on a relationship, like a donor seeing their own gifts) but does not support sharing rules (criteria-based access, like a case worker seeing only clients in their district). That limit is documented by Salesforce and drives one of the most common and most expensive mistakes in nonprofit portal builds. Customer Community Plus adds sharing rules, role-based access, and full reports and dashboards, at a higher per-user cost and with more setup, because each external user needs a role.
Choosing the right license depends on how your users need to see data and which nonprofit objects the portal must reach. MagicFuse scopes this in discovery, before configuration begins, so the access model is correct from the first build.
What Goes Wrong When a Portal Is Not Built Correctly
The Experience Cloud engagement we take on most often is a rebuild: a portal scoped wrong the first time, brought back for repair. Here is what we tend to find.
The Portal Was Added After the Core Build
When a portal is bolted on after Nonprofit Cloud go-live, the sharing model was never designed for external access. External users end up able to see records they should not, a data protection risk, or unable to see records they need, which sends staff back to manual processes. Fixing it means rebuilding sharing rules, profiles, and page layouts. Plan every portal at the start of the Nonprofit Cloud build, even when it ships in a later phase.
The Wrong License Was Chosen at the Start
An organization picks Customer Community on cost, then finds it needs sharing rules that only Customer Community Plus supports. Correcting a license mid-project means deactivating users, migrating profiles, and reviewing data already live in the portal. A short scoping conversation at the start catches this every time.
The Donor Portal Was Built but Fundraising Objects Were Not Connected
Donors log in, see contact details, and find no giving history, no recurring donations, and no tax receipts, so the portal does not do the one thing they came for. The usual cause is a missing step: the FundraisingExperienceCloudAccessPsl permission set license that exposes Nonprofit Cloud fundraising objects was never configured. It is a documented, specific step, easy to miss without Nonprofit Cloud experience.
The Volunteer Portal Was Not Connected to Volunteer Records
Volunteers log in, but their shift history, hours, and documents never appear in Salesforce, so the coordinator keeps managing volunteer data in a separate system. Volunteers for Salesforce or the native volunteer objects were configured on one side and the portal on the other, never joined at the data model level.
The Portal Was Built but Never Adopted
The portal works, technically, and nobody uses it. Donors still email, volunteers still call, and staff avoid it because they do not trust the answers. This happens when a portal is treated as a technical project with no user testing, staff training, or onboarding for external users. A portal nobody uses costs more than no portal, because it needs maintenance while delivering nothing.
Why MagicFuse
MagicFuse is a Salesforce Summit Partner with more than 270 Salesforce certifications and over 80 certified consultants, including Experience Cloud and Nonprofit Cloud specialists certified on the Salesforce platform, built over 11+ years in the Salesforce ecosystem.
Our nonprofit Salesforce consulting and portal portfolio spans volunteer portals, member and stakeholder portals, resident self-service platforms, and fundraising-connected donor portals, delivered for organizations across the UK, Europe, and Africa. The architecture gets scoped before configuration starts, so your license type, sharing model, data connections, and adoption plan are defined before the build begins.
From portal builds to managed services, the self-service capabilities we deliver reduce the administrative burden on your nonprofit team, and we have shipped them for nonprofit clients across sectors.
Nonprofits come to us for portal services at different stages:
- New portal builds, designed correctly from the start and integrated with Nonprofit Cloud
- Rebuilds and rescues, taking over a portal that is not working and making it work
- Portal plus Nonprofit Cloud builds, where the portal architecture is part of the core implementation
- Managed services, for ongoing portal support and development after go-live
Talk to MagicFuse about building your nonprofit portal on Experience Cloud. Book a scoping call.
FAQs
- What is Salesforce Experience Cloud for nonprofits?
Experience Cloud is Salesforce's platform for creating branded, secure portals that give external users (donors, volunteers, beneficiaries, grantees, or members) authenticated access to data already in your Salesforce org. For a nonprofit on Nonprofit Cloud, a donor can check giving history, a volunteer can book a shift, or a beneficiary can view a care plan, all connected to the records your team uses internally. It was previously called Community Cloud; the product was renamed and the capabilities carried over.
- What can nonprofits build with Salesforce Experience Cloud?
The portal types nonprofits create most with us are donor portals (giving history, recurring donations, tax receipts, including the fundraising objects introduced in Spring 2024), volunteer portals (shift signup, onboarding, document management, hour tracking), participant or beneficiary portals (program enrollment, care plans, self-service updates), and member or grantee portals (membership management, grant applications, event registration, invoicing). Each runs on the same Salesforce instance as your core Nonprofit Cloud org, so the portal is a window into the same data.
- How much does Salesforce Experience Cloud cost for nonprofits?
Experience Cloud licensing is separate from your Nonprofit Cloud licenses and is priced by license type, number of external users, and whether you use a login-based or member-based model. Eligible nonprofits can access discounted pricing, including the dedicated Experience Cloud for Nonprofits license, though Experience Cloud is not part of the 10 donated licenses in the Power of Us Program. Because pricing shifts with use case and scale, the most accurate next step is a scoping conversation with MagicFuse or Salesforce.
- What is the difference between Customer Community and Customer Community Plus for nonprofits?
Customer Community is the lighter license, suited to portals where users mainly access their own records; it supports sharing sets (access based on a relationship) but not sharing rules (criteria-based access). Customer Community Plus adds sharing rules, role-based access, and full reports and dashboards, which you need for cases like a case worker who should see only their assigned clients. The wrong choice means rebuilding profiles, permission sets, and sharing later, so MagicFuse settles the right license in discovery.
- Can nonprofits build a donor portal in Salesforce that shows giving history?
Yes. Since Spring 2024, nonprofits can build donor portals in Experience Cloud that expose Nonprofit Cloud fundraising objects (GiftTransaction, GiftCommitment, GiftSoftCredit, GiftRefund, and GiftTribute) through the FundraisingExperienceCloudAccessPsl permission set license. Donors then view giving history, active recurring donations, and contribution records. It depends on correct configuration and is not on by default, so MagicFuse sets it up as part of donor portal builds.
- How long does it take to build an Experience Cloud portal for a nonprofit?
It depends on the portal type, the number of user personas, the state of your existing Nonprofit Cloud setup, and how much custom design the build calls for. The honest answer comes from scoping: once we understand those factors, we map a realistic timeline with you. Talk to MagicFuse and we will put together a plan for your build.
- Can we add an Experience Cloud portal to an existing Nonprofit Cloud setup?
Yes, though it takes more care than adding a portal to a fresh build. An existing setup usually needs a sharing model review, profile and permission set design for each external persona, and data model checks to confirm the right objects and fields reach the portal. If the original setup was built without external access in mind, some configuration may need to change first. MagicFuse assesses this in a structured discovery phase before scoping the build.
- What should we look for in a Salesforce partner for Experience Cloud nonprofit portals?
Look for Nonprofit Cloud experience specifically, because the data model tying portal records to fundraising, program, and case management objects differs from a standard org. Look for Experience Cloud delivery aimed at nonprofits, a clear architecture and licensing scoping process, and a track record of portals people actually adopted. As a nonprofit Salesforce consultant and Summit Partner, MagicFuse brings a nonprofit portal portfolio across volunteer portals, member portals, and beneficiary self-service platforms in several countries.
