To create a report that shows who the solicitor is for each donor using automated soft credits, the system admin should use the "Opportunities with Partial Soft Credits and Contacts" report type. This report type allows the inclusion of soft credits and the related contacts, making it possible to track the solicitor for each donation.
Steps to Create the Report:
Choose the Report Type:
Navigate to the Reports tab and click "New Report."
Select the "Opportunities with Partial Soft Credits and Contacts" report type.
Customize the Report:
Add the necessary fields to display the solicitor, donor, and relevant opportunity information.
Use filters to refine the data as needed.
Save and Run the Report:
Save the report with an appropriate name and run it to view the results.
Salesforce Nonprofit Success Pack Documentation
Salesforce Trailhead: Create and Customize Reports

When a system administrator attempts to delete a Household Account record that has Contacts with Recurring Donations, Relationships, and closed/won donations, Salesforce will display an error message due to the presence of closed/won donations associated with the Account record.
Log in to Salesforce: Access the Salesforce org where NPSP is installed.
Navigate to the Household Account:
Go to the Accounts tab and locate the Household Account record.
Attempt to Delete the Account:
Try to delete the Household Account record.
Salesforce will prevent the deletion and display an error message because there are closed/won donations linked to this Account.
Review Associated Records:
Check for closed/won Opportunities and other related records that are preventing deletion.
If necessary, consider reassigning or archiving these records instead of deleting the Household Account.
This safeguard ensures data integrity by preventing the loss of critical financial records.

When integrating an external email platform with Salesforce, it's important to consider storage implications and retention policies. Here are the steps to take into account these considerations:
Evaluate Storage Requirements:
Campaign Member records are used to track email interactions within Salesforce. These records typically consume less storage compared to creating a custom object for the same purpose.
Custom objects can lead to higher storage usage, especially if tracking detailed interaction data.
Retention Policies:
Understand the email platform's data retention policies. Some platforms allow you to specify how long subscriber activity data (such as opens, clicks, and unsubscribes) should be retained.
Configure the retention settings to align with your organization's data retention policies and compliance requirements.
Integration Setup:
Set up the integration to ensure that Campaign Members are created or updated with each email interaction.
Use the external email platform's API to push data into Salesforce, ensuring that Campaign Members are updated in real-time or through scheduled syncs.
Monitor and Optimize:
Regularly monitor storage usage in Salesforce and optimize data retention settings to balance between having sufficient historical data and managing storage costs.
Salesforce Storage Usage Best Practices: Detailed best practices for managing storage in Salesforce. Salesforce Help.
Email Platform Integration Guides: Specific guides for integrating popular email platforms with Salesforce (e.g., Mailchimp, Pardot).

(https://trailhead.salesforce.com/en/content/learn/modules/contact-and-account-settings-in-nonprofit-success-pack/merge-duplicate-contacts-and-accounts-npsp) When encountering errors while trying to merge contacts using the NPSP Contact Merge tab, the following issues are likely causes:
Delete Access to Contacts:
The user needs to have delete access to the contacts being merged. Without the necessary permissions, the user will not be able to complete the merge operation.
Ensure that the user's profile or permission set includes delete permissions on the Contact object.
Unique External ID:
If a unique external ID is retained from the non-master contact, it can cause conflicts during the merge process. The system expects unique external IDs to remain unique, and retaining an ID from a record that is being merged (and effectively deleted) can create issues.
Salesforce Nonprofit Success Pack Documentation
Salesforce Merge Contact Permissions Guide

When the system administrator notices a scheduled skew job but does not remember scheduling it, the best course of action is to view the Setup Audit Trail. This will help determine the origin and purpose of the job. Here's how to do it:
Navigate to Setup:
Click on the gear icon in the top right corner of Salesforce.
Select "Setup".
Access the Setup Audit Trail:
In the Quick Find box, type "Setup Audit Trail".
Click on "View Setup Audit Trail".
Review the Audit Trail:
The Setup Audit Trail logs changes made to your Salesforce configuration, including scheduled jobs.
Look for entries related to the creation or modification of scheduled jobs.
Identify who created the job, when it was created, and any additional details provided in the log.
Determine Next Steps:
Based on the information found in the audit trail, decide whether the job is necessary.
If the job is not needed, it can be deleted. If it is essential, ensure that it is documented and understood.
Salesforce Documentation: Monitor Setup Changes
Salesforce Trailhead: Monitor Changes in Your Org