In fundraising, it is essential to distinguish between the person who physically wrote the check (the "Hard Credit") and the person who influenced the gift (the "Soft Credit"). In Nonprofit Cloud for Fundraising, this influence is tracked using the Gift Soft Credit object.
How a Consultant Configures Influence Tracking:
* The Transaction: A Gift Transaction is created for the donor who made the payment.
* The Influence: If a board member or a volunteer solicitor was responsible for bringing in that gift, a Gift Soft Credit record is created and linked to that Gift Transaction.
* Soft Credit Roles: The consultant can define different types of soft credits using the Role field.
Common roles include "Solicitor," "Peer-to-Peer Fundraiser," or "Household Member."
* Reporting: By using this object, the organization can run reports on "Total Influence" per volunteer.
This is vital for donor recognition programs where "Solicitors" are honored for the total funds they helped raise, even if they didn't donate the money personally.
Why other options are incorrect:
* Gift Tribute (Option A): This is used to track gifts made "In Honor Of" or "In Memory Of" someone.
While it involves a third party, it is specifically for the sentiment of the gift rather than the professional or volunteer solicitation influence.
* Gift Designation (Option C): This object is used to allocate the funds to specific internal accounts or programs (e.g., "General Fund" or "Building Campaign"). It tracks where the money goes, not who helped get it.
The Gift Soft Credit object ensures that the organization has a 360-degree view of constituent engagement, acknowledging both financial contributors and the champions who drive the fundraising engine.

When an organization uses a Private sharing model (Organ11ization-Wide Defaults), users can only see records they own or records owned by their subordinates in the role hierarchy. To open up visibility to a
"subset" of records for a "selected" group of staff, the consultant must use a Sharing Rule.
Implementing the Solution:
* Criteria-Based Logic: Since only a subset of Service Deliveries (e.g., those related to "Mental Health" or a specific "Program") needs to be shared, the consultant should use a Criteria-Based Sharing Rule.
* Definition: The rule might state: "Share Service Delivery records where Program Name EQUALS ' Youth Outreach' with the 'Program Staff' Public Group."
* Access Level: The consultant defines the level of access (Read Only or Read/Write).
* Public Groups: The "selected staff" should be added to a Public Group. The sharing rule then targets this group.
Why other options are incorrect:
* Public Read/Write (Option B): This would expose all records to all users, violating the nonprofit's strict security requirements.
* Permission Sets / Profiles (Options C & D): These grant the functional ability to use the object (CRUD), but in a Private sharing model, they do not grant access to specific records owned by others.
Sharing rules are the primary tool for record-level visibility in Salesforce.

When donor totals (e.g., "Total Gifts This Year") are incorrect, the consultant must investigate the l30ogic that aggregates those numbers. In NPSP, this involves a combination of configuration settings and system health tools.
Three Critical Areas to Troubleshoot:
* Customizable Rollups (B): This is the engine that calculates the totals. The consultant should check if the Filter Groups are correctly defined. For example, if a rollup is set to only count "Individual" gifts but the missing gifts are marked as "Major Gifts," the filter logic is the culprit.
* Opportunity Stages (C): NPSP rollups only include donations that are in a "Closed/Won" state. If the organization created a custom stage (e.g., "Received - Awaiting Acknowledgment") but didn't mark that stage as "Won" in the Stage picklist settings, those gifts will be ignored by the rollup engine.
* NPSP Health Check (D): This is the first place a consultant should look for system-wide issues. The Health Check will identify if the nightly rollup batch job is failing, if there are orphaned records, or if there are "Data Integrity" issues (like an Opportunity without an Account) that prevent the rollups from processing successfully.
Why other options are incorrect:
* Salesforce Optimizer (Option A): This is a general org health tool (checking limits, unused fields, etc.) and does not have the nonprofit-specific logic needed to troubleshoot NPSP rollups.
* Campaign Hierarchy (Option E): While hierarchies help with campaign reporting, they do not impact the "hard credit" rollups on Account and Contact records.

In NPSP, we must distinguish between "Hard Credit" (legal ownership) and "Soft Credit" (influence
/relationship). When a family foundation (a Business Account) gives a donation, the Foundation gets the Hard Credit. However, the organization wants the Household Account (the family themselves) to receive credit for that gift in their "Total Giving" history.
The Solution: Account Soft Credits:
* Hard Credit: The Opportunity is created with the Family Foundation Account in the Account Name field. This is the legal donor.
* Soft Credit: To reflect this gift on the Family's Household, the consultant uses the Account Soft Credit feature.
* Relationship Tracking: A record is created in the Account Soft Credit related list on the Opportunity.
The "Account" is the Family's Household Account, and the "Role" is set to something like "Family Foundation."
* Rollups: NPSP's rollup engine will then pick up this soft credit. The family's Household record will now show this gift in fields like "Total Account Soft Credits" or "Total Gifts" (if the organization includes soft credits in their summary).
Why other options are incorrect:
* GAU Allocation (Option A): This tracks the fund or purpose of the money (e.g., "Building Fund"), not the donor or household credit.
* Lookup Fields (Options B & D): Adding custom lookup fields does not trigger NPSP's complex rollup logic. Only the standard Account Soft Credit object is recognized by the NPSP engine for aggregating influence-based giving to an account.

For organizations delivering personalized social services, the intake evaluation is the most critical touchpoint.
To manage this efficiently, Salesforce Nonprofit Cloud utilizes Dynamic Assessments, a feature built upon the Discovery Framework and OmniStudio (specifically OmniScript).
Unlike a static form, a Dynamic Assessment allows a caseworker to navigate a "branching" path of questions.
If a client answers "Yes" to a question about housing instability, the system can automatically trigger a sub- section of questions regarding shelter history. If they answer "No," those questions remain hidden, reducing
"form fatigue" and ensuring the intake is as fast and relevant as possible.
Step-by-Step Implementation for the Consultant:
* Define Assessment Questions: Using the Discovery Framework, the consultant creates a library of individual questions (e.g., "Do you have dependable transportation?"). These questions are modular and can be reused across different intake forms.
* Build the OmniScript: The consultant uses the OmniScript Designer to arrange these questions. This is where the Conditional Logic is applied (e.g., "Set Element Visibility" based on prior answers).
* Map to Objects: Through DataRaptors or Integration Procedures, the consultant ensures that the data captured during the assessment is automatically pushed into the correct Salesforce objects, such as Person Accounts, Case Proceedings, or Life Events.
* Action Plan Integration: Often, the completion of a Dynamic Assessment is linked to an Action Plan, which might automatically generate a "Welcome Kit" task or a "Referral" based on the needs identified during intake.
By using Dynamic Assessments, the nonprofit ensures a standardized, compliant, and data-driven intake process that captures a 360-degree view of the client's assets and barriers to success without requiring the caseworker to navigate through irrelevant fields.