Skip to main content
Portal pages are standard Experience Builder pages on your Experience Cloud site. You create a page, lay out its columns, set its access, then drag fusionCore components onto it. fusionCore portal components read their context from URL query parameters, not from a record bound to the page. For example, the checkout component reads the order it should display from an ?orderId= parameter in the page URL. When you link to a context-driven page, include the parameter the component expects — a checkout page reached without ?orderId= cannot tell which order to load.

​
Prerequisites

  • A portal site already created — see Setting up a Portal Site.
  • A user with admin permissions to edit the site in Experience Builder.

​
How to Create a Portal Page

1

Open Experience Builder

In Setup, search for All Sites in the Quick Find box and select it. Find your portal site and click Builder.
The All Sites list with the Builder link for a portal site

Opening Experience Builder for a site

2

Add a new standard page

In Builder, open Settings and select New Page, then choose Standard Page.
The New Page option in Experience Builder settings
The page type dialog with Standard Page selected

Choosing a Standard Page

3

Name the blank page

Select New Blank Page, give the page a name, and click Create.
The new blank page dialog with a page name entered

Naming the new page

4

Lay out the page

Add as many columns as the page needs. Use the Settings, Style, and Visibility tabs to configure the layout and appearance.
The page layout configuration tabs in Experience Builder

Configuring the page layout

5

Set page access

In the page settings, set Page Access according to who should reach the page — for example, public for guests or authenticated for logged-in members only.
The Page Access setting in Experience Builder

Setting page access

6

Add components and publish

At the top left, click the Lightning icon to open the component palette, then drag the fusionCore components you need onto the page. When you are done, click Publish at the top right to push your changes live.
The Experience Builder component palette with fusionCore components

Dragging components onto the page

​
Redirecting Portal Users on Page Load

To send portal users to a different page automatically — for example, to route members from a landing page to their profile — place the FS Portal - Auto Redirect component on the page. Set its Target Redirect URL property to the destination, and the component redirects the user when the page loads. Use a relative site URL or a full URL as needed for your destination.
The FS Portal - Auto Redirect component selected in Experience Builder, with the Target Redirect URL property set to /profile in the right-hand property panel

The FS Portal - Auto Redirect component selected, with its Target Redirect URL property

​
Limitations and Common Pitfalls

  • Context-driven components need their URL parameter. Components such as checkout read their context from URL query parameters (for example, ?orderId=), not from a record bound to the page. A page reached without the expected parameter shows a missing-context error. Always link to these pages with the parameter the component expects.
  • fusionCore components only appear inside an Experience Cloud site. If a component is missing from the palette, confirm you are editing an Experience Cloud site page, not an internal Lightning page.
  • Changes go live only on Publish. Edits in Experience Builder are not visible to users until you click Publish.