Salesforce Nonprofit-Cloud-Consultant Salesforce Certified Nonprofit Cloud Consultant (SU24) Exam Practice Test

A Salesforce-recommended governance structure for nonprofit organizations ensures the implementation runs smoothly and effectively. It typically includes the following elements:

Release Management: This ensures that changes are systematically planned, tested, and deployed. It involves managing how new features and updates are rolled out to avoid disruption and ensure smooth transitions.

Rules of Engagement: These define how different stakeholders will interact with the system and with each other. It includes protocols and guidelines for communication, decision-making, and responsibilities.

Center of Excellence (CoE): This is a dedicated team or a hub of experts that provides leadership, best practices, research, support, and training. A CoE helps ensure that the organization is leveraging Salesforce effectively and efficiently.

References:

Salesforce Nonprofit Cloud Implementation Guide

Salesforce Trailhead: Governance Framework

To track specific funds associated with gifts from individuals and organizations in NPSP, the consultant should create General Accounting Unit (GAU) records for each of the funds and associate them with the Opportunity by GAU Allocation record amounts.

Steps:

Log in to Salesforce: Access the Salesforce org with NPSP installed.

Create GAU Records:

Navigate to the App Launcher and search for "General Accounting Units".

Click "New" to create a new GAU record for each fund.

Fill in the necessary details such as GAU Name, Description, and any other relevant information.

Save the GAU records.

Associate GAUs with Opportunities:

Navigate to the Opportunity related to the donation.

In the Opportunity record, find the "GAU Allocations" related list.

Click "New" to create a new GAU Allocation.

Select the appropriate GAU record from the lookup field.

Enter the allocation amount and any other necessary details.

Save the GAU Allocation record.

Reporting: Use standard or custom reports to track and report on GAU Allocations for reconciliation with the finance system.

References:

CertGod Nonprofit Cloud Consultant Guide

When a corporate matching gift is received and the original donor did not indicate that it was to be matched, the consultant should recommend using the "Find Matched Gifts" feature. This feature helps in identifying and linking the matching gift to the original donation:

Select Find Matched Gifts: This option is available within the Nonprofit Success Pack (NPSP) and is designed to help match donations.

Click on the Find More Gifts button: This button will allow the development associate to search for and match the original donation with the corporate matching gift.

This process ensures that all matched gifts are accurately recorded and credited appropriately.

References:

Salesforce Nonprofit Success Pack Documentation

Salesforce Trailhead: Matching Gifts in NPSP

To send a mailing to all clients and track who was sent the invitation and who responded, you should use Campaigns in NPSP. Here’s how to set it up:

Create a Campaign:

Navigate to the Campaigns tab.

Click "New Campaign" and fill out the necessary details such as Campaign Name (e.g., "Workforce Development Program Invite").

Filter List View for Clients:

Go to the Contacts tab.

Create a new list view or filter an existing one to include only clients. This might include adding filters for criteria that identify clients, such as specific Account Record Types or custom fields.

Add Contacts to Campaign:

Select all the clients in the list view.

Use the "Add to Campaign" button to add these Contacts to the previously created Campaign.

Track Responses:

After sending the invitations, track responses by updating the Campaign Member Status. This can be done manually or through an automated process if you have integrated email tracking.

Create a Campaign Report:

Go to the Reports tab.

Create a new report using the "Campaigns with Campaign Members" report type.

Filter the report to show the specific Campaign and the statuses of the Campaign Members (e.g., "Sent", "Responded").

This process ensures that the nonprofit can track who the invitations were sent to and who has responded, providing a clear view of the engagement for the workforce development program.

References:

"Campaign Management in NPSP" from Salesforce Help: Campaign Management

"Creating and Managing Campaigns" from Salesforce.org: Campaigns Guide

Updates to the Nonprofit Success Pack (NPSP) are pushed to production organizations once every two weeks. These frequent updates ensure that organizations using NPSP have access to the latest features, bug fixes, and improvements. Here’s what you need to know:

Regular Updates:

NPSP follows a bi-weekly release schedule, meaning updates are deployed approximately every two weeks.

Automatic Updates:

These updates are automatically pushed to production environments, requiring no manual intervention from administrators.

Release Notes:

Release notes for each update are published and can be accessed to understand the changes and new features included in each release.

Testing and Sandbox Environments:

It’s recommended to test updates in a sandbox environment before they are deployed to production, especially if customizations are in place.

References:

"NPSP Release Schedule" from Salesforce.org: NPSP Release Schedule

"Release Notes and Announcements" from Salesforce.org: NPSP Release Notes

To automatically add donors who give to the Capital Fund to the Capital Campaign:

Enable Automatic Campaign Member Management in NPSP Settings: This feature allows automatic management of Campaign Members based on criteria defined in NPSP settings.

Populate the Primary Campaign Source Field on the Opportunity Record: By setting the Primary Campaign Source on the Opportunity record, donors can be automatically added to the associated Campaign.

These steps ensure that any donor contributing to the Capital Fund is automatically linked to the Capital Campaign, streamlining the process and ensuring accurate tracking.

References:

Salesforce Nonprofit Success Pack Documentation

Salesforce Trailhead: Managing Campaigns in NPSP

To allow prospective volunteers to fill out their volunteer application online:

Set up the Volunteers for Salesforce Volunteer Signup Form: This form can be embedded on the nonprofit's website, allowing prospective volunteers to submit their information directly into Salesforce.

This approach leverages the existing Volunteers for Salesforce functionality, making it easy to capture and manage volunteer applications.

References:

Salesforce Volunteers for Salesforce Documentation

Salesforce Trailhead: Setting Up Volunteers for Salesforce

To capture information for grants and easily access previous grant details, the following setup can be used in Salesforce:

Previous Grant/Gift Opportunity Lookup Field:

Add a lookup field on the Opportunity object called "Previous Grant/Gift Opportunity".

When creating a new grant Opportunity, fill in this field with the previous grant's Opportunity record.

Is Grant Renewal Checkbox:

Add a checkbox field on the Opportunity object called "Is Grant Renewal".

Check this box for Opportunities that are renewals of previous grants.

Grant Tracking and Reporting:

This setup allows easy tracking of grant renewals and provides a straightforward way to report on grants and their renewals.

Use reports and dashboards to summarize and analyze grant data, including renewals.

By linking each renewal grant to the original grant Opportunity, you maintain a clear record of the grant history, making it easy to access previous grant information and analyze grant renewals.

References:

"Grant Management Best Practices" from Salesforce Help: Grant Management

"Nonprofit Success Pack Grant Management" from Salesforce.org: NPSP Grant Management

After migrating to a Nonprofit Success Pack (NPSP) Salesforce org, it's essential to ensure that all migrated Accounts are consistent with the chosen account model. The Data Quality Analysis Dashboard is a vital tool for this purpose.

Data Quality Analysis Dashboard:

This dashboard provides comprehensive insights into data quality across the org.

It helps identify inconsistencies, missing data, and discrepancies in Account records.

Steps to Ensure Consistency:

Run the Data Quality Analysis Dashboard:

Navigate to NPSP Settings and select the Data Quality Analysis Dashboard.

Review the results to identify any Accounts that do not conform to the expected account model.

Address Identified Issues:

Correct any identified discrepancies by updating the Account records to align with the chosen model (e.g., Household Account Model).

Regular Monitoring:

Schedule regular runs of the Data Quality Analysis Dashboard to maintain data integrity over time.

Benefits of Consistency:

Ensures accurate reporting and analytics.

Improves data integrity and usability across the organization.

Facilitates better donor and constituent management.

Complementary Tools:

While the Data Quality Analysis Dashboard is primary, tools like the NPSP Health Check Tool and Salesforce Optimizer can provide additional insights into overall org health and performance.

References:

CertGod Nonprofit Cloud Consultant study guide: "Run the Data Quality Analysis Dashboard"​​.

When setting up a sandbox strategy for a nonprofit implementation project involving two major development initiatives, it is essential to use separate sandboxes for different purposes. The key purposes include Quality Assurance, Staging, and Development. Here’s why:

Quality Assurance (QA):

QA sandboxes are used to test new features and functionalities to ensure they work as expected.

This environment helps identify and fix bugs before the changes are moved to production.

Staging:

A staging sandbox is a replica of the production environment.

It is used for final testing and validation of new features, configurations, and data migrations.

Ensures that everything works correctly in an environment that closely mimics production.

Development:

Development sandboxes are used by developers to build and test new features.

Each developer can have their own sandbox to avoid conflicts with others’ work.

Using separate sandboxes for these purposes ensures a clear and organized development process, reduces the risk of conflicts, and helps maintain a stable production environment.

