Skip to main content
The Portal is the secure, self-service destination your members and customers use to manage their profiles, view and pay Orders, save payment methods, and renew subscriptions. It is built on a standard Salesforce Experience Cloud site: you create the site, then place fusionCore components onto its pages. fusionCore ships the components and the checkout engine — not the site container itself — so your Experience Cloud site and these components together make up the Portal.

​
How Portal Is Packaged

The Portal is delivered as two packages that play different roles. Knowing which package a component comes from tells you whether you can configure it, edit it, or only customize a copy.
  • Portal (FCORE_PORTAL) — the managed package. It ships the checkout engine and the payment-sensitive and other secure components (checkout, payment, wallet, and payment confirmation). Because it is managed and lives behind the FCORE_PORTAL namespace, you configure these components through their properties and supporting metadata, but you cannot edit their code.
  • Portal Components — the unmanaged package. It has no namespace and uses the FS_PORTAL_ (Apex) and fs_portal_ (component) prefixes. It ships most of the customer-facing components — the profile sections, the benefits and subscription hubs, and the checkout display shell. Because the package has no namespace, you can edit these directly, and they are meant to be customized to fit your site.
The two packages work together: the unmanaged display components call into the managed FCORE_PORTAL checkout engine to do the secure work.
Clone before you customize. Configuration-only changes are always safe and need no clone — adjusting a component’s properties in Experience Builder or editing a field set changes behavior without touching code, and a package upgrade leaves them intact.Code changes are different. If you need to change the code of an unmanaged component or Apex class, first make a clone of it (a renamed copy), apply your changes to the clone, and point your Experience page at the copy. If you edit the shipped unmanaged component directly, the next package upgrade overwrites your changes. The managed FCORE_PORTAL components cannot be edited at all — you configure them through their properties instead.

​
Setting Up the Portal

Setting up the Portal is a sequence: create the Experience Cloud site, decide who can reach it, build the pages, and place fusionCore components on those pages to handle checkout, profiles, subscriptions, and payments. If you are new to the Portal, start with Setting Up a Portal Site, then enable your users before building out individual pages.

Setting Up a Portal Site

Create the Salesforce Experience Cloud site that hosts your fusionCore components.

Enabling Guest Portal Users

Let unauthenticated visitors reach the pages you choose, and control what they can see.

Enabling Authenticated Portal Users

Give your members logins so they can manage their own records on the Portal.

Creating Portal Site Pages

Build Experience Builder pages and place fusionCore components onto them.

​
Portal Components and Pages

Checkout (LWC)

Set up the checkout page that takes payment against an Order or installment.

My Profile

Let portal users view and edit their own Account and Contact information through profile sections.

Portal Order Page (Roster Settings)

Configure the Order page and the roster settings that drive it.

Subscription Hub

Give members a hub to view, manage, renew, and cancel their subscriptions and allocate benefits.

Wallet Item Page

Place the wallet component so portal users can add and manage saved payment methods.