Salesforce Nonprofit Cloud: users with the same profile cannot see Program Cohort, Interaction, or Fundraising objects

Work through the causes below in order. Two users on the same profile can have different effective permissions if their permission set assignments differ.

Cause 1: A permission set or permission set group is not identically assigned to both users

1. Go to Setup > Users > Users and open the affected user's record.
2. In the Permission Set Assignments and Permission Set Group Assignments related lists, note every entry.
3. Open the working colleague's user record and compare the two lists item by item.
4. Assign any missing permission set: go to Setup > Users > Permission Sets, select the missing set, and click Manage Assignments > Add Assignment.
5. Assign any missing permission set group: go to Setup > Users > Permission Set Groups, select the missing group, and click Manage Assignments > Add Assignment.

Cause 2: The object has no Read access in any assigned permission set

1. Go to Setup > Users > Permission Sets and open the Nonprofit permission set assigned to the affected user.
2. Click Object Settings and locate the missing object.
3. For the Interaction related list under Person Account: enable Read on InteractionParticipant — this is the correct API name for the related list object under Person Account in NPC. Enabling the parent Interaction object alone is not sufficient.
4. Also assign the "Interaction Summary" permission set — this is the packaged NPC permission set that grants caseworkers access to Interaction records and detailed notes. Without it, the related list remains hidden regardless of object-level Read.
5. For Program Cohort / Program Cohort Member: enable Read on both ProgramCohort and ProgramCohortMember.
6. Assign either the "Advanced Program Management" permission set or the "Nonprofit Standard User" permission set group. Object-level Read on Program, ProgramCohort, ProgramCohortMember, and ProgramEnrollment must all be present together — granting one without the others causes silent access failures.
7. Click Save.

Cause 3: Fields are hidden by field-level security (FLS)

1. Go to Setup > Object Manager, select the affected object, and click Fields & Relationships.
2. Open each missing field and click Set Field-Level Security.
3. Set Visible to checked for the user's profile and all assigned permission sets.
4. Confirm the field is also on the correct page layout: Setup > Object Manager > [Object] > Page Layouts. Drag the field onto the layout for the correct record type (for example, Person Account Fundraising vs. Organization Fundraising).

Cause 4: A profile-level system permission is missing

1. Go to Setup > Users > Profiles and open the affected user's profile.
2. Grant View Setup and Configuration if the user needs setup-driven pickers such as queue lookups.
3. For Fundraising object and settings visibility, the following three conditions must all be met — object-level Read and a Fundraising Access PSL alone are not sufficient:

• Assign the Fundraising Access permission set license (PSL)
• Assign the relevant Fundraising Access permission set (grants object-level access to Fundraising objects such as Planned Gift, Giving History, and Donation records)
• Enable the "Fundraising User" system permission on the user's profile or a directly assigned permission set

1. Without the Fundraising User system permission, users will not see Fundraising configuration, settings pickers, or related Fundraising objects even if the PSL and permission set are correctly assigned.
2. After assignment, ask the user to log out and back in to refresh their permission context.

Verification: Log in as the affected user (Setup > Users > Users > Login) and open the relevant record page. Confirm the Program Cohort, Program Cohort Member, Interaction related list, or Fundraising fields now display, and that the user's view matches the working colleague's.