References:

Salesforce Documentation: Sandbox Types and Templates

Salesforce Trailhead: Developing in Sandboxes

For managing social media presence, listening to constituents, measuring impact, and managing activities from a mobile app, Salesforce's Social Studio is the recommended tool.

Social Studio Overview:

Social Studio is a powerful social media management tool within Salesforce.

It provides capabilities for social listening, publishing, engagement, and analytics across multiple social media platforms.

Features and Capabilities:

Social Listening:

Monitor social media channels for mentions, comments, and conversations about the organization.

Identify trends and sentiment to understand constituent engagement and feedback.

Publishing:

Schedule and publish content across multiple social media platforms.

Manage social media campaigns and track their performance.

Engagement:

Interact with constituents directly from the platform.

Manage responses and engage with the audience in real-time.

Analytics:

Measure the impact of social media activities.

Use dashboards and reports to gain insights into engagement, reach, and sentiment.

Mobile App Management:

Social Studio includes a mobile app that allows users to manage social media activities on the go.

This ensures that social media management is not limited to the desktop and can be handled efficiently from anywhere.

Implementation:

Set up Social Studio within the Salesforce environment.

Configure social media accounts and start tracking and managing social media activities.

References:

CertGod Nonprofit Cloud Consultant study guide: "Social Studio"​​.

When installing NPSP (Nonprofit Success Pack) in an existing Salesforce org for a nonprofit organization that plans to use the memberships feature, the consultant should create a Membership Opportunity record type. This step is crucial because it allows the organization to effectively track and manage membership-related opportunities distinctly from other types of opportunities.

Steps:

Log in to Salesforce: Access the Salesforce org where NPSP will be installed.

Navigate to Object Manager: Go to Setup and search for "Object Manager".

Select Opportunity Object: From the Object Manager, select the Opportunity object.

Create a New Record Type:

Click "Record Types" under the Opportunity object.

Click "New" to create a new record type.

Enter "Membership" as the Record Type Label.

Provide a description such as "Record type for tracking membership opportunities".

Select the existing record type to clone from (e.g., "Master").

Assign this record type to appropriate profiles.

Click "Save".

Customize Page Layouts: Assign and customize page layouts for the new Membership record type as needed.

Verify and Test: Ensure that the Membership record type is correctly set up by creating a test membership opportunity.

References:

CertGod Nonprofit Cloud Consultant Guide

In the Nonprofit Success Pack (NPSP), donations can be credited in two ways: hard credits and soft credits. Hard credits reflect direct donations, while soft credits are used to acknowledge indirect contributions, such as when a donor's employer matches a donation.

Hard Credits:

Hard credits represent the actual donor who made the donation.

In this scenario, the employer who matches the donation will receive a hard credit for the matched amount.

Soft Credits:

Soft credits are used to recognize individuals or entities who influenced or facilitated the donation but are not the direct donors.

The donor will receive a soft credit for the amount matched by their employer.

Scenario Application:

The donor made a donation of $500. This is a hard credit for the donor.

The employer matches this donation with another $500. The employer receives a hard credit for this matched amount.

The donor is acknowledged for facilitating the matched gift, thus receiving a soft credit of $500.

Implementation in NPSP:

To implement this, configure the Opportunity Contact Role to automatically assign soft credits to related contacts, such as employers matching donations.

Use the NPSP Settings to ensure that soft credit roles are correctly assigned and tracked.

References:

CertGod Nonprofit Cloud Consultant study guide: "The donor has a soft credit of $500 and the employer has a hard credit of $500"​​.

When troubleshooting the issue of Recurring Donation Opportunities having close dates at the end of the month instead of the 15th, the consultant should check if the "Always use last day of the month" field is selected. This field setting overrides other close date settings and defaults the close date to the last day of the month.

Log in to Salesforce: Access the Salesforce org where NPSP is installed.

Navigate to NPSP Settings: Go to the App Launcher, search for "NPSP Settings", and select it.

Find Recurring Donations Settings:

In NPSP Settings, expand the "Donations" section.

Click on "Recurring Donations".

Check the "Always use last day of the month" Field:

Locate the "Always use last day of the month" setting.

Verify whether this checkbox is selected.

If selected, uncheck this option if you want the close date to follow the Day of the Month picklist value.

Save the Settings: Save any changes made and verify that new Recurring Donations reflect the correct close date.

By ensuring this field is not selected, the system will correctly use the 15th of the month as specified in the Day of the Month picklist.

To track website visitors who download white papers, case studies, and impact reports, and subsequently pursue them as constituents, Pardot is the recommended solution. Pardot provides robust marketing automation features that can effectively manage and nurture leads. Here’s how to set it up:

Install Pardot:

Purchase Pardot and install it in your Salesforce org.

Configure Pardot Tracking:

Add Pardot tracking code to your website.

This code will track visitor behavior, including downloads of white papers, case studies, and impact reports.

Create Pardot Forms and Landing Pages:

Use Pardot to create forms and landing pages for visitors to fill out before they can download the assets.

These forms will capture visitor information and automatically create a prospect in Pardot.

Set Up Automation Rules:

Create automation rules in Pardot to add prospects to specific lists based on their behavior.

For example, create a rule to add a prospect to a "White Paper Download" list if they download a white paper.

Sync Pardot with Salesforce:

Ensure that Pardot is integrated with Salesforce to sync prospects as leads or contacts.

Use Salesforce campaigns to track these leads and monitor their progress.

Nurture Leads:

Use Pardot’s email marketing and nurturing capabilities to engage with these leads.

Track their interactions and score them based on their engagement to prioritize follow-ups.

By using Pardot, the nonprofit can efficiently track and engage website visitors, converting them into valuable constituents.

References:

Salesforce Pardot Documentation: Pardot Tracking Code

Salesforce Trailhead: Marketing Automation with Pardot

For a nonprofit organization looking for a CRM with an integrated email marketing tool that includes built-in scoring and engagement tracking, the recommended solution is:

NPSP (Nonprofit Success Pack): This provides the CRM functionality to manage constituents.

Marketing Cloud: This offers advanced email marketing capabilities, including automation, scoring, and engagement tracking.

Marketing Cloud is designed to handle complex marketing needs and integrates seamlessly with NPSP to provide a comprehensive solution for nonprofits.

References:

Salesforce Nonprofit Success Pack Documentation

Salesforce Marketing Cloud Overview

Understanding the trial experiences available on the Salesforce.org website is crucial for setting expectations and planning custom configuration work. Here’s detailed information about the trial options:

Available Trial Experiences:

Lightning Enterprise: This option provides a standard Salesforce Lightning Enterprise edition, suitable for exploring core CRM capabilities.

Lightning Enterprise + NPSP: This trial includes the Nonprofit Success Pack (NPSP) on top of the Lightning Enterprise edition, tailored specifically for nonprofit needs.

Free Trial Period:

The free trial period for Salesforce.org trials is 30 days. This provides enough time to explore features, gather requirements, and conduct initial custom configuration work.

Why Not Other Options:

Option A: While free licenses may be available for qualified customers, this is separate from the trial experience and not universally applicable.

Option D: The trial orgs provided by Salesforce.org are typically not Developer Edition orgs but are configured to showcase the Enterprise capabilities with or without NPSP.

By knowing that the trial choices include Lightning Enterprise or Lightning Enterprise + NPSP and that the free trial period is for 30 days, the consultant can effectively plan and execute the initial phases of the project.

References:

Salesforce.org Trial Experiences Information

Salesforce Nonprofit Success Pack (NPSP) Documentation

In the Nonprofit Success Pack (NPSP), managing various relationships such as siblings, deceased, and divorced spouses involves using the Relationship object. This object is specifically designed to track and manage the different types of personal relationships between Contacts.

Relationships in NPSP:

The Relationship object allows you to define and track various types of personal connections between Contacts.

This includes familial relationships such as siblings, as well as marital statuses such as deceased and divorced spouses.

Adding Relationships Manually:

Navigate to the Contact record where you want to add a relationship.

In the Relationships related list, click "New Relationship."

Fill out the necessary fields, including the Related Contact and the Relationship Type (e.g., Sibling, Deceased Spouse, Divorced Spouse).

Save the relationship record.

Why Manual Entry:

Manual entry ensures accuracy and allows customization for each specific relationship.

Automated or bulk processes might not accurately capture the nuances of each relationship type.

Use Cases:

For siblings, you would manually create a Relationship record linking the two sibling Contacts.

For deceased or divorced spouses, create a Relationship record and select the appropriate relationship type to reflect the status.

Benefits:

Provides a clear and structured way to manage complex personal relationships.

