agentleFS
omoji-personalomoji-personal/torque/.agents/skills/salesforce-nonprofit-cloud/SKILL.md

salesforce-nonprofit-cloud

Skill0 starsChanged 3 days agoMITView on GitHub

Work in Salesforce Nonprofit Cloud (Agentforce Nonprofit), the native successor to NPSP. Use it before any design, build, data load or diagnosis in an org with Nonprofit Cloud objects such as GiftTransaction, and when planning a move from NPSP. Covers Fundraising, Program and Case Management, Grantmaking, Volunteer Management and Outcome Management, Person Accounts and households, Data Processing Engine rollups, gift entry, licenses and permission sets, metadata versus UI-only setup, gotchas with checks, and NPSP to Nonprofit Cloud migration.

The file

Files
SKILL.md

Salesforce Nonprofit Cloud

Nonprofit Cloud (NPC, marketed as Agentforce Nonprofit since late 2025) is native: its objects are standard objects with no namespace (GiftTransaction, not npsp__...), built on Industries components (Person Accounts, Group Membership, Data Processing Engine, Business Rules Engine, OmniStudio, Action Plans). Features arrive with the seasonal releases; there is no package to upgrade. NPSP is a different product (see the salesforce-npsp skill); moving from it is re-platforming.

State described: Winter '27, API 68.0. Items marked verify could not be confirmed in a primary source; test them in an org before repeating them to a client.

Reference files in this folder:

  • references/data-model.md: fundraising objects and lifecycle, households, rollups, programs, grantmaking, volunteers, outcomes.
  • references/gotchas.md: common failure modes, each with a check.
  • references/migration.md: NPSP to NPC object map, gaps, sequence, reconciliation.

First checks

QuestionCheck
NPC or NPSP?SELECT COUNT() FROM GiftTransaction succeeds only with NPC Fundraising; sf package installed list shows NPSP namespaces
Which features are licensed?Setup > Company Information > Permission Set Licenses: Fundraising Access, Grantmaking, VolunteerManagementPsl, Record Aggregation, Data Pipelines Base User
Person Accounts on?SELECT IsPersonAccount FROM Account LIMIT 1 compiles
Rollups running?Setup > Data Processing Engine has an active copy of each template in use; Setup > Monitor Workflow Services shows recent Completed runs
Commitment processing healthy?SELECT COUNT() FROM GiftCommitment WHERE LastNextGenCmtProcError != null (describe first; if the field is not filterable, select it and count non-empty rows)
Fundraising settingsFundraisingConfig (retrieve it): donor matching, lapsed and failing counts, next-transaction creation, household soft credits

A query that errors can also mean the running user lacks the licence or access: treat an error as "not checked" and confirm with the permission set licences. General build practice is in skills salesforce-build and salesforce-flow; this skill holds what is specific to Nonprofit Cloud.

A plain Developer Edition cannot be switched to NPC. For testing, use the 30-day trial, a scratch org with the Fundraising, ProgramManagement, Grantmaking, VolunteerManagement, OutcomeManagement, PersonAccounts and DataProcessingEngine features, or a sandbox of a licensed org.

Model in brief

  • Money. GiftTransaction is the payment and the unit of revenue (Status defaults to Unpaid). GiftCommitment plus GiftCommitmentSchedule is the promise (recurring gift or pledge). Opportunity is optional and means tracked solicitation.
  • Funds. GiftDesignation (one org-wide IsDefault), split per transaction by GiftTransactionDesignation, with defaults from GiftDefaultDesignation on a Campaign, Commitment or Opportunity.
  • Credit. GiftSoftCredit (role, partial amount or percent); household soft credits can be created automatically.
  • People. Person Accounts for individuals. A household is a business Account plus a PartyRelationshipGroup of Type Household plus an AccountContactRelation per member. Households are optional.
  • Rollups. Data Processing Engine definitions write DonorGiftSummary (per donor), GiftDesignation totals and OutreachSummary. Calendar-year only.
  • Entry. GiftEntry rows, alone or in a GiftBatch, processed into donors, transactions, designations and soft credits. Status and result stay as the audit trail.
  • Programs. Program, ProgramEnrollment, Benefit, BenefitSchedule, BenefitSession, BenefitAssignment, BenefitDisbursement.
  • Grantmaking (separate license, funder side): FundingOpportunity, ApplicationForm (use this; IndividualApplication appears to receive no new enhancements, verify), FundingAward, FundingAwardRequirement, FundingDisbursement.
  • Volunteers (API 64+): VolunteerInitiative, JobPosition, JobPositionShift, JobPositionAssignment.
  • Outcomes: ImpactStrategy, Outcome, IndicatorDefinition, IndicatorAssignment, IndicatorResult.

Licenses and permissions

FeatureAssign
FundraisingFundraisingAccess plus permission set group Fundraising_User or Fundraising_Admin
Households and groupsGroup Membership; merging needs a clone with Merge and Split Groups
Household naming"Automatic Household Creation and Naming" add-on license
Program ManagementProgram Management permission set; cohorts need Advanced Program Management
GrantmakingGrantmaking Manager, reviewer and Experience Cloud permission sets; every viewer needs a paid license
Volunteer ManagementVolunteer Management User group; portal and guest sets for sign-up sites
Outcome ManagementOutcome Management permission set
DPEData Pipelines Base User (few are included, and Fundraising_Admin uses one per admin; count them in Setup > Company Information, verify)

Assign permission set groups and extend with custom or muting sets, not ad hoc object permissions. Person Account object access comes from Account permissions, field-level security from Contact fields.

Metadata versus UI

Deployable: objects, fields, layouts, pages, flows, permission sets, FundraisingConfig, FieldMappingConfig, GiftEntryGridTemplate, BatchCalcJobDefinition (DPE), RecordAggregationDefinition, RelationshipGraphDefinition, Business Rules Engine definitions, ActionPlanTemplate, IndustriesSettings.

Per-org UI steps: enabling Person Accounts (irreversible), enabling Data Pipelines and its Salesforce output connector, assigning permission set licenses, Save As and Activate on shipped DPE templates, the Default Workflow User, duplicate rule activation, add-on licenses. Check activation state after any DPE deploy.

Data, not metadata: PartyRoleRelation roles, designations, source codes, benefit types, units of measure, programs, decision matrix rows. The Data Import Wizard does not support NPC objects; use Data Loader, Bulk API or an ETL tool.

Gotchas to check first

  • Nothing rolls up until each DPE template is copied with Save As and the copy activated and scheduled.
  • Three identities make DPE work: the admin with Data Pipelines Base User, the writeback user with full access to written objects, and the Analytics integration user with Read.
  • GiftTransaction Status defaults to Unpaid; loads that omit it create gifts rollups ignore.
  • Commitment Status is computed; loaded values do not stick.
  • ProgramEnrollment.IsActive defaults to false.
  • Donor summary "this year" is calendar year, never fiscal.

Full list with checks: references/gotchas.md.

Sources

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.