Set up the Experience Cloud site that hosts your fusionCore portal components.
A fusionCore portal site is a standard Salesforce Experience Cloud site — there is no custom “portal site” object. fusionCore ships the portal components (profile sections, checkout, payment confirmation, and more), not the site container itself. Every fusionCore portal component declares Experience Cloud page targets, which is why it appears in the Experience Builder component palette and can only be placed inside an Experience Cloud site.Use a Lightning Web Runtime (LWR) template for new sites. Aura templates still work, but the Aura framework is being deprecated, so LWR is the recommended path for any new fusionCore portal.
In Setup, search for and open Digital Experiences, then click Settings. Select the Enable Digital Experiences checkbox and click Save.
The Digital Experiences Settings page in Setup
Once Digital Experiences is enabled, the Enable Digital Experiences checkbox is replaced by this Settings page, which shows your experience domain and management options. The domain you set here forms the base URL for every site you create.
2
Create a new site
In Setup, open Digital Experiences, click All Sites, then click New.Choose an LWR template for your use case, provide the site name, URL, and description, then click Create.
Creating a new Experience Cloud site
3
Grant profile access to the site
After the site is created, click Workspaces to open the administration panel, then click Administration.Click Members, set the filter to All Profiles, and add the profile types you want to give access to this portal. Users with the selected profiles will be able to log in to the site.
fusionCore portal components render only inside an Experience Cloud site. They target Experience Builder pages only, so you cannot place them on internal Lightning record pages or Lightning app pages. If a component is missing from the palette, confirm you are editing an Experience Cloud site and not an internal page.
Use an LWR template for new sites. Aura templates are supported for legacy sites, but the Aura framework is being deprecated. Starting on Aura now means a migration later.
⌘I
Assistant
Responses are generated using AI and may contain mistakes.