Enhances reporting and analysis of donor and constituent relationships.

References:

CertGod Nonprofit Cloud Consultant study guide: "Add them as Relationship entries manually"​​.

To automatically generate an Opportunity whenever a Lead is converted in NPSP, the consultant should enable the "Create an Opportunity on Lead Convert" option in the NPSP Settings. This option ensures that an Opportunity is automatically created as part of the lead conversion process.

Navigate to NPSP Settings:

Go to the App Launcher, search for "NPSP Settings", and select it.

Enable Lead Conversion Setting:

In NPSP Settings, expand the "Leads" section.

Find the "Lead Conversion" settings.

Check the box for "Create an Opportunity on Lead Convert".

Save the settings.

This configuration streamlines the process, ensuring that Opportunities are consistently created during lead conversion, without requiring additional custom code or third-party applications.

References:

CertGod Nonprofit Cloud Consultant Guide:

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

Salesforce.org recommends using the Affiliations object to address the complexity of tracking donors who have relationships with many different Accounts. The Affiliations object is designed to manage and represent the various roles and relationships that a Contact can have with multiple Accounts. This is especially useful for non-profit organizations that need to track complex and multifaceted relationships between donors and organizations.

Understanding Affiliations in NPSP:

Affiliations are used to track the various roles a Contact has with different Accounts.

Each Affiliation record links a Contact to an Account, along with a Role and a Status.

This allows organizations to manage and report on the different ways Contacts are connected to multiple Accounts.

Setting Up Affiliations:

In NPSP (Nonprofit Success Pack), navigate to the App Launcher and select "NPSP Settings."

Under the Affiliations section, you can configure different settings related to Affiliations, such as default role values and Affiliation mappings.

Creating and Managing Affiliations:

When creating a new Contact or updating an existing one, you can add Affiliation records to link the Contact to various Accounts.

Navigate to the Contact's detail page, and in the Affiliations related list, click "New Affiliation."

Fill out the required fields such as Account, Role, and Status, then save the record.

Using Affiliations for Reporting:

Affiliations can be included in reports to analyze the relationships Contacts have with multiple Accounts.

For example, you can create a report to show all Contacts and their respective roles in various organizations, which helps in understanding the network and influence of donors.

Benefits of Using Affiliations:

It provides a structured way to manage complex donor relationships.

Enhances reporting capabilities by allowing detailed analysis of donor connections.

Improves data accuracy by avoiding duplicate records and ensuring each Contact's relationships are properly tracked.

References:

CertGod Nonprofit Cloud Consultant study guide: "Which Salesforce object does Saleforce.org recommend using to address this complexity?" ​​

Salesforce Nonprofit Success Pack documentation on Affiliations: "Manage and represent the various roles and relationships that a Contact can have with multiple Accounts."

For a nonprofit organization providing case management and requiring automatic scoring of clients based on various factors like age, income, and health conditions, along with automating the creation and assignment of follow-up tasks, the best combination of functions is Engagement Plans and Levels.

Engagement Plans: These are used to automate the creation of tasks and follow-up activities based on predefined templates. This feature ensures that specific tasks are generated and assigned to relevant staff members as soon as certain criteria are met.

Steps to Set Up Engagement Plans:

Navigate to the "Engagement Plans" tab in NPSP.

Create a new Engagement Plan Template, defining the tasks and follow-ups that should be created.

Specify the conditions under which this Engagement Plan should be triggered (e.g., a new client intake).

Assign the Engagement Plan to the appropriate client records.

Levels: These are used to categorize clients (or any other records) based on numeric values or other criteria. In this case, Levels can be used to automatically assign a score to each client based on their age, income, and health conditions.

Steps to Set Up Levels:

Navigate to NPSP Settings > Levels.

Create a new Level, specifying the criteria for each level (e.g., age range, income bracket, number of health conditions).

Define the actions that should be triggered when a client reaches a specific level.

By using Engagement Plans and Levels, the nonprofit can automate both the scoring of clients and the creation of follow-up tasks, ensuring a streamlined case management process.

References:

CertGod Nonprofit Cloud Consultant Guide:

To track nested campaigns effectively, Salesforce Campaign Hierarchies can be utilized. Here are the steps to set this up:

Create Parent Campaign:

Create the top-level parent Campaign called "Friends of the Organization".

Create Sub-Campaigns:

Create sub-campaigns under the parent campaign for each hierarchical level: FY19, Capital Campaign, Annual Fund, Digital Donations, and Mobile.

Link each sub-campaign to its parent campaign using the Parent Campaign lookup field.

Configure Campaign Hierarchy Settings:

Ensure the Campaign Hierarchy settings are configured to allow for the desired depth of nested campaigns.

Track Campaign Performance:

Use Campaign Hierarchy reports to track the performance of each campaign within the hierarchy.

Analyze metrics such as total donations, engagement, and conversion rates at each level.

By creating a structured Campaign Hierarchy, the nonprofit can effectively track and manage complex campaign structures, gaining insights into performance at each level of the hierarchy.

References:

"Campaign Hierarchies" from Salesforce Help: Campaign Hierarchies

"Managing Campaigns in NPSP" from Salesforce.org: Campaign Management

Before upgrading from version 2 to version 3 of NPSP, the consultant should:

Run NPSP Health Check: This tool identifies potential issues in the current NPSP configuration, including deprecated fields, custom objects, and other configurations that might cause problems during the upgrade.

Running NPSP Health Check ensures that the upgrade process goes smoothly by addressing any issues beforehand.

References:

Salesforce Nonprofit Success Pack Documentation

Salesforce Trailhead: Upgrading NPSP

Creating a Campaign hierarchy is the most effective way to track funding for projects and monitor year-over-year goals in Salesforce. Campaign hierarchies allow for organizing campaigns in a structured manner, making it easy to roll up data and track progress across different levels. Here’s how to set this up:

Create Parent Campaigns for Years:

For each year, create a parent campaign. For example, "2023 Projects" and "2024 Projects".

Create Sub-Campaigns for Projects:

Under each yearly parent campaign, create sub-campaigns for each project. For instance, "2023 Projects" can have sub-campaigns like "Project A", "Project B", etc.

Link Sub-Campaigns to Parent Campaigns:

Use the Parent Campaign lookup field to link each project campaign to its respective year campaign. This establishes the hierarchy.

Track Goals and Progress:

Use Campaign fields to set goals and track actual amounts. Fields like "Campaign Member Status", "Amount Raised", and custom fields can be used to track the funding and progress.

Use roll-up summary fields to aggregate data from sub-campaigns to parent campaigns.

Reporting and Dashboards:

Create reports and dashboards to monitor the progress of each project and year-over-year comparisons. Use the Campaign Hierarchy feature in reports to show aggregated data.

By setting up a Campaign hierarchy, the foundation can easily track the funding, manage goals, and compare progress year-over-year.

References:

"Campaign Hierarchies" from Salesforce Help: Campaign Hierarchies

"Managing Campaigns in NPSP" from Salesforce.org: Managing Campaigns

To allow volunteers to log their own hours in Volunteers for Salesforce, the consultant should propose setting up the Volunteers Personal Site or adding a Log Volunteer Hours section on the nonprofit’s website.

Volunteers Personal Site:

This site allows volunteers to log in and manage their hours directly within Salesforce.

Steps to Set Up:

Navigate to Setup > Sites.

Create a new site and configure it to use the Volunteers for Salesforce functionality.

Add the Volunteers Personal Site tab and configure the permissions.

Direct volunteers to use this site to log their hours.

Log Volunteer Hours Section on Website:

Create a section on the nonprofit’s website where volunteers can log their hours.

Steps to Set Up:

Design a web form that captures the volunteer's job or shift and the hours worked.

Use Salesforce Web-to-Case or Web-to-Lead to capture this data and create records in Salesforce.

Direct volunteers to this section to submit their hours.

Both solutions provide a user-friendly way for volunteers to log their hours without requiring manual entry by staff.

To track various funds and report on restricted donations, General Accounting Units (GAUs) in NPSP should be used. Here’s a step-by-step guide:

Set Up General Accounting Units (GAUs):

Navigate to the App Launcher and search for "General Accounting Units".

Create GAUs:

Create new GAU records for each fund you need to track.

Provide names and descriptions that clearly identify each fund.

Link GAUs to Donations:

When creating or updating an Opportunity (donation), scroll to the GAU Allocations section.

Allocate the donation amount to the relevant GAU(s). This ensures that each donation is correctly attributed to the specific fund.

Run Reports on GAU Allocations:

Create reports that include GAU Allocation data to see how funds are being utilized and to ensure that restricted donations are tracked correctly.

