For administrator-controlled registration, the Contact page layout should include the Enable Customer User action. This allows an authorized internal user to manually provision an Experience Cloud login from the constituent ' s Contact record rather than permitting visitors to create their own accounts.

Salesforce ' s documented manual-registration process instructs administrators to open Contact page-layout configuration and add Enable Customer User and, where appropriate, View Customer User. An administrator then opens the participant ' s Contact record, selects Enable Customer User, and specifies the username, profile, and other required user information. Current Salesforce guidance also confirms that Manage External Users functionality includes the Enable Customer User action and that these actions appear individually on Contact layouts in Lightning Experience. Self-registration would directly contradict the requirement because it allows external visitors to initiate account creation. There is no separate standard Contact action named Register User that replaces the established external-user provisioning mechanism described here. This configuration gives the PSO controlled onboarding of grantseekers while still allowing the resulting users to authenticate to the Grants Management Experience Cloud site after their accounts are provisioned.

Study Guide References: Grants Management; Experience Cloud User Administration; Manual Registration; Contact Page Layout; Enable Customer User.

Partner Central is the Experience Cloud template designed for partner and channel-management scenarios. Salesforce specifically identifies Partner Central as supporting lead distribution, lead monitoring, deal registration, partner onboarding, channel programs, and collaborative marketing capabilities. Salesforce documentation states that organizations can use Partner Central to implement lead distribution and deal registration and manage channel-sales relationships without constructing those functions from the ground up.

Deal registration is particularly relevant because Partner Central includes predesigned components and processes for partner-submitted deals, including Quick Create capabilities, lead and deal list views, approval workflows, and channel-conflict management. The template also supports partner recruitment and onboarding as well as marketing initiatives such as campaigns and market-development activities. Help Center is primarily intended for customer self-service and knowledge delivery, while Customer Account Portal focuses on customer account interaction. Neither is optimized for partner relationship management and channel-selling workflows. Partner Central therefore aligns directly with the agency ' s requirement to manage external associates as channel partners.

Study Guide References: Experience Cloud; Partner Central; Partner Relationship Management; Lead Distribution; Deal Registration; Channel Marketing.

Two Decision Matrices provide the appropriate separation of rule domains. One matrix represents the Federal Income Limit reference data, where inputs such as household size are evaluated to return the corresponding income threshold. The Expression Set can then calculate the household ' s AMI percentage by comparing household income with the returned threshold.

A second Decision Matrix maps that calculated percentage to the appropriate prioritization pool. This separation keeps externally defined income thresholds independent from the agency ' s prioritization policy, enabling either rule set to be maintained without restructuring the other. Salesforce defines Decision Matrices as lookup tables that match input values to rows and return the corresponding output values. Expression Sets perform calculations and can invoke Decision Matrices as part of a larger rule sequence. Salesforce ' s eligibility examples similarly demonstrate using household income and household size as matrix inputs for determining income thresholds before subsequent eligibility or benefit calculations. A third matrix for household data is unnecessary because household income and size are runtime inputs, not a separate policy lookup table.

Study Guide References: Business Rules Engine; Expression Sets; Decision Matrices; Lookup Tables; Prioritization; Income and Household Eligibility Rules.

Shield Platform Encryption and Event Monitoring provide complementary controls for protecting and monitoring sensitive information such as protected health information.

Platform Encryption protects sensitive Salesforce data at rest while preserving critical application functionality. Salesforce specifically identifies Platform Encryption as a capability that can help organizations address requirements associated with storing PHI, personally identifiable information, confidential data, and other sensitive information. Organizations retain control over encryption keys and can determine which supported fields and data categories are encrypted. Event Monitoring addresses the monitoring and audit side of the security model. It captures detailed information about user activity and system interactions, including who accesses Salesforce data, when access occurs, and the context of that activity. These event records can support security investigations, threat detection, compliance monitoring, and integration with external security platforms such as SIEM solutions. Together, these tools provide defense in depth: encryption protects sensitive PHI stored within the platform, while Event Monitoring supplies visibility into access and usage. Field Audit Trail is valuable for long-term field-change retention, and Setup Audit Trail tracks administrative configuration changes, but the pair explicitly aligned to PHI protection in the supplied scenario is Platform Encryption and Event Monitoring.

Study Guide References: Salesforce Shield; Platform Encryption; Event Monitoring; Protected Health Information; Public Sector Security and Compliance.

The appropriate design combines authentication, bot protection, and restrictive external record access. Experience Cloud allows individual pages to be configured as Requires Login, which prevents unauthenticated visitors from accessing those pages even when other portions of the site are publicly available. Grant application OmniScripts should therefore be placed behind authenticated access when they collect or expose constituent-specific information.

CAPTCHA or reCAPTCHA adds automated abuse protection by distinguishing legitimate human submissions from bots. Salesforce documents reCAPTCHA implementations for Experience Cloud scenarios specifically to prevent automated or fraudulent form submissions. The external organization-wide default for sensitive application records should also be Private. Salesforce recommends keeping external OWD settings Private whenever possible and then opening access only through controlled sharing mechanisms. With Private external access, authenticated external users cannot automatically see other constituents ' records. A public application-reference search page would risk unnecessary information exposure and does not prevent form abuse. The combination of authentication, CAPTCHA, and restrictive sharing implements defense in depth for constituent application data.

Study Guide References: Experience Cloud Security; Requires Login; CAPTCHA/reCAPTCHA; External Organization-Wide Defaults; Grant Application Privacy; OmniScripts.

Before an initial OmniStudio package installation, Salesforce requires the organization to prepare both the browser environment and the Salesforce org.

