Who sees and changes which records in the target — and with which licenses?

A migration is the one moment you get to rethink access without a change-management project, because everything is being configured fresh anyway. The question is not “what did NPSP grant?” — years of accumulated permissions are part of what you are leaving — but “who needs to see and change what, now?” Donor and gift records are personal data; the private-by-default posture, opened per persona (fundraising, finance, administration), grants access for a purpose rather than by inheritance. Where program management is in scope, say the quiet part aloud: program participation is sensitive in its own right, and its access model should be separate from fundraising’s, not inherited from it.

The pragmatic counterweight: a small team already living happily on a public sharing model should not buy complexity it will not maintain — a sharing model nobody understands is its own security risk. Two details deserve early attention because they carry cost and lead time. Permission-set licenses: which ones each persona needs for the fundraising objects is a licensing question to confirm with Salesforce, not something readable from metadata. And testing: every persona gets a test user that proves its access — both what it can reach and what it cannot — as part of go-live criteria, not after.

When Horus Eye assesses an NPSP org, this question is raised with the evidence the scan saw — the record types, fields and settings behind it — its recommendation marked, and the reasons stated. Accept records the recommendation; Change opens the options. Recording an answer writes nothing to Salesforce: it is captured in the decision register, with who decided and when, and the migration plan, mappings and documents are kept consistent with what your organization actually decided. Horus Eye recommends; your organization decides.

• 1. Salesforce Help · Security and Permissions for Nonprofit Cloud — The permission sets and access model of the target. ↩︎
• 2. Salesforce · Fundraising Implementation Guide (PDF) — How Fundraising is planned and configured in the target: processes, objects, gift entry, RFM scoring. ↩︎

“Salesforce”, “Agentforce” and related marks are the property of Salesforce, Inc. Horus Eye is an independent product and is not affiliated with, endorsed, or sponsored by Salesforce, Inc.