Automate Allocations (Optional):

Use NPSP settings to define default GAU allocations for specific types of donations to automate this process.

By using GAUs, the nonprofit can effectively manage and report on restricted funds, ensuring compliance and transparency.

References:

Salesforce NPSP Documentation: General Accounting Units (GAUs)

Salesforce Trailhead: Nonprofit Success Pack (NPSP) Overview

For a nonprofit organization needing an email marketing tool to measure email engagement and evaluate prospective supporters:

Pardot Grading: This measures how well a prospect fits the ideal customer profile based on criteria such as job title, industry, and location.

Pardot Scoring: This tracks a prospect’s engagement with marketing materials, assigning points based on interactions such as email opens, clicks, and form submissions.

Combining Pardot Grading and Scoring provides a comprehensive view of both the quality and engagement level of prospective supporters.

References:

Salesforce Pardot Documentation

Salesforce Trailhead: Pardot Scoring and Grading

To track the high school a student attended and their college enrollment, the consultant should recommend using the NPSP Affiliations objects:

NPSP Affiliations: This object is designed to connect Contacts to Accounts representing institutions like high schools and colleges.

Status Field: Use the Status field within the Affiliations object to indicate if the student is currently enrolled or a former student.

This approach allows the nonprofit to maintain a detailed history of the student's educational journey and easily track changes in their enrollment status.

References:

Salesforce Nonprofit Success Pack Documentation

Salesforce Trailhead: Affiliations and Relationships in NPSP

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.

References:

Salesforce Documentation: Monitor Setup Changes

Salesforce Trailhead: Monitor Changes in Your Org

To load 45,000 records into Salesforce from a single flat file:

Data Loader: This tool is designed for bulk data import and export, handling large volumes of records efficiently. It supports complex data mappings and transformations required for importing donor, donation, and payment processing records.

Large Volume Handling: Data Loader can process up to millions of records, making it suitable for the task at hand.

Using Data Loader ensures that the records are imported accurately and efficiently, with the ability to handle data transformations as needed.

References:

Salesforce Data Loader Documentation

Salesforce Trailhead: Data Management Tools

Establishing a Center of Excellence (CoE) addresses the governance function of the application development lifecycle. A CoE provides leadership, best practices, and oversight to ensure consistent and effective use of Salesforce across the organization:

Governance: Ensures that there are clear policies, standards, and guidelines for managing and using Salesforce.

Best Practices: The CoE promotes best practices for development, deployment, and ongoing management of Salesforce applications.

By focusing on governance, a CoE helps maintain the integrity, quality, and strategic alignment of Salesforce initiatives within the nonprofit.

References:

Salesforce Governance Framework Documentation

Salesforce Trailhead: Center of Excellence

To enhance the security of Salesforce usernames and passwords and prevent them from being compromised, setting up two-factor authentication (2FA) is the recommended approach. Here’s how to implement it:

Enable Two-Factor Authentication for the Org:

Navigate to Setup.

In the Quick Find box, type "Two-Factor Authentication" and select it.

Enable 2FA at the organization level.

Assign 2FA to User Profiles:

Go to the user profiles that require 2FA.

Under the profile settings, enable the requirement for two-factor authentication.

Configure 2FA Methods:

Allow users to register their preferred authentication method (e.g., Salesforce Authenticator app, SMS, email, or third-party authenticator apps).

Ensure users set up their 2FA methods through their personal settings.

User Training and Support:

Provide training materials and support to help users understand and set up 2FA.

Offer assistance for troubleshooting common issues during the setup process.

Monitor and Enforce:

Use Salesforce’s monitoring tools to ensure compliance with 2FA requirements.

Regularly review and update security policies to maintain a high level of security.

Implementing two-factor authentication significantly reduces the risk of account compromise by adding an extra layer of security beyond just usernames and passwords.

References:

"Setting Up Two-Factor Authentication" from Salesforce Help: Two-Factor Authentication

"Salesforce Authenticator" from Salesforce Help: Salesforce Authenticator

When migrating a large volume of contacts, organizations, and address records into NPSP, it is essential to consider the following:

Complexity with the Address Object:

Using the Address object to track addresses can introduce complexity, especially if multiple addresses per contact or organization need to be managed. This complexity arises from the need to ensure all address records are correctly linked and maintained.

Impact on Data Storage:

Migrating all historical address information can significantly impact system data storage. Salesforce has storage limits, and large volumes of data can quickly consume available storage. It is important to plan for data storage needs and consider archiving or summarizing historical data to manage storage usage effectively.

Steps for Migration:

Data Preparation:

Clean and standardize the data before migration to ensure consistency.

Identify and remove duplicates to avoid data redundancy.

Data Mapping:

Map the fields from the legacy system to the corresponding fields in NPSP, including custom fields if necessary.

Data Import Tools:

Use Salesforce Data Loader or the NPSP Data Importer for the migration process.

Import data in batches, starting with Accounts, followed by Contacts, and then address information.

Testing and Validation:

Test the migration in a sandbox environment to identify and resolve any issues.

Validate the imported data to ensure accuracy and completeness.

References:

"Data Import Strategies for Nonprofits" from Salesforce Help: Data Import Strategies

"Address Management in NPSP" from Salesforce.org: Address Management

To locate NPSP release information, two key places are:

Power of Us Hub: This is a community for Salesforce.org customers, where they can access release notes, documentation, and discussions about NPSP updates.

GitHub Cumulus Releases: This repository contains detailed release information, including new features, bug fixes, and enhancements for NPSP.

These sources provide comprehensive and up-to-date information on NPSP releases.

References:

Power of Us Hub

GitHub Cumulus Releases Repository

To determine if an acknowledgment letter was sent for a donation, the best approach is to check the "Acknowledgement Status" picklist value on the Opportunity object. Here's how you can do it:

Navigate to the Opportunity Object:

Go to the App Launcher and find Opportunities.

Add the Acknowledgement Status Field:

Ensure that the "Acknowledgement Status" field is included in the Opportunity page layout.

Navigate to Setup.

In the Object Manager, select Opportunity.

Go to Page Layouts and add the "Acknowledgement Status" field to the relevant layout if it is not already there.

Review the Acknowledgement Status:

Open the Opportunity record for the donation in question.

Look for the "Acknowledgement Status" field to see if it indicates that the acknowledgment letter has been sent.

Automate Tracking (Optional):

Use workflows or Process Builder to update the "Acknowledgement Status" automatically when certain conditions are met, such as when a task related to sending an acknowledgment letter is marked complete.

References:

Salesforce Nonprofit Success Pack (NPSP) Documentation: Managing Acknowledgments

Salesforce Trailhead: Opportunities and Donations

Using Case Hierarchy is the best way to relate Cases for the same client to each other in Salesforce. This allows the organization to see the connection between various Cases and manage them effectively. Here’s how to set it up:

Enable Case Hierarchy:

Ensure that the Case Hierarchy feature is enabled in your Salesforce org. This is typically enabled by default.

Create Parent and Child Cases:

When creating or editing a Case, you can specify a parent Case using the "Parent Case" lookup field.

For each new Case related to the same client, select the main Case as the parent.

View Case Hierarchy:

On the Case record page, click on "View Hierarchy" to see all related Cases in a hierarchical view.

This allows you to easily track and manage all Cases related to a specific client.

By using Case Hierarchy, you can maintain a clear structure of all Cases related to a client and ensure they are appropriately connected and managed.

References:

"Case Hierarchies" from Salesforce Help: Case Hierarchies

"Managing Cases in NPSP" from Salesforce.org: Case Management

When a nonprofit organization creates a custom Opportunity name for all organization donations, the consultant should discuss the following considerations:

Using the "Refresh Name" Action (B):

The organization should use the "Refresh Name" action to change existing Opportunities to the new naming convention. This action ensures that the custom naming convention is applied correctly.

Navigate to the Opportunity record.

Click on the "Refresh Name" button to update the Opportunity name according to the new naming convention.

Using the "Refresh All Opportunity Names" Button in Bulk Data Processes (C):

For bulk updates, the organization should use the "Refresh All Opportunity Names" button available in Bulk Data Processes.

Go to NPSP Settings.

Under Bulk Data Processes, find the "Refresh All Opportunity Names" button.

Click on it to update all existing Opportunities to the new naming convention in bulk.

These methods ensure that the custom naming convention is applied consistently across all existing Opportunity records, maintaining data integrity and consistency within the Salesforce org​​.

To avoid manually entering information twice and ensure it appears on both the Opportunity record and the Payment record, follow these steps:

Create Payment Mappings in NPSP Settings:

