Skip to main content

Hello! 

I am running into a user permission issue with NPSP Data Importer. Help! 

I am utilizing the NPSP Data Importer to upsert Donations related to new & existing Contacts. That is working just fine! On the same file, some donations will be associated to a new Organization Accounts only (no contact). For my (sys admin) upload, the new Organization is created correctly and the Donation is associated to it (I can see this on the Account1 Imported field). However, one of my users is doing the same action and the new Organization is not created with the Account1 Name field, but instead created as an Anonymous Household.  

The user 

does 

have access for create Organizations, so I am not sure what permission is missing to allow her to create a new Organization in the importer. Seeing as my import is working fine, she must be missing some mapping/field access somewhere but she has view all/modify all permission on NPSP Data Imports and NPSP Data Import Batches.  

 

What permission does she need for the NPSP Data Importer to create named new Organizations instead of Households in this import? 

 

Note: when the Organization exists in the system, the donation 

is correctly mapped to the Account1 in the Donation Donor field. I am only seeing this error when she attempts to create new Organizations.

2 answers
  1. Nov 5, 2025, 6:59 PM

    Hi @Michelle Dwyer

    This is happening because the user's default Account Record Type is assigned as Household Account. The default Account Record Type should be "Organization" (anything that isn't "Household Account.")  

     

    What is happening here is that the organization created is being assigned the Household Record Type, so NPSP is expecting a Primary Contact. Without the Primary Contact, it's invoking Household naming rules with unknown (Anonymous) contacts.  

     

    Hope that helps!

0/9000