11.1 Public Sector Experience Cloud Site Templates & Citizen Self-Service

11.1 Public Sector Experience Cloud Site Templates & Citizen Self-Service

Exam Focus: Experience Cloud is the primary constituent engagement layer (Layer 5) of Salesforce Public Sector Solutions (PSS). On the AP-222 exam, candidates must master the pre-built public sector site templates (Licenses and Permits, Grantmaking), understand the citizen self-service lifecycle (from public catalog browsing to inspection scheduling and fee payment), configure Experience Builder layouts and audience targeting, and embed OmniStudio Lightning Web Components (OmniScripts, FlexCards) to deliver accessible, high-performing digital government services.

---

Experience Cloud Architecture in Public Sector Solutions

Modern constituents expect government interactions to mirror consumer-grade digital experiences: intuitive navigation, mobile responsiveness, transparent processing timelines, and frictionless self-service. Historically, public agencies maintained fragmented, siloed web portals that merely hosted downloadable PDF forms, requiring manual clerical re-entry and generating substantial administrative overhead.

Salesforce Experience Cloud serves as the external digital front door for Public Sector Solutions, bridging public constituents directly with agency back-office operations on a unified platform. In the PSS multi-tiered enterprise architecture, Experience Cloud represents the Presentation & Engagement Layer (Layer 5), sitting directly above the Digital Process Automation tier (OmniStudio & Business Rules Engine) and the core PSS Domain Data Models (Licenses, Permits, Inspections, Grants, and Benefits).

+-----------------------------------------------------------------------------------+
| Experience Cloud Citizen Engagement Layer (LWR / Aura Runtime)                   |
| [Public Landing Pages]  [Constituent Dashboard]  [Application Tracking]  [Payment]|
+-----------------------------------------------------------------------------------+
                                        |
                                        v
+-----------------------------------------------------------------------------------+
| OmniStudio Presentation Components (Embedded LWCs)                               |
| [Intake OmniScripts]  [Constituent 360 FlexCards]  [Document Checklist Uploader]  |
+-----------------------------------------------------------------------------------+
                                        |
                                        v
+-----------------------------------------------------------------------------------+
| Digital Process Automation & Business Rules Engine (Server-Side)                  |
| [Integration Procedures]  [Data Mappers]  [Expression Sets & Fee Decision Tables] |
+-----------------------------------------------------------------------------------+
                                        |
                                        v
+-----------------------------------------------------------------------------------+
| Public Sector Solutions Standard Data Models                                      |
| [BusinessLicenseApplication]  [IndividualApplication]  [Visit]  [RegulatoryFee]    |
+-----------------------------------------------------------------------------------+

Runtime Architectures: Aura vs. Lightning Web Runtime (LWR)

When provisioning an Experience Cloud site in Public Sector Solutions, architects must evaluate the underlying runtime framework:

• Lightning Web Runtime (LWR): Built on standard Web Components, LWR delivers unmatched page load speeds, superior Core Web Vitals, and strict Content Security Policy (CSP) enforcement. LWR sites load exceptionally fast because they compile minimal JavaScript overhead, making them ideal for high-volume public crisis portals, emergency assistance intake, and mobile-first constituent experiences.
• Aura Runtime: The mature, feature-rich framework that supports extensive legacy component ecosystems, standard Chatter feeds, and complex pre-packaged AppExchange solutions. While LWR is the strategic direction for modern public sector deployments, Aura remains widely deployed across agencies requiring deep backward compatibility.

---

Pre-Built Public Sector Site Templates

To accelerate deployment and ensure adherence to industry best practices, Salesforce delivers pre-configured Experience Cloud templates specifically designed for public administration. Rather than building digital portals from generic customer service templates, implementation teams leverage these domain-specific blueprints.

1. Licenses and Permits Template

The Licenses and Permits Template is engineered specifically for municipal, county, and state regulatory authorities. It provides pre-configured page layouts, navigation hierarchies, and workflow components for occupational licensing boards, building departments, health inspection bureaus, and environmental agencies.

Key out-of-the-box capabilities include:

• Public Authorization Catalog: A searchable directory where citizens and commercial entities explore available regulatory authorizations, prerequisite requirements, estimated processing durations, and fee schedules.
• Guided Application Intake: Pre-integrated OmniScript wrappers that launch dynamic, multi-step application filings for standard records such as BusinessLicenseApplication and IndividualApplication.
• Application Status & Milestone Tracking: Real-time visibility into application review stages without exposing internal casework notes or sensitive enforcement investigations.
• Self-Service Inspection Management: Portal pages allowing constituents to review required inspections, request site visit dates, and review inspection findings.
• Electronic Permit & License Issuance: Automated document distribution where approved applicants download official, watermarked PDF authorization certificates generated by OmniStudio Document Generation.

2. Grantmaking (Grants Management) Template

The Grantmaking Template is tailored for funding organizations, educational grant bodies, research councils, and state/federal departments distributing public funds or block grants.

Key out-of-the-box capabilities include:

• Notice of Funding Opportunities (NOFO) Discovery: A public-facing funding catalog displaying active grant programs (FundingProgram), open opportunities (FundingOpportunity), eligibility criteria, and submission deadlines.
• Grant Application Workspace: A comprehensive applicant workspace where organizations draft multi-section grant proposals, collaborate across team members, and upload detailed project budgets and financial audits.
• Milestone & Progress Reporting: Post-award management pages enabling grant recipients to submit periodic programmatic updates, performance metrics, and expenditure reports.
• Disbursement Schedule Visibility: Financial dashboards displaying approved grant award amounts (FundingAward), payment schedules, and historical disbursement records (Disbursement).

Template Architectural Comparison

---

Citizen Portal Structure & Core Self-Service Journeys

A production-ready public sector portal organizes the constituent experience into five distinct functional zones, balancing public information discovery with authenticated transactional processing.

1. Public Landing Pages

The unauthenticated homepage serves as the public agency's digital front door. Key structural components include:

• Global Universal Search: An enterprise search bar that queries published Knowledge articles, regulatory catalogs, and public announcements.
• Service Category Tiles: Visual entry points categorized by statutory domain (e.g., Building & Construction, Professional Licensing, Public Health & Safety, Business Registration).
• Emergency Announcements & Banners: Prominent alert components for municipal emergencies, office closures, statutory deadline extensions, or seasonal fee adjustments.

2. Constituent Dashboard ("My Services" Hub)

Once an authenticated citizen logs into the portal, they are greeted by a personalized constituent dashboard. This dashboard aggregates all active interactions into a single actionable interface:

• Active Applications: Summary cards displaying submitted BusinessLicenseApplication and IndividualApplication records, highlighted with current status badges (e.g., Under Initial Review, Pending Zoning Clearance, Action Required: Resubmit Plan).
• Active Licenses & Registrations: Digital cards representing issued BusinessRegulatoryAuthorizationType records, showing license numbers, effective dates, expiration warnings, and one-click "Renew License" actions.
• Upcoming Inspections: Interactive schedule views displaying scheduled Visit records, assigned inspection windows, inspector contact details, and rescheduling links.
• Financial Account Summary: Outstanding regulatory fees, citation penalties, and historical payment receipts.

3. Application Status & Milestone Tracking

Constituent anxiety regarding permit and license approvals represents the single largest driver of inbound call center volume in public agencies. Experience Cloud mitigates this through declarative Application Status Trackers:

• Visual Chevron Progression: Displays linear milestones (e.g., Submitted -> Completeness Check -> Technical Review -> Site Inspection -> Final Board Approval -> Issued).
• Selective Transparency: The status tracker reads public-facing milestone statuses while shielding internal operational complexities. For example, internal caseworker chatter, fraud investigation flags, and supervisory notes remain strictly hidden from the constituent portal view.
• Actionable Task Prompts: When an application requires applicant intervention—such as an illegible architectural drawing or an expired insurance certificate—the status tracker displays an alert banner linking directly to the required DocumentChecklist item.

4. Self-Service Inspection Scheduling

Rather than engaging in multi-day phone tag with agency dispatchers, constituents manage compliance inspections directly through the portal:

• Inspection Prerequisite Verification: The portal evaluates whether prerequisite milestones are completed (e.g., structural framing cannot be scheduled until foundation inspection is marked Compliant).
• Dynamic Slot Reservation: Integration with Salesforce Scheduler or PSS Inspection Visit management presents real-time inspector availability windows based on geographical territory and inspection type.
• Pre-Inspection Checklist Distribution: Upon confirmation, the portal delivers automated instructions detailing job-site safety requirements, required on-site personnel, and physical access prerequisites.

5. Fee Payment Integration

Statutory applications require fee collection before processing or license issuance. The portal integrates payment workflows:

• Fee Presentation: Displays line-item breakdowns derived from RegulatoryTransactionFee and RegulatoryTransactionFeeItem records calculated by the Business Rules Engine.
• Payment Gateway Processing: Embeds secure payment components integrating with state treasuries, Pay.gov, CyberSource, Stripe, or Authorize.Net via hosted payment pages or tokenized iframes.
• Automated Reconciliation: Upon successful payment capture, an Integration Procedure creates a Payment record, links it to the fee, updates the application status to Paid, and advances the review workflow.

---

Experience Builder Configuration: Branding, Layouts & Audience Targeting

Experience Builder is the declarative design environment used by administrators and consultants to customize public sector portals without custom code.

Theme Layouts & Design System Compliance

Public sector portals must project authority, trust, and strict accessibility compliance:

• Design Standards Alignment: In the United States, federal portals must adhere to the U.S. Web Design System (USWDS), while state and municipal agencies enforce localized branding guidelines. Experience Builder allows administrators to configure primary, secondary, and neutral color palettes, official government seal logos, and standard typography that satisfy WCAG 2.1 Level AA contrast ratios (minimum 4.5:1 for standard text).
• Header and Footer Customization: Public agency portals require standardized header layouts with official government agency identifiers, emergency contact numbers, privacy disclosures, and mandatory legal footers (FOIA notices, accessibility statements, terms of service).
• Theme Layout Components: Administrators configure theme layouts (e.g., Citizen Home Layout, Transactional Form Layout, Knowledge Base Article Layout) to control header, navigation, and sidebar positioning across different page templates.

Navigation Hierarchies & Route Structure

• Multilevel Navigation Menus: Structure intuitive navigational paths categorized by public persona (e.g., Residents, Businesses, Contractors, Visitors).
• Tile Menus & Visual Cards: Deploy high-contrast graphical tiles on landing pages for prominent constituent actions (Apply for a Permit, Pay a Citation, Report a Code Violation, Verify a Professional License).
• Breadcrumb Navigation: Essential for deep statutory knowledge bases, allowing constituents to retrace steps across multi-tiered regulatory documentation.

Audience Targeting: Dynamic Personalization

Audience Targeting in Experience Cloud allows architects to present different page variations, components, or navigation menus to specific user groups without cloning or duplicating site infrastructure.

In Public Sector Solutions, Audiences are defined using criteria such as:

1. User Profile & Permission Set: Differentiating between individual citizens (Customer Community profile) and commercial corporate contractors (Customer Community Plus profile).
2. Constituent Location / Geo-targeting: Displaying regional ordinances, municipal district notices, or localized fee waivers based on the constituent's physical postal code.
3. Account & Record Criteria: Presenting a "Commercial Cannabis Dashboard" component only to users whose associated Account possesses an active commercial cannabis authorization type.

+-------------------------------------------------------------------------+
| Experience Builder Page Canvas: "My Authorizations"                     |
+-------------------------------------------------------------------------+
| Audience Rule A: Profile == "Commercial Contractor Portal"              |
| -> Renders Multi-Entity Switcher, Fleet Inspection Tabs, Corporate Fees |
+-------------------------------------------------------------------------+
| Audience Rule B: Profile == "Citizen Self-Service Portal"               |
| -> Renders Individual License Cards, Personal Renewal Reminders         |
+-------------------------------------------------------------------------+
| Default Audience: Unauthenticated / Guest Citizen                       |
| -> Renders Public Search Catalog & "Create Account / Login" Prompt      |
+-------------------------------------------------------------------------+

---

Embedding Lightning Web Components on Experience Cloud Pages