Navigate to NPSP Settings.

Go to "Donations" and select "Payment Mappings".

Create mappings to ensure that relevant fields from the Opportunity record are automatically populated in the Payment record.

Create Custom Fields on the Payment Object:

Navigate to Setup.

In the Object Manager, select "Payment".

Click on "Fields & Relationships".

Create custom fields that correspond to the Opportunity fields you want to map.

Ensure the field types match those on the Opportunity object to facilitate accurate data transfer.

These steps automate the data transfer between Opportunities and Payments, reducing manual entry and ensuring consistency across records.

References:

Salesforce NPSP Documentation: Payment Mappings

Salesforce Trailhead: Custom Fields

When using the NPSP Data Importer for Contacts, if some Account records are not being automatically created, the consultant should check:

Required Fields in the Import: Ensure that all required fields for creating an Account are included in the data import file. Missing required fields can prevent Account creation.

Required Fields on the Account: Verify that the Account object does not have custom required fields that are not being populated by the import process. Custom fields marked as required at the field level or in page layouts can block record creation if not provided.

Checking these factors ensures that the import process has all the necessary information to create Account records successfully.

References:

Salesforce Nonprofit Success Pack Documentation

Salesforce Trailhead: Importing Data with NPSP Data Importer

When finalizing the plan for new features during a Salesforce major seasonal release window:

Verify Sandbox Release:

Check if the sandbox is on the same release as production to ensure consistency. Navigate to Setup -> Company Information in both environments to verify the release versions.

Review Sandbox Preview Instructions:

Salesforce provides sandbox preview instructions before a major release. Review these instructions to understand the new features and changes. Go to the Salesforce Release Readiness & Feature Adoption group on the Trailblazer Community for the latest updates.

Prepare Change Sets:

Create and validate change sets in the sandbox environment. Ensure all components are tested and ready for deployment after the production instance is upgraded.

Monitor Release Window:

Keep track of the Salesforce release window schedule to plan the deployment timing accordingly. Avoid deploying changes during the release window to prevent conflicts or unexpected issues.

References:

Salesforce Release Readiness & Feature Adoption Documentation

Salesforce Sandbox Preview Instructions

Salesforce Trailblazer Community for Release Updates

To ensure information appears on both the Opportunity and Payment records without entering it twice, the following steps should be taken:

Create Custom Fields on the Payment Object:

Identify the fields that need to be shared between the Opportunity and Payment records.

Go to the Payment object in Salesforce and create custom fields that match those on the Opportunity object.

Create Payment Mappings in NPSP Settings:

Navigate to NPSP Settings.

Go to the “Donations” section and find “Payment Mappings.”

Set up mappings to link Opportunity fields to the corresponding Payment fields.

This ensures that when an Opportunity is created or updated, the relevant data is automatically copied to the Payment record.

By creating custom fields and setting up payment mappings, the required information will be synchronized between Opportunity and Payment records, eliminating the need for duplicate data entry.

References:

Salesforce Nonprofit Success Pack (NPSP) documentation on Payment Mappings

CertGod Nonprofit Cloud Consultant guide​

https://trailhead.salesforce.com/content/learn/modules/program-management-with-nonprofit-cloud/manage-nonprofit-programs-with-salesforce

To track each program and the status of youth enrolled in the program using the Program Management Module (PMM) in Salesforce, the consultant should use the "Programs" and "Program Engagements" objects.

Key Features:

Programs: This object represents the various programs offered by the nonprofit. Each program can have multiple engagements and activities associated with it.

Program Engagements: This object tracks the involvement of individuals (youth in this case) in specific programs. It allows the nonprofit to monitor the status and progress of each participant within the program.

Steps to Implement:

Set Up Programs:

Navigate to the Programs tab.

Create records for each after-school program offered by the nonprofit.

Track Engagements:

Navigate to the Program Engagements tab.

Create records for each youth enrolled in the programs, linking them to the appropriate program and tracking their status.

References:

Salesforce Program Management Module Documentation

Salesforce Trailhead: Program Management for Nonprofits

To ensure that a deceased donor no longer appears on any mailing lists, the appropriate action is to select the Deceased field on the donor's Contact record.

Deceased Field:

Salesforce provides a specific field to mark a Contact as deceased.

This field is designed to handle the scenario of deceased Contacts appropriately within the system.

Steps to Mark Contact as Deceased:

Navigate to the Contact record of the deceased donor.

Find the Deceased checkbox field and select it.

Save the record.

Impact of Selecting the Deceased Field:

Once marked as deceased, the Contact will automatically be excluded from future mailing lists and communications.

This helps maintain respectful and accurate communication practices.

Other Considerations:

Do Not Email, Do Not Contact, and Email Opt Out Fields: While these fields prevent specific types of communications, they do not address the status of the Contact as being deceased, which is important for accurate records and reporting.

Deleting Contact Record: Deleting the Contact record is not recommended as it removes historical donation data and other important information that may be needed for reporting and compliance purposes.

References:

CertGod Nonprofit Cloud Consultant study guide: "Select the Deceased field"【22:2†source】.

To provide each affiliate and the national nonprofit the ability to see only its own donor data in a single Salesforce org, the consultant should use Criteria-based Sharing. Here's why:

Criteria-based Sharing:

This feature allows for defining sharing rules based on specific criteria, such as record ownership or certain field values.

By setting up criteria-based sharing rules, each affiliate and the national nonprofit can be restricted to viewing only the records that meet the specified criteria, such as records tagged with their specific region or affiliate identifier.

References:

Salesforce Sharing and Visibility Guide

Salesforce Criteria-based Sharing Rules Documentation

To help a nonprofit run a large scholarship program using Salesforce for accepting external scholarship applications, reviewing processes, and tracking requirements, the following solutions are recommended:

Experience Cloud:

Experience Cloud allows the nonprofit to create a community or portal where external applicants can submit their scholarship applications.

It provides a user-friendly interface for applicants and reviewers to interact with the application process.

Steps to Implement Experience Cloud:

Set up an Experience Cloud site and customize it to match the nonprofit’s branding.

Create forms and pages for application submission.

Enable user roles and permissions to control access for applicants and reviewers.

Outbound Funds Module:

The Outbound Funds Module (OFM) is specifically designed to manage the distribution of funds, such as scholarships.

It allows for tracking applications, managing review processes, and ensuring compliance with scholarship requirements.

Steps to Implement Outbound Funds Module:

Install and configure the Outbound Funds Module from the AppExchange.

Set up funding programs, grant types, and application criteria.

Use OFM’s built-in features to manage the review and approval workflows.

These solutions provide a comprehensive and integrated approach to managing the scholarship program within Salesforce.

References:

Salesforce Experience Cloud Documentation

Salesforce AppExchange: Outbound Funds Module

Nonprofit Success Pack (NPSP) Documentation

To protect data and secure login credentials for external systems, the consultant should recommend using Named Credentials. Named Credentials simplify the management of authentication for external systems by storing login credentials securely within Salesforce. This approach reduces the risk of exposed credentials and ensures that data remains protected even if an employee is terminated.

Steps:

Configure Named Credentials in Salesforce for each external system.

Store the authentication details securely within Salesforce.

Use Named Credentials in Apex code and integrations to access external systems.

Regularly review and update Named Credentials as needed to maintain security.

References:

CertGod Nonprofit Cloud Consultant Guide: Discusses the use of Named Credentials for securing access to external systems​​.

Salesforce Documentation on Named Credentials: Provides setup and usage instructions.

For tracking and reviewing scholarship applications and recording scholarship recipients, award amounts, and dates, the consultant should recommend setting up the Outbound Funds Module. This module is designed for managing funds that are disbursed, such as grants and scholarships. By connecting the Funding Request to Contacts for the recipient, the nonprofit can effectively manage and track all related information in a structured and organized manner.

References:

Salesforce Outbound Funds Module Documentation

Salesforce Nonprofit Cloud Consultant Study Guide

To present active volunteer sites on a map that should be visible without logging in, the nonprofit can use Tableau Public. Here’s why:

Tableau Public:

Tableau Public is a free platform that allows users to create and share interactive data visualizations online.

It supports publishing maps and other visualizations that can be accessed publicly without requiring login credentials.

This tool is ideal for sharing information like volunteer site locations with a broad audience.

References:

Tableau Public Documentation

Salesforce and Tableau Integration Guide

https://powerofus.force.com/s/article/NPSP-Configure-Automated-Soft-Credits#ariaid-title6

To automatically credit the spouse for a donation in NPSP, the consultant should recommend enabling Automatic Soft Credit for household members in the NPSP settings. This setting ensures that any donation made by a household member is automatically soft credited to other members of the household.

