Download Latest Nonprofit-Cloud-Consultant Questions

For a large nonprofit organization functioning like a for-profit corporation and needing to manage Leads and track its Opportunity pipeline:

Salesforce Account Model without NPSP: This model is suitable as it aligns with for-profit business processes, focusing on managing business accounts, leads, and opportunities. The Household Account Model in NPSP is more suited for organizations managing individual donors, which is not applicable here.

Using the standard Salesforce Account Model allows the organization to leverage Salesforce’s CRM capabilities tailored for B2B interactions.

References:

Salesforce Account Model Documentation

Salesforce Trailhead: Managing Leads and Opportunities

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

Create GAU Records:

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

Create a new GAU record for each designated fund.

Link Donations to GAUs:

When entering or importing donations (Opportunities), use the GAU Allocation section to allocate the donation amount to the relevant GAU.

Specify the amount or percentage of the donation that should be allocated to each GAU.

Set Up GAU Allocation:

In the Opportunity record, scroll to the GAU Allocations related list.

Click "New" to create a new GAU Allocation.

Select the appropriate GAU and enter the allocation amount.

Reporting on GAUs:

Create reports to track donations by GAU.

Use the GAU Allocation object in your report to filter and summarize donations by designated funds.

By using GAU Allocations, the nonprofit can effectively manage and report on restricted funds, ensuring that donations are tracked according to donor intent.

References:

Salesforce NPSP Documentation: General Accounting Units (GAUs)

Salesforce Trailhead: Manage General Accounting Units (GAUs)

To protect sensitive data like a government-issued ID number, encrypting the field and carefully managing access permissions is crucial. Here's a step-by-step guide on implementing this security solution:

Create the Custom Field:

Navigate to Setup.

In the Object Manager, select the relevant object (e.g., Contact).

Click on Fields & Relationships.

Create a new Text field for the government-issued ID number.

Enable Classic Encryption for Custom Fields:

In Setup, search for "Encryption Policy".

Enable "Encrypt Custom Fields".

Select the custom field you created for the government-issued ID and mark it for encryption.

Set Permissions:

Navigate to Setup.

Go to Profiles or Permission Sets.

Ensure only the necessary profiles/permission sets have the "View Encrypted Data" permission:

Click on the relevant Profile or Permission Set.

In System Permissions, enable "View Encrypted Data".

Assign this permission only to those users who need to interact with the government ID data.

Adjust Field-Level Security:

In the Object Manager, select the custom field for the government ID.

Click on "Set Field-Level Security".

Ensure the field is visible only to the necessary profiles.

Remove the field from page layouts for users who should not access it.

Test the Setup:

Log in as a user with access to the encrypted data to verify they can view and interact with the data.

Log in as a user without access to ensure they cannot see the encrypted field.

By following these steps, you ensure that the government-issued ID number is encrypted and only accessible to authorized personnel, thereby protecting sensitive client data effectively.

References:

Salesforce Security Guide: Classic Encryption for Custom Fields

Salesforce Permission Sets: Managing Permissions

Enabling State and Country Picklists in Salesforce can improve data consistency and accuracy for address fields. However, there are specific considerations when using them with NPSP:

NPSP Data Import Object Doesn't Support State and Country Abbreviations in Picklist Form:

The NPSP Data Import object does not natively support state and country abbreviations in picklist form. This means that data imports using this object will require additional handling to map state and country values correctly.

Predefined State and Country Abbreviations on Address Records Must Be Used:

When using State and Country Picklists, predefined state and country abbreviations must be used. This ensures consistency and compatibility with Salesforce’s standard address fields.

If your current data uses different formats (e.g., full names or alternative abbreviations), you will need to standardize these before importing or entering data.

Consideration for Existing Data:

If enabling State and Country Picklists for the first time, review and clean existing data to match the picklist values.

Use data tools to update existing records with the correct state and country abbreviations to ensure smooth transition and consistency.

By understanding these considerations and preparing your data accordingly, you can successfully implement State and Country Picklists in NPSP.

References:

"State and Country/Territory Picklists Overview" from Salesforce Help: State and Country Picklists

"Managing Addresses in NPSP" from Salesforce Help: NPSP Address Management