The power of Public Sector Solutions on Experience Cloud lies in embedding enterprise OmniStudio components directly onto portal pages, combining declarative UI authoring with industrial-strength digital automation.

1. Embedding OmniScripts via LWC Wrappers

Every compiled OmniScript functions natively as a standard Lightning Web Component. Administrators deploy OmniScripts in Experience Builder by dragging the standard OmniScript LWC component onto the page canvas.

Key configuration parameters include:

• Type, SubType, and Language: Identifies the unique OmniScript metadata definition (e.g., Type: BuildingPermit, SubType: ResidentialSolar, Language: English).
• Context Passing (recordId / c__contextId): Automatically injects the active record ID from the portal page URL into the OmniScript Data JSON, enabling prefill Data Mappers to extract applicant and asset records instantaneously.
• Layout Configuration: Configures the component runtime to render using standard Salesforce Lightning Design System (SLDS) or custom Newport Design System (NDS) styling.
• Run Mode: Allows running in LWC mode directly inside the page DOM or within a modal dialog triggered by a button click.

2. Embedding FlexCards for Constituent 360 Summaries

FlexCards deliver contextual, responsive data summaries and quick actions:

• Constituent Summary Card: Displays applicant contact information, verified identity status, and active licenses with embedded flyouts.
• Action Framework: Action buttons on FlexCards launch OmniScripts in modal popups (e.g., clicking "Request Extension" opens a 2-step extension filing OmniScript without leaving the current dashboard).
• Responsive Design: FlexCard grids automatically reorganize across 12-column layouts, providing clean rendering on mobile smartphones, tablets, and desktop workstations.

3. Record Lists and Detail Components

• Secure Record Lists: Deploy standard CRM List Views filtered by constituent ownership, ensuring citizens see only applications and permits tied to their personal Person Account or commercial organization.
• Field-Level Security (FLS) Enforcement: Portal page components respect profile-level FLS, ensuring internal scoring rubrics, caseworker fraud alerts, and internal audit notes are never delivered to the client browser.

---

💡 Real-World AP-222 Exam Scenarios & Case Analysis

Scenario 1: State Occupational Licensing Board Multi-Trade Portal

A state occupational licensing board regulates 45 distinct professions, ranging from apprentice electricians to master plumbing contractors. Individual apprentices apply for personal certifications, while master contractors operate commercial contracting businesses employing dozens of tradespeople. The agency requires a single digital portal where individual apprentices see only their personal exam scores and apprentice cards, while commercial contractors can manage company licenses, view all employee affiliations, and pay bulk renewal fees for their entire workforce.

How should the Lead Architect configure this solution in Experience Cloud?

• Site Template: Deploy the Licenses and Permits Template on an LWR runtime.
• Audience Targeting: Create two Experience Cloud Audiences:
  • Audience 1: Individual Licensees (bound to the standard Customer Community profile).
  • Audience 2: Commercial Contractors (bound to the Customer Community Plus profile).
• Page Variation: Configure a page variation on the "My Services" dashboard:
  • For Audience 1, render a simplified FlexCard displaying personal certifications and continuing education hours.
  • For Audience 2, render an advanced FlexCard grid showing corporate BusinessLicenseApplication records, an employee affiliation management table, and a bulk payment OmniScript component.

Scenario 2: High-Volume Municipal Building Permitting & Inspection Surge

A metropolitan building department receives 150,000 residential solar and roofing permit applications annually. The agency is overwhelmed by telephone inquiries from homeowners asking if their permit has been approved and when inspectors will arrive. The agency requires an online self-service portal where applicants can track progress, receive alerts if architectural plans are rejected, and pick their own inspection dates without calling agency staff.

What architecture should the candidate recommend on the exam?

• Intake & Status: Embed an OmniScript intake flow on the portal for permit filing. Deploy an Application Status Tracker component on the constituent's application detail page to display real-time milestone chevrons.
• Document Remediation: Configure standard DocumentChecklist items. When an examiner rejects an architectural plan, the status tracker alerts the constituent and provides an inline upload button to submit revised drawings.
• Inspection Scheduling: Implement Self-Service Inspection Scheduling on the portal tied to the Visit object. The constituent selects available time slots populated dynamically based on inspector territory routing.