Steps to Enable:

Navigate to NPSP Settings:

Go to Setup -> NPSP Settings.

Enable Automatic Soft Credits:

Under Donations -> Soft Credits, enable the option for Automatic Soft Credit for Household Members.

Verify Soft Credits:

Check the Opportunity records to ensure that soft credits are correctly applied to household members.

References:

Salesforce Nonprofit Success Pack Documentation

Salesforce Trailhead: Manage Soft Credits in Nonprofit Success Pack (NPSP)

Top of Form

Bottom of Form

https://trailhead.salesforce.com/content/learn/modules/project-risk-management-for-partners/identify-ass ess-address-risk

In project management, the three elements impacted by change that cause risk are cost, quality, and time. These elements are often referred to as the project management triangle or triple constraint.

Elements Impacted by Change:

Cost: Changes can lead to increased project costs, affecting the budget and financial resources.

Quality: Changes can impact the quality of the project deliverables, potentially leading to rework or reduced standards.

Time: Changes can affect the project timeline, causing delays and extending the project schedule.

Steps for Risk Mitigation:

Identify Potential Risks:

Conduct a risk assessment to identify potential changes that could impact cost, quality, or time.

Develop Mitigation Strategies:

Create plans to mitigate identified risks, including contingency plans and resource allocations.

Monitor and Control:

Regularly monitor the project for changes and adjust plans as necessary to manage risks effectively.

References:

Salesforce Project Management Best Practices

Salesforce Trailhead: Risk Management in Project Management

When loading a large volume of data, such as 5 million donation history records, into Salesforce, it is essential to temporarily disable TDTM (Trigger Handler Framework) to ensure the data load is successful. TDTM triggers can slow down or interrupt the data load process due to the large volume of records being processed.

Steps:

Go to Setup > Custom Metadata Types.

Select "Trigger Handlers."

For each trigger handler, uncheck the "Active" checkbox to temporarily disable it.

Perform the data load using Data Loader or another data import tool.

Once the data load is complete, re-enable the TDTM Trigger Handlers by checking the "Active" checkbox for each trigger handler.

References:

CertGod Nonprofit Cloud Consultant Guide: Advises on the importance of managing TDTM triggers during large data loads​​.

Salesforce Documentation on TDTM: Provides instructions on managing and disabling TDTM triggers.

To ensure that Person Accounts and NPSP can coexist within the same Salesforce org, follow these configurations:

Different Household Record Type in NPSP Settings:

Navigate to NPSP Settings.

Ensure that the Household record type specified in NPSP settings is different from the Person Account record type.

This prevents conflicts and ensures that NPSP correctly distinguishes between Household Accounts and Person Accounts.

Default Record Type for Profiles of Users Converting Leads:

Go to Setup > Profiles.

Ensure that the default record type for any profiles of users who convert leads is not set to the Person Account record type.

This ensures that when leads are converted, they do not automatically become Person Accounts, which could disrupt the NPSP data model.

By following these configurations, the nonprofit can effectively manage both Person Accounts and NPSP functionalities within the same Salesforce environment.

References:

Salesforce NPSP Documentation: NPSP Configuration.

Salesforce Person Accounts Guide: Person Accounts.

To ensure the campaign for monthly project updates to donors who have given 10 or more times stays current, the consultant should:

Create a Contact Report:

Create a report on the Contact object and include a filter to display only those contacts whose total number of gifts meets the criteria (10 or more).

This filter ensures that only the relevant donors are included in the report.

Run the Report Monthly:

Schedule or manually run the report each month to get the updated list of donors.

Use the "Add to Campaign" button to add the contacts from the report to the newsletter campaign, ensuring the campaign list stays current with donors who meet the criteria.

References:

Salesforce Reporting Guide

Salesforce Campaign Management Guide

https://trailhead.salesforce.com/en/content/learn/modules/salesforce-data-mask/understand-the-importance-of-data-privacy

Salesforce Data Mask is the recommended solution to ensure the contractor is unable to access sensitive data in a full copy sandbox. Data Mask is designed to secure sensitive data in sandboxes by masking or obfuscating it, thereby preventing unauthorized access.

Salesforce Data Mask Overview:

Salesforce Data Mask allows you to obfuscate sensitive data in sandboxes, ensuring that real data is not exposed.

It provides various masking options, including anonymization, pseudonymization, and deletion.

Implementation Steps:

Install Salesforce Data Mask from the Salesforce AppExchange.

Configure the masking rules for the fields that contain sensitive information. You can choose the appropriate masking technique based on your needs (e.g., random characters, fixed characters, or deletion).

Apply the masking rules to the full copy sandbox where the contractor will be working.

Benefits of Using Data Mask:

Security: Ensures sensitive data is not exposed in non-production environments.

Compliance: Helps meet regulatory and compliance requirements by protecting personal and personally identifiable information.

Flexibility: Allows you to define specific rules for different types of data and fields.

References:

CertGod Nonprofit Cloud Consultant study guide: "Implement Salesforce Data Mask and mask the sensitive data"​​.

To collect information online about new volunteers, including names, contact details, skill sets, and availability, and create a report with this information, the following solutions are recommended:

Collect Contact Information During Job Sign Up:

Use the Job Listings feature in Volunteers for Salesforce to capture volunteer information during the job sign-up process.

Ensure that the sign-up form includes fields for contact details, skill sets, and availability.

Steps to Set Up Job Listings:

Navigate to the Volunteers for Salesforce setup.

Configure job listings and ensure the sign-up forms capture all necessary information.

Add the Volunteer Sign Up Form to the Nonprofit's Website:

Create a Volunteer Sign Up form and embed it on the nonprofit’s website.

Use the Volunteers for Salesforce Web-to-Volunteer feature to automatically capture and create records in Salesforce.

Steps to Set Up Web-to-Volunteer:

Go to Volunteers for Salesforce settings.

Set up the Web-to-Volunteer form with the required fields.

Embed the form on the nonprofit’s website.

These methods ensure that all relevant volunteer information is captured and stored in Salesforce, allowing for easy reporting and management.

References:

Volunteers for Salesforce Documentation

Salesforce Help: Setting Up Web-to-Volunteer Forms

Top of Form

Bottom of Form

To track all donations that go to a designated fund, the consultant should create a GAU Allocation record for the designated fund. Here’s why:

GAU Allocation Record:

General Accounting Units (GAUs) are used in NPSP to allocate portions of donations to specific funds or purposes.

Creating a GAU Allocation record allows the nonprofit to specify the amount of each donation that should be allocated to the designated fund, ensuring accurate tracking and reporting.

References:

Salesforce NPSP Documentation on General Accounting Units (GAUs)

Salesforce Nonprofit Success Pack GAU Allocation Guide

When the consultant encounters API call limit errors after switching the integration from a sandbox to a production environment, the likely explanation is:

Different API Call Limits for Sandbox and Production Environments:

Salesforce environments have different API call limits based on the type of environment and the organization's Salesforce edition. Sandbox environments often have higher API call limits for testing purposes, while production environments have stricter limits to ensure performance and reliability.

To track a check that includes donations from several donors for a specific program, the consultant should configure GAU Allocations and Partial Soft Credits in NPSP. Here’s why:

GAU Allocations:

General Accounting Unit (GAU) Allocations are used to track how donations are allocated across different programs or funds.

This feature allows the nonprofit to specify which portion of the check is designated for the specific program, providing clear tracking and reporting.

Partial Soft Credits:

Partial Soft Credits can be used to attribute portions of a single donation to multiple donors.

This feature allows the nonprofit to recognize each donor for their contribution while keeping the accounting of the total donation intact.

References:

Salesforce NPSP Documentation on GAU Allocations

Salesforce NPSP Documentation on Soft Credits

https://powero fus.force.com/s/article/NPSP-Configure-Gift-Entry

Gift Entry Templates in NPSP allow for the configuration of different batch data input settings for various types of donations. This feature ensures consistency and efficiency in processing different donation batches.

Steps:

Access the Gift Entry Templates in NPSP.

Create a new template for each type of donation batch that needs to be processed.

Configure the fields and layout for each template to match the specific data requirements of each donation type.

Save and publish the templates.

Use the templates when processing donation batches to ensure consistent data entry and processing.

References:

CertGod Nonprofit Cloud Consultant Guide: Recommends using Gift Entry Templates for managing different donation types and ensuring consistent data processing​​.

Salesforce Documentation on Gift Entry Templates: Provides detailed instructions on creating and using Gift Entry Templates in NPSP.