First, the browser and Salesforce environment must satisfy the published minimum requirements. Salesforce specifies supported browser requirements, JavaScript availability, minimum system resources, a supported Salesforce edition, and the necessary OmniStudio entitlement. Second, the org must have Orders enabled. Third, email deliverability must be configured with the access level set to All email. These settings are part of Salesforce ' s explicit pre-installation checklist. The preparation procedure is intended to avoid package-test and runtime failures caused by missing Salesforce platform dependencies. Salesforce also notes that Enhanced Email is normally enabled and that OmniStudio package testing uses functionality related to the EmailMessage object. Person Accounts can be an important Public Sector prerequisite when the agency needs to represent individual constituents, but Person Accounts are not a universal OmniStudio package installation prerequisite. Similarly, enabling Assets is not one of the specified package preparation requirements. The proper sequence is therefore to validate the supported browser and platform environment, enable Orders, and ensure Salesforce email deliverability is configured for All email before beginning installation.

Study Guide References: Prepare to Install OmniStudio; OmniStudio Package Prerequisites; Enable Orders; Email Deliverability; Browser and Platform Requirements.

The Analytics for Licenses, Permits, and Inspections template performs a data compatibility check before creating the analytics application. Salesforce requires the Public Sector org to contain source records from the LPI operational data model so that the template can build its datasets and dashboards.

Salesforce ' s current data-requirements documentation identifies Visit as one of the supported source objects used by LPI analytics, along with Business License Application, Individual Application, Public Complaint, and Regulatory Transaction Fee. If the org lacks qualifying source data, the template returns an error during application creation and instructs the administrator to add the required data before trying again. Among the choices, missing Visit data is the relevant operational-data problem associated with the inspection portion of the analytics application. Visits represent actual inspection activity and are therefore central to metrics such as inspections performed, inspection volume, and related operational trends. Violation records, active Action Plan Templates, and Person Account enablement are not listed as the prerequisite represented by this compatibility-check scenario.

Study Guide References: CRM Analytics for Public Sector; Analytics for Licenses, Permits, and Inspections; Data Requirements; Visit Object; Analytics Compatibility Check.

Salesforce ' s Grants Management installation requirements include the appropriate Grants Management entitlement together with Customer Community Plus Login licensing, Lightning Experience, Digital Experiences, My Domain, and Chatter. Salesforce explicitly lists Customer Community Plus Login, Lightning Experience, and Chatter among the package prerequisites.

Customer Community Plus is important because a grantmaking portal generally requires richer authenticated external-user capabilities than a basic high-volume customer portal. Grant applicants need controlled access to funding requests, requirements, application records, and related processes. The Grants Management implementation can also establish a grantseeker profile and sharing configuration for those users. Lightning Experience is required because Grants Management and its modern application components operate within the Lightning platform. An organization whose staff still work in Salesforce Classic must therefore transition the relevant users to Lightning Experience before adopting the solution. Chatter is also a prerequisite because Grants Management includes collaboration-dependent functionality. Web-to-Lead does not provide the grant-application architecture, and basic Customer Community licensing does not satisfy the package ' s specified portal licensing requirement.

Study Guide References: Grants Management Installation; Grants Management Prerequisites; Customer Community Plus; Lightning Experience; Chatter; Grantseeker Portal.

Administrator users responsible for creating and managing Public Sector analytics require both the CRM Analytics platform-level administrator capability and the Public Sector-specific analytics administrator capability.

CRM Analytics Plus Admin supplies the permissions required to administer CRM Analytics, including creation and management of templated analytics applications. Salesforce describes this prebuilt permission set as providing the administrative permissions for CRM Analytics Plus and associated application-management functionality. The administrator must also receive the Public Sector analytics administrator permission set represented in the options by CRMA for Public Sector Admin. Current Salesforce documentation identifies this Public Sector-specific administrative permission as TCRM for Public Sector Admin. Salesforce ' s setup procedure explicitly instructs administrators to assign CRM Analytics Plus Admin AND TCRM for Public Sector Admin to users who create and manage Public Sector analytics applications. The combination separates platform administration from industry-template access. CRM Analytics Plus Admin alone does not provide the full Public Sector-specific entitlement required by the LPI application, while the industry permission alone does not supply the necessary CRM Analytics platform administration rights.

Study Guide References: CRM Analytics for Public Sector; Analytics for Licenses, Permits, and Inspections; Admin Permissions; CRM Analytics Plus Admin; Public Sector Analytics Admin.

DataRaptor—called OmniStudio Data Mapper in current Salesforce terminology—provides the declarative data-mapping capability required to convert incoming application data into records on Salesforce objects.

A Data Mapper Load accepts JSON, XML, or custom-formatted input and creates or updates Salesforce records according to configured field mappings. Salesforce explicitly states that Data Mapper Load writes input data to Salesforce objects and can populate multiple mapped records without requiring custom Apex. This capability is particularly relevant when the source application runs outside Salesforce. Salesforce provides a Data Mapper REST API through which an external system can issue a POST request containing the application payload and invoke a Data Mapper Load to update the appropriate Salesforce objects. For the agency, grant application information collected in the existing external portal can therefore be transformed and mapped into Agentforce Public Sector records such as constituent, application, or funding-related objects. Integration Procedures provide broader server-side orchestration and can themselves invoke Data Mappers, but the specific requirement emphasized here is mapping submitted data into Salesforce objects. FlexCards are presentation components, while OmniOut is primarily used to run OmniStudio UI components outside Salesforce rather than serving as the direct object-mapping mechanism.

Study Guide References: OmniStudio DataRaptors/Data Mappers; Data Mapper Load; REST API; External Portal Integration; Public Sector Grant Application Data Mapping.