Required permissions for Salesforce and Salesforce NPSP integrations

Salesforce

Accessing profile settings

In Salesforce, go to Setup and use the Quick Find box to search for "Profiles". Configure permissions for the profile. This profile can be assigned to specific users later.

Custom App Settings

• Everything can be set to non-visible.
• The Default can be any of the options.

Tab Settings

Everything can be set to "Default Off".

Administrative Permissions

• API Enabled: Necessary as the integration uses the API in multiple areas.
• Customize Application: Required for connecting the integration and creating custom objects.
• Manage Profiles and Permission Sets: Essential for setting up the integration, including automatic profile permissions adjustments for new custom objects.
• Modify Metadata Through Metadata API Functions: Needed for connecting the integration.

General User Permissions

• Convert Leads: Required for the synchronization process.
• Edit Tasks: Required for the synchronization process.

Standard Object Permissions

For Accounts, Campaigns, Contacts, Opportunities, and Leads, the following permissions are required:

• Read: Necessary for mapping configurations.
• Create: Required for the synchronization process.
• Edit: Necessary for mapping configurations.
• Delete (only for Opportunities): Required for deleting pledge opportunities.

Custom Object Permissions

Ensure the following permissions are set for the "Recurring Plans" custom object, as they are essential for the sync process:

• Read
• Create
• Edit

Salesforce NPSP Specific permissions

In addition to the permissions outlined above, Salesforce NPSP integration requires permissions for the "Recurring Donations" custom object. These are all required for the connect and sync processes:

• Read
• Create
• Edit

Field-Level Security

In addition to object-level permissions, the integration user’s profile must have field-level visibility for the Salesforce fields used by Fundraise Up. Before connecting or testing the Salesforce NPSP integration, make sure the Salesforce profile or permission set used by the Fundraise Up integration user has field-level access to the Recurring Donation fields used by the integration. If a required field exists in Salesforce but is not visible to the user, sync can fail with an INVALID_FIELD, No such column, or “unable to access field” error.

How to check field-level security

In Salesforce:

• Go to Setup > Object Manager.
• Open Recurring Donation for Salesforce NPSP.
• Open Fields & Relationships.
• Search for each field API name listed below.
• Open the field and select Set Field-Level Security.
• Make sure Visible is enabled for the profile used by the integration user.

Fields to review for Salesforce NPSP

For Salesforce NPSP, review field-level visibility for the Recurring Donation object: npe03__Recurring_Donation__c.

Common Recurring Donation fields to check include:

• npe03__Contact__c
• npe03__Date_Established__c
• npsp__Day_of_Month__c
• npsp__PaymentMethod__c
• npsp__EndDate__c
• npsp__StartDate__c
• npsp__DisableFirstInstallment__c
• npsp__InstallmentFrequency__c
• npsp__CardLast4__c
• npsp__CardExpirationMonth__c
• npsp__Status__c
• npsp__ACH_Last_4__c

Additional fields may require visibility if they are used in the organization’s Fundraise Up mapping rules.