Both Marketing Cloud and Pardot offer the capability to segment data and functionality using business units. This is particularly useful for large nonprofits with multiple chapters operating under a single brand but needing customized roles, processes, and messaging.

Marketing Cloud:

Business Units: Allows organizations to separate data, user permissions, and content based on different parts of the organization, such as chapters or departments. Each business unit can have its own data and customizations, enabling localized marketing while maintaining centralized control.

Pardot:

Business Units: Pardot Business Units enable marketing teams to partition data and customize marketing efforts for different segments within the organization. This ensures that each chapter can tailor its marketing automation processes to its specific needs while maintaining brand consistency.

References:

Salesforce Marketing Cloud Documentation

Salesforce Pardot Documentation

Salesforce Trailhead: Get Started with Marketing Cloud Business Units

For a data migration involving tens of millions of records to NPSP over a weekend, the Bulk API is recommended due to its ability to handle large volumes of data efficiently:

Prepare Data for Migration:

Ensure all data is cleaned and formatted correctly for import into Salesforce.

Segment the data into manageable batches to optimize the migration process.

Use Bulk API for Migration:

The Bulk API is designed for loading large data sets and operates asynchronously, allowing for high performance.

Create a Bulk API job to import the data.

Upload data batches and monitor the job status to ensure successful data import.

Minimize System Downtime:

Schedule the data migration to occur during a weekend to reduce the impact on users and minimize system downtime.

Inform stakeholders about the migration schedule and expected downtime.

Verify Data Integrity:

After the migration, run data integrity checks to ensure that all records have been accurately imported.

Compare source data with the imported data in Salesforce to verify completeness.

Using the Bulk API will ensure that the large volume of data is migrated efficiently within the limited timeframe, minimizing disruption to the organization’s operations.

References:

Salesforce documentation on using the Bulk API for data migration

CertGod Nonprofit Cloud Consultant guide​

To create a report that shows Opportunity and General Accounting Unit (GAU) custom field data for gifts to the "General Fund" GAU and adds filters to show only the gifts connected to the "Annual Campaign," the consultant should use the "GAU Allocations with Opportunity" report type. This report type allows for filtering on both Opportunity and GAU Allocation fields.

Steps to Create the Report:

Select Report Type:

Go to the Reports tab and create a new report using the "GAU Allocations with Opportunity" report type.

Add Filters:

Filter on the Opportunity object for the Primary Campaign Source = "Annual Campaign."

Filter on the GAU Allocation object for General Accounting Unit = "General Fund."

Customize Report:

Add the necessary fields from both the Opportunity and GAU Allocation objects to the report layout.

Save and run the report to view the desired data.

References:

Salesforce Nonprofit Success Pack Documentation

Salesforce Trailhead: Create and Customize Reports in Salesforce

To ensure that users only see Engagement Plans on Opportunity records for donations with an Amount greater than 10,000, the consultant should use component visibility filters in Lightning. Here’s the step-by-step process:

Add the Related List - Single Lightning Component:

On the Opportunity Lightning page, add the "Related List - Single" component and set it to display the Engagement Plans related list.

Component Visibility Filter:

Configure a visibility filter on the Related List component. Set the filter condition to check if the Opportunity Amount field is greater than 10,000.

This ensures that the Engagement Plans related list only appears on Opportunities where the amount exceeds the specified threshold.

References:

Salesforce Lightning App Builder Documentation

Salesforce Component Visibility Filters Guide

These solutions provide detailed steps and references to effectively configure and troubleshoot Salesforce Nonprofit Cloud settings and features.

To ensure that a deceased donor no longer appears on any mailing lists, the nonprofit organization should select the "Deceased" field on the donor's contact record. Here’s how to do it:

Navigate to the Contact Record:

Go to the Contacts tab in Salesforce.

Search for and open the donor’s contact record.

Select the Deceased Field:

Locate the "Deceased" checkbox on the contact record.

Check the box to mark the contact as deceased.

Verify Exclusion from Mailing Lists:

Ensure that automated workflows and processes exclude contacts marked as deceased from email and mailing lists.

Review and update any relevant segments or mailing lists to remove the deceased donor.

This action preserves the donor’s history in Salesforce while ensuring they are no longer included in future communications.

References:

Salesforce NPSP Documentation: Managing Contact Records

Salesforce Trailhead: Nonprofit Success Pack (NPSP) Basics

When a nonprofit creates a custom Opportunity Name for all in-kind gifts, it is important to understand how this change impacts existing and new Opportunity records. The Refresh All Opportunity Names utility can be used to update the names of existing Opportunities to match the new naming convention. Additionally, the custom Opportunity Name Format will only apply to new Opportunities that match the specified record type.

Steps:

Update the Opportunity Name Format settings to reflect the new naming convention for in-kind gifts.

Use the Refresh All Opportunity Names utility to apply the new naming convention to existing Opportunities. This ensures consistency across all records.

Inform users that the new naming convention will only be automatically applied to new Opportunities created with the matching record type going forward.

Monitor the changes and verify that the updated names meet the nonprofit's requirements.

References:

CertGod Nonprofit Cloud Consultant Guide: Provides guidance on updating Opportunity names and using utilities for bulk updates​​.

Salesforce Documentation on Opportunity Name Formats: Details the steps for configuring and applying custom naming conventions.

For a nonprofit that does a lot of mail appeals to donors and wants to ensure addresses are formatted correctly, the consultant should recommend:

NPSP Address Management:

NPSP Address Management helps ensure that addresses are standardized and formatted correctly. It includes tools and processes to manage and validate addresses, thus reducing errors in mailings and improving delivery rates.

To integrate wealth scoring information into Salesforce, the consultant should recommend using a third-party app from the AppExchange. Here’s the process:

Explore AppExchange:

Visit the Salesforce AppExchange.

Search for wealth scoring or donor prospecting applications.

Evaluate Apps:

Review the available apps that offer wealth scoring and donor analytics.

Evaluate the features, customer reviews, and integration capabilities of each app.

Select an App:

Choose an app that best fits the nonprofit’s requirements for wealth scoring integration.

Popular options include apps like WealthEngine, DonorSearch, or iWave.

Install and Configure the App:

Install the selected app into the Salesforce org.

Follow the configuration steps provided by the app to integrate wealth scoring data with Salesforce records.

Map Wealth Scores to Salesforce Fields:

Map the wealth scoring data fields to the appropriate fields on Salesforce objects, such as Contacts and Opportunities.

Ensure the data is displayed where it is most useful for development officers and other users.

By using a third-party app from the AppExchange, the nonprofit can seamlessly integrate comprehensive wealth scoring information into Salesforce, enhancing their donor prospecting and engagement strategies.

References:

Salesforce AppExchange: WealthEngine

Salesforce Documentation: Install Apps from AppExchange

https://developer.salesforce.com/forums/?id=9060G000000I7sYQAS ,and “D”.( When importing data into the NPSP Data Import Object, if the error message indicates that the Record ID field is not mapped, the system admin should ensure that the appropriate mapping is set up and use the correct operation for the data loader.

Select the Appropriate Record ID (A):

In the Salesforce Data Import Wizard, ensure that the Record ID field is correctly mapped. This field is required for updating existing records or ensuring data integrity.

Select "Upsert" Operation (C):

When using the Salesforce Data Loader, choose the "Upsert" operation. This allows the system to insert new records or update existing ones based on the Record ID or an external ID, ensuring that duplicates are avoided and data is accurately imported.

Steps to Resolve:

Check Field Mapping:

Verify that the Record ID field is mapped correctly in the import wizard or data loader.

Choose Upsert Operation:

If using the Data Loader, select the "Upsert" option to handle both insertions and updates.

References:

Salesforce Nonprofit Success Pack Documentation

Salesforce Trailhead: Import Data for Nonprofits

To quickly deploy a solution that provides insights into corporate sponsorships, including pipeline value, number of opportunities, Pardot score, win/loss percentage, stage value, and a table of opportunities, the consultant should recommend B28 Marketing Analytics. Here’s why:

B28 Marketing Analytics:

This analytics solution is designed to provide deep insights into marketing performance, including detailed views of pipeline metrics and opportunity analysis.

It integrates with Salesforce and Pardot, offering out-of-the-box dashboards and reports that can be quickly deployed.

The tool enables the nonprofit to gain actionable insights into why certain sponsorships are closing or being lost, facilitating data-driven decision-making.

References:

Salesforce B28 Marketing Analytics Documentation

Salesforce Pardot Integration Guide

To configure Accounting Subledger so that only the appropriate records are created and available for export to finance, you need to set up Stage to State Mapping. This ensures that only donations at a certain stage are included in the ledger entries. Here are the steps:

