Top Salesforce Winter ’27 Release Features for Education and Nonprofit Teams

We went through the Salesforce Winter ’27 release across Nonprofit Cloud, Education Cloud, and the core platform to pull out the features that change the day-to-day for education and nonprofit teams.

Here are the six Winter ’27 features we think you should look at first, and how to think about turning them on.

A quick calendar note before you plan anything: the sandbox preview opens August 28, so refresh your sandbox by August 27 for early hands-on time. Production orgs upgrade on September 4, October 2, or October 9, depending on your instance. Details are in the official Salesforce Winter ’27 release notes.

Automatic household naming keeps donor records mailing-ready

A household groups the people who give, attend, and receive services together, and its name is what appears on acknowledgments, appeals, and mailings. When a family changes through marriage, divorce, or a new member, someone must remember to rename the record. An outdated name going out to a donor can be a big slip up. 

Winter ’27 brings automatic household creation and naming to Agentforce Nonprofit (Nonprofit Cloud). You set a naming pattern once at the org level, and Salesforce recalculates the household name and greeting in real time as membership changes. You can flag individual households to leave alone when you want to name them by hand.

This is the feature that stands out most for fundraising teams, because it closes a gap that NPSP handled and that Nonprofit Cloud implementations have had to rebuild. It removes a recurring cleanup task and a common source of embarrassing mail. It ships in both Agentforce Nonprofit and Agentforce Education with the Automatic Household Creation and Naming add-on, so advancement teams on either cloud benefit. For any organization that generates appeals or acknowledgments from Salesforce, this is a big win for feature parity.

Release note: https://help.salesforce.com/s/articleView?id=release-notes.rn_fundraising_auto_household_naming.htm&release=264&type=5

Create households during gift entry without a separate build

Households can now be created directly from the Gift Entry Grid or through the Business Process API, with no separate automation to build or maintain. Gift officers get organized donor data at the point of entry, and partners can create households in bulk using gift or commitment payloads.

The practical result is that donor records are complete when the gift is recorded, so reporting gaps close immediately instead of surfacing at year-end. Paired with automatic naming, this covers two common custom automations we have built on Nonprofit Cloud fundraising projects.

Release note: https://help.salesforce.com/s/articleView?id=release-notes.rn_fundraising_automate_household_gift_entry.htm&release=264&type=5

The Attendance Management Agent turns absences into one automated follow-up

When a student is marked absent, the follow-up has traditionally fallen to staff: a call home, a note to the teacher, a manual update to the record. In a busy K-12 front office, some of that simply does not happen, and the attendance record drifts away from reality.

The new Attendance Management Agent in Education Cloud automates the whole loop. A Marketing Cloud Next flow sends an SMS to the family as soon as a student is marked absent. An inbound Omni-Channel flow lets the parent explain the absence in a natural conversation with a voice agent, with no form and no phone tag. The agent captures the reason, updates the student’s official attendance record, and notifies the responsible instructor in Slack.

Families, the record, and the instructor stay in sync without adding to anyone’s workload. It does rely on a few connected pieces, including Marketing Cloud Next, Omni-Channel, and Slack, so confirm those are in place before you scope it.

Release note: https://help.salesforce.com/s/articleView?id=release-notes.rn_edu_resolve_absences_with_voice_agent.htm&release=264&type=5

Managing student accounts in Education Cloud gets easier

Three Winter ’27 updates to Student Financials add up to a real change in how students and staff handle money. Together they cover the billing questions that generate the most email and the most manual work.

First, students can see their own billing. Self-service access gives them detailed invoices, installment plans, and payment timelines, plus a unified account view that brings refund, payment, and credit balances into one place. More accurate term-level fee breakdowns mean fewer balance questions land on staff.

Second, flexible payment plans let students spread tuition over monthly, quarterly, or custom installments, with collection running automatically through integrated gateways. Students track plan status and upcoming auto-debits from the learner portal, so there are no surprises on either side.

Third, overpayment refunds run end to end. When a student drops a course or reduces an order, Student Financials identifies the original invoices, applies credit memos to outstanding balances, and initiates refunds, with a full audit trail for compliance.

For a bursar or student accounts team, this is less about any single feature and more about fewer manual touchpoints across the whole account lifecycle.

Release note (self-service billing): https://help.salesforce.com/s/articleView?id=release-notes.rn_edu_share_billing_details_students.htm&release=264&type=5

Release note (flexible payment plans): https://help.salesforce.com/s/articleView?id=release-notes.rn_edu_spread_tuition_payments_flexible_payment_plans.htm&release=264&type=5

Release note (automated refunds): https://help.salesforce.com/s/articleView?id=release-notes.rn_edu_automate_refund_processing_student_overpayment_refunds.htm&release=264&type=5

Preview records from a report without losing your place

Everyone knows the pattern. You are working through a report, you click into a record to check one field, and now your filters are gone because you forgot to save. Getting back to where you were costs more time than the check did.

Record preview opens record details in a side panel while your report filters, columns, and place in the list all stay put. A fundraiser working a report of lapsed donors can move down the list checking giving history without ever leaving the report. One caveat worth being clear about: this feature is beta, so Salesforce can still change it. Try it in a sandbox before you build a process on it.

Release note: https://help.salesforce.com/s/articleView?id=release-notes.rn_rd_reports_record_preview.htm&release=264&type=5

Inline editing in list views finally works across multiple record types

Editing records straight from a list view is the fastest way to clean up a batch of data, but two limits have always gotten in the way. You could edit only the fields that sat on the page layout, and any list containing more than one record type turned editing off entirely.

Winter ’27 adds two optional settings that remove both limits. Users can edit any field they have access to, whether or not it appears on the layout, and mixed record types no longer block inline editing. Both settings are off by default, so nothing changes until an admin turns them on.

For teams that manage records across multiple record types, this removes a daily friction point that has no good workaround today. Turn it on deliberately: once the layout restriction is gone, field and object permissions are the only thing governing who can edit what, so audit access first.

Release note: https://help.salesforce.com/s/articleView?id=release-notes.rn_list_views_inline.htm&release=264&type=5

How to decide what to turn on in the Salesforce Winter ’27 release

So what should you do with this? Start with the calendar. Refresh a sandbox before August 27 so you have time to try these features before they reach production. Then look at the six above and pick the two or three that map to a problem your team has right now, instead of turning on everything at once.

Check the conditions before you commit. In-report record preview is in beta, so keep it in a sandbox for now. The inline editing settings are off by default, and once you remove the layout restriction, field and object permissions govern who can change what. The Attendance Management Agent depends on Marketing Cloud Next, Omni-Channel, and Slack being in place. Turn a feature on in a sandbox first, confirm it fits your data model, then plan how you will roll it out and get your team using it.

If you want help mapping which Winter ’27 features are worth enabling for your organization and how to roll them out without disrupting what already works, that is the kind of question our Committed Consulting managed services team handles every release cycle. Reach us at booking@elevation.solutions.