Loading

Nonprofit Cloud Base Access Permission Set and Salesforce Go Tile Missing After P10 Provisioning

Data pubblicazione: Jul 29, 2026
Descrizione

The admin reported:

I am missing the Non-Profit Cloud Base Access Permission Set and its configuration package in Salesforce Go. I have program management and fundraising, but we only want to use Account and Contact relationship functionality. Can you please add this functionality and permissions?

Investigation in the org (with login access granted) confirmed:

  1. The P10 entitlement landed. The Nonprofit Cloud permission set licenses and several feature permission sets (Advanced Program Management, Fundraising Access, Outcome Management, and others) are present. These are seeded automatically when the licenses are provisioned.
  2. The Nonprofit Cloud Base Access permission set does not exist anywhere in the org, and there is no Nonprofit Cloud tile in Salesforce Go.
  3. Person Accounts is not enabled in the org.

Root-cause chain: the base access permission set and the Salesforce Go configuration are not provisioned with the licenses. They are created by the Nonprofit Cloud foundational setup. That setup has not been run, so the base access permission set and Salesforce Go tile are absent. The Account and Contact relationship data model the admin wants is built on Person Accounts, which is part of the foundational prerequisites and is likewise not yet enabled.

Risoluzione

There is no permission for Support to activate. The Base Access permission set and the Salesforce Go tile are created automatically when the admin runs the Nonprofit Cloud foundational setup. The licenses are already in place, so nothing is missing on the licensing side.

For the constituent (Account and Contact) relationship model only, the relevant step is the prerequisites, which enable Person Accounts and Group Membership. Fundraising, Program Management, and other feature areas do not need to be enabled to get the relationship model, and the licenses remain available to add those later.

Because Person Accounts is a one-way change (it cannot be turned off once enabled) and is enabled per org, prove it out in a sandbox first. Turning it on in a sandbox has no effect on production, so production does not need to be activated first. Recommended sequence:

  1. Enable Person Accounts directly in the sandbox (no production change required first).
  2. Run the remaining Nonprofit Cloud prerequisites in the sandbox and confirm the Base Access permission set and the Account and Contact relationship model appear as expected.
  3. Once validated, repeat the same steps in production during a planned maintenance window.
Numero articolo Knowledge

005390216

 
Caricamento
Salesforce Help | Article