Nonprofit-Cloud-Consultant Questions and Answers

In Salesforce Nonprofit Cloud, Action Plan Templates are used to standardize repeatable processes, such as the steps required to onboard a new client or complete a grant application. To ensure data integrity and version control, Salesforce treats published Action Plan Templates as "locked" records.

When an organization needs to modify an "Active" or "Published" template—such as adding new tasks—the system does not allow direct editing of the existing record to prevent breaking current active Action Plans that were generated from that specific version. The standard procedure for a consultant is as follows:

Clone the Template: The user must select the existing Action Plan Template and use the Clone action. This creates a new "Draft" version of the template with all the existing tasks copied over.

Modify the Draft: In the new draft record, the consultant can add the additional tasks, define their priority, set the number of days for completion, and assign roles or specific users to those tasks.

Publish: Once the modifications are complete, the new template must be Published. Publishing makes the template available for users to generate new Action Plans.

Retire the Old Template: Although not strictly required to make the new tasks work, it is best practice for a consultant to deactivate or rename the old version to ensure staff only use the most up-to-date process moving forward.

Option B is incorrect because Salesforce does not typically allow you to "deactivate and edit" the task structure of a template that has already been published. Option A describes a specific setting that allows end-users to add extra tasks to an individual instance of a plan, but it does not address the requirement of updating the master template itself.

To create a sophisticated, multi-section grant application in Nonprofit Cloud for Grantmaking, Salesforce leverages the Discovery Framework and Dynamic Assessments. This combination allows a consultant to build an interactive digital experience that goes far beyond simple data entry.

Step-by-Step Application Build:

Discovery Framework: The consultant starts by creating the individual "Questions" in the Discovery Framework. Each question (e.g., "Number of individuals served" or "Geographic focus") is a reusable record.

Assessment Definition: These questions are then organized into an Assessment Task or Assessment Definition.

OmniScript Design: Using OmniStudio, the consultant builds an OmniScript that serves as the "Dynamic Assessment" engine. This is where the multi-section logic is defined. For example, a "Counseling Details" section might only appear if the applicant selects "One-on-one Counseling" as their service type.

Mapping: Using DataRaptors, the data entered into the form is mapped directly to the Individual Application object and its related records (like Budget or Contact Profile).

Experience Cloud Integration: Finally, the consultant places the Assessment component on the Grantmaking portal. The Form Overview and Form Review components (part of the Grantmaking template) work specifically with this Discovery Framework/OmniScript data to show the applicant their progress and allow them to review their answers before a final submission.

Why other options are incorrect:

Option A: "Form Framework" is not a standard, named feature in NPC; the required technology is Discovery Framework.

Option B: While Dynamic Forms (and Field Sets) work for internal record pages, they do not support the complex multi-step, branching logic or the specialized "Overview/Review" components required for a public-facing Grantmaking portal application. Using Discovery Framework is the architecturally correct way to provide a professional and compliant grant seeking experience.

In Salesforce, sensitive data like Social Security Numbers or Tax IDs is often protected using Classic Encryption or Shield Platform Encryption. When a field is encrypted, it appears as masked (e.g., XXXX-XX-1234) to most users, even if they have "Read" access to the Contact object.

To allow a specific subset of users (such as the HR Director or a high-level Compliance Officer) to see the actual, unmasked data, the View Encrypted Data system permission must be utilized.

Step-by-Step Implementation:

Create a Permission Set: The consultant should create a specific Permission Set named "PII Access" or similar.

Enable System Permission: Under the System Permissions section of the Permission Set, the consultant must locate and check the box for View Encrypted Data.

Assign to Users: This Permission Set is then assigned only to the specific users who require access to the sensitive identification numbers.

Security Principle: This follows the "Principle of Least Privilege." Users with this permission can see the data in plain text in reports, list views, and record pages, while all other users see the masked version.

Why other options are incorrect:

View All Data (Option A): This is a very broad and dangerous permission that grants access to almost all data in the org, but even "View All Data" does not automatically unmask encrypted fields unless View Encrypted Data is also present.

Manage Encryption Keys (Option B): This is a highly technical administrative permission for managing the security certificates and keys; it does not grant the ability to view field data.

View All Contacts (Option D): This provides object-level visibility but respects field-level security and masking.

When a nonprofit organization needs to integrate external third-party applications into the Salesforce user interface while maintaining a seamless "single pane of glass" experience, Salesforce Canvas is the specialized tool designed for this purpose.

How Salesforce Canvas Works:

Application Encapsulation: Canvas allows a consultant to take an existing external web application (such as a legacy accounting tool, a specialized document management system, or a custom program tracking app) and "embed" it directly within Salesforce.

Authentication and Identity: Unlike a simple