Access Accounting Subledger Setup:

Navigate to the Accounting Subledger settings in Salesforce.

Configure Stage to State Mapping:

Define the mapping between Opportunity Stages and Accounting Subledger States.

For example, map the "Closed Won" stage to a state that signifies the donation is ready for ledger entry creation.

Update Opportunity Stages:

Ensure that your Opportunity Stages are correctly set up to reflect the different states of your donation process (e.g., "Pledged", "Received").

Create Ledger Entries:

Once an Opportunity reaches the specified stage (e.g., "Closed Won"), a ledger entry is automatically created.

Only these ledger entries are included in the export to finance.

By configuring the Stage to State Mapping, you ensure that only finalized donations (those that reach a specific stage) are included in the ledger entries, making the finance export process more efficient and accurate.

References:

Salesforce Accounting Subledger Documentation: Stage to State Mapping.

To ensure full compliance with Salesforce best practices for data security, the consultant should use Salesforce Health Check. Here’s why:

Salesforce Health Check:

This tool provides a comprehensive security assessment of your Salesforce org by measuring its settings against the Salesforce recommended baseline.

It evaluates critical security settings such as password policies, session settings, and other security configurations.

Health Check provides a score and recommendations to improve the overall security posture of the org, making it a crucial tool for maintaining data security compliance.

References:

Salesforce Health Check Documentation

Salesforce Security Best Practices Guide

To allow a fundraiser to easily track and update her gift asks for donation solicitations, using Path is a suitable solution in Salesforce. Here’s how to configure and use Path for this requirement:

Enable Path:

Navigate to Setup and type "Path" in the Quick Find box.

Click on Path Settings and enable Path if it is not already enabled.

Create a Path:

Click New Path and follow the steps to create a new Path.

Select the Opportunity object since you want to track donation solicitations.

Define the stages of your solicitation process (e.g., Identification, Cultivation, Solicitation, Stewardship).

Configure Key Fields and Guidance:

For each stage, specify key fields that the fundraiser should complete.

Add guidance for success to provide tips and best practices for each stage.

Assign the Path to a Record Type:

If using record types, ensure the Path is assigned to the correct record type for your donation solicitations.

Use Path:

On the Opportunity record page, the fundraiser can now see the Path at the top of the record.

She can track her progress, update fields, and follow the guidance provided at each stage.

Using Path helps the fundraiser to visualize the stages of the solicitation process, ensuring she can track and update gift asks effectively.

References:

Salesforce Path Documentation: Path in Salesforce.

To provide real-time insights into membership data stored in a proprietary system, the nonprofit should use Salesforce Connect to store this information in External Objects:

Salesforce Connect:

Salesforce Connect allows Salesforce to integrate with external data sources in real-time without the need to import the data into Salesforce.

It uses External Objects to represent the data from the external system, making it accessible within Salesforce like any other object.

Implementing Salesforce Connect:

Set up an external data source connection in Salesforce to the proprietary membership management system.

Define External Objects for the membership data, such as member status, renewal dates, and other relevant data points.

Create relationships between External Objects and standard Salesforce objects (e.g., Contacts, Accounts) to link donor and membership information.

Real-Time Insights:

Use reports and dashboards to display membership data alongside fundraising and program data.

Ensure that membership data is updated in real-time, providing accurate and timely insights.

By utilizing Salesforce Connect and External Objects, the nonprofit can achieve real-time visibility into its membership data without duplicating data storage.

References:

Salesforce Connect Documentation

Trailhead Module: Integrate with External Data Sources Using Salesforce Connect

When migrating a large volume of contacts, accounts, and address records into NPSP, the following considerations are important:

Managing Multiple Addresses:

NPSP allows for multiple addresses per contact or account, which can introduce additional complexity in managing and maintaining these records.

It is essential to have a clear strategy for handling primary, mailing, and other types of addresses to ensure data consistency and accuracy.

Data Storage Consumption:

Each address record consumes additional data storage in Salesforce.

Nonprofits should be aware of their data storage limits and plan accordingly to avoid running out of storage space.

Consider archiving old or inactive address records to manage storage usage efficiently.

These considerations help ensure a smooth data migration process and ongoing data management within NPSP.

References:

Salesforce Help: Managing Addresses in NPSP

Nonprofit Success Pack (NPSP) Documentation: Data Management and Storage

When setting up the process for importing lists of Contacts into Salesforce Campaigns using the NPSP Data Import tool, it is essential to consider how Campaign Members are created and matched.

Key Considerations:

Automatic Campaign Member Creation (A):

The NPSP Data Import tool will automatically create Campaign Member records for the imported Contacts with the default Member Status. This helps streamline the process of adding members to campaigns.

Exact Name Matching (D):

Existing Campaigns in Salesforce are matched by exact Name. This means that the names in the CSV files must match the names of the Campaigns in Salesforce exactly for the import process to associate Contacts with the correct Campaigns.

Steps to Set Up:

Prepare CSV Files:

Ensure that the Campaign names in the CSV files exactly match the names of the Campaigns in Salesforce.

Include all necessary fields to map Contacts to Campaign Members.

Configure NPSP Data Import:

Navigate to NPSP Settings -> Data Import.

Ensure the settings align with the import requirements, including handling duplicates and respecting duplicate matching rules if enabled.

Perform Dry Run:

Use the NPSP Data Import Dry Run feature to validate the import configuration and ensure that the Campaign Member Status and other settings are correctly applied.

References:

Salesforce Nonprofit Success Pack Documentation

Salesforce Trailhead: Import Data for Nonprofits

Before converting from Legacy Recurring Donations to Enhanced Recurring Donations, nonprofits should consider several factors to ensure a smooth transition. Enhanced Recurring Donations offer improved functionality but may introduce compatibility issues with existing integrations. Additionally, once the switch is made, reverting to Legacy Recurring Donations is not supported, which means careful planning and testing are essential.

Steps:

Review all existing integrations to ensure compatibility with Enhanced Recurring Donations.

Conduct thorough testing in a sandbox environment to identify any potential issues.

Inform stakeholders that reverting to Legacy Recurring Donations is not supported once the switch is made.

Plan for a phased rollout and provide training to users on the new features and processes.

References:

CertGod Nonprofit Cloud Consultant Guide: Discusses considerations and steps for transitioning to Enhanced Recurring Donations​​.

Salesforce Nonprofit Success Pack (NPSP) Documentation: Details the features and limitations of Enhanced Recurring Donations.

For a nonprofit using direct mail extensively and needing to automate the search for duplicate contact records, the consultant should recommend implementing Duplicate Jobs. Here’s why:

Duplicate Jobs:

Duplicate Jobs allow organizations to run deduplication processes on a schedule, ensuring that the data remains clean and free from duplicates.

This feature can be configured to find and merge duplicate contacts based on predefined matching rules.

It helps maintain data quality by regularly identifying and managing duplicate records, which is essential for effective direct mail campaigns.

References:

Salesforce Duplicate Management Documentation

Salesforce Nonprofit Success Pack Duplicate Management Guide

The error message "the data you are trying to access is unavailable" when running a mailing list report on a campaign using the NPSP Household Mailing List button likely indicates a permissions issue. Since the button works as expected for the system administrator, the issue is probably related to user permissions.

Apex Class Access (A): The most likely cause is that the user does not have access to the necessary Apex Class for Manage Households. Ensure that the user has the required permissions to access and execute this Apex Class.

References:

Salesforce Nonprofit Success Pack Documentation

Salesforce Help: Manage Apex Classes and Permissions

The Program Management Module (PMM) in Salesforce is designed to help nonprofits manage their programs and services, including tracking participation in courses and training. PMM provides the necessary tools and features to capture and report on the various activities and outcomes associated with the programs run by the nonprofit.

Key Features:

Service Delivery Tracking: PMM allows for detailed tracking of services provided, including courses and training sessions.

Customizable Program Management: Nonprofits can configure PMM to meet their specific needs for managing programs and tracking participant engagement.

Steps to Implement PMM:

Install PMM:

Go to the Salesforce AppExchange and install the Program Management Module.

Set Up Programs and Services:

Define programs and related services within PMM to reflect the courses and training offerings.

Track Participation:

Use the PMM features to log and manage participant data, track attendance, and monitor outcomes.

References:

Salesforce Program Management Module Documentation

Salesforce Trailhead: Program Management for Nonprofits

Note: While the Education Data Architecture (EDA) is tailored for educational institutions and managing student data, it is not specifically designed for nonprofits focusing on fundraising and program management like NPSP and PMM. Therefore, PMM is the more appropriate solution for tracking courses and training participation alongside fundraising activities in a nonprofit context.