Under the Household Account model in Salesforce NPSP, a Contact's Account represents where they live, essentially their Household. The Primary Affiliation, on the other hand, indicates where they work or are affiliated professionally.
* Household Account:
* This is used to group individuals living at the same address into a single account.
* All contacts associated with a Household share the same Account record, representing their home address and family unit.
* Primary Affiliation:
* This is a special relationship field in NPSP that links a Contact to an Organization or company where they work or have a significant relationship.
* It allows nonprofits to track where their constituents are employed or connected professionally, separate from their residential information.
References:
CertGod Nonprofit Cloud Consultant Guide

For a large nonprofit organization functioning like a for-profit corporation and needing to manage Leads and track its Opportunity pipeline:
* Salesforce Account Model without NPSP: This model is suitable as it aligns with for-profit business processes, focusing on managing business accounts, leads, and opportunities. The Household Account Model in NPSP is more suited for organizations managing individual donors, which is not applicable here.
Using the standard Salesforce Account Model allows the organization to leverage Salesforce's CRM capabilities tailored for B2B interactions.
References:
Salesforce Account Model Documentation
Salesforce Trailhead: Managing Leads and Opportunities

When setting up Volunteers for Salesforce in an international context, it's important to ensure that volunteer jobs and shifts reflect the local time zones accurately. Here's how to configure this:
* Navigate to Volunteers for Salesforce Settings:
* Go to Setup.
* Type "Volunteers for Salesforce" in the Quick Find box and select it.
* Configure Volunteer Jobs:
* Create Volunteer Jobs for each country.
* For each job, set the "Website Time Zone" field to the local time zone where the job will take place.
* Adjust Volunteer Shift Times:
* When creating volunteer shifts, ensure the start and end times are set according to the local time zone.
* Update Website Information:
* Inform volunteers about the time zone settings on the volunteer signup pages if necessary.
"Volunteers for Salesforce Setup Guide" from Salesforce Help: Volunteers for Salesforce
"Managing Volunteer Shifts and Jobs" from Salesforce.org: Volunteer Management

To retain the legacy system's 150 donation appeal source codes as historical data in NPSP, you should follow these steps:
* Create Campaigns for Each Legacy Source Code:
* Navigate to the Campaigns tab in Salesforce.
* Create a new Campaign for each of the 150 legacy source codes.
* Name the Campaigns according to the source codes for easy identification.
* Prepare Your Import Data:
* Ensure that your import data includes a column for Campaigns, where you can map each donation to the corresponding legacy source code Campaign.
* Import Contacts and Opportunities:
* Use the Data Import Wizard or Data Loader to import your Contacts and Opportunities.
* During the import process, map the source code field in your data to the appropriate Campaign in Salesforce.
* Relate Contacts and Opportunities to Campaigns:
* Ensure that each Contact and Opportunity record is related to the correct Campaign representing the legacy source code.
By organizing your legacy source codes into Campaigns and mapping your import data accordingly, you can effectively retain and manage historical donation appeal source codes in NPSP.
References:
Nonprofit Success Pack (NPSP) Data Import documentation.
Salesforce documentation on Campaigns and data import processes.

Install NPSP:
Ensure that NPSP is installed in your Salesforce instance. You can download it from the AppExchange or install it directly from the NPSP Installer page.
Configure Acknowledgement Settings:
Navigate to NPSP Settings.
Under "Donations," find the "Acknowledgements" settings.
Configure the settings to define when and how acknowledgements should be sent.
Set Up Email Templates:
Go to Setup > Classic Email Templates.
Create a new email template or modify an existing one to suit your acknowledgment needs.
Ensure the template includes merge fields to personalize the emails with donor information.
Create Automation with Process Builder:
Use Process Builder to automate the sending of acknowledgment emails.
Create a new process on the Opportunity object.
Set criteria to trigger the process when a new donation is recorded.
Add an action to send an email using the previously created template.
Testing:
Test the process by creating a test donation record and verifying that the acknowledgment email is sent automatically.
Monitoring and Refinement:
Monitor the process to ensure it is working correctly.
Refine the email templates and automation rules based on feedback and evolving needs.
By utilizing the NPSP, nonprofits can streamline their donation acknowledgment process, ensuring timely and personalized communications with donors, ultimately enhancing donor satisfaction and retention.