Skip to main content
The portal profile page lets a logged-in member view and edit their own data. There is no single “My Profile” component — you build the page from one or more FS Portal - Profile Section (fs_portal_profileSection) components, placing one per logical section (for example, Contact Information, Address Information, and Account Information). Each section renders a field set you choose on either the Account or the Contact object. You can also add the FS Portal - Profile Image (fs_portal_profileImage) component for the member’s photo.
The rendered portal profile page, showing the profile image followed by Contact Information, Address Information, and Account Information sections, each with an Edit button

A profile page as a logged-in member sees it, built from a Profile Image and three Profile Section components

​
Profile Section Properties

Each FS Portal - Profile Section component has these properties:
  • title (required) — the section heading shown to the member.
  • description — optional supporting text under the heading.
  • objectSetting (required) — the object whose field set is rendered. Must be exactly Account or Contact.
  • fieldSetApiName (required) — the API name of the field set, defined on the chosen object, that determines which fields appear.

​
Who Can Edit Each Section

How a section behaves depends on the object:
  • Contact sections are always editable. A member can always edit their own Contact.
  • Account sections are gated. A member can edit the Account section only if they are the Account’s Primary Contact (Primary_Contact__c), its Billing Contact (Billing_Contact__c), or the Account is a Person Account. Otherwise the section is read-only, and attempting to save throws an error.
  • Person Accounts render the section with the Name field disabled.

​
Prerequisites

  • A portal page to host the profile — see Creating Portal Site Pages.
  • The field sets you intend to use already defined on the Account or Contact object.
  • A user with admin permissions to edit the site in Experience Builder.

​
How to Build the Profile Page

1

Open the profile page in Experience Builder

Open your portal site in Experience Builder and navigate to the page you created for the profile. Click the Lightning icon to open the component palette.
2

Add the profile image (optional)

Drag the FS Portal - Profile Image component to the top of the page for the member’s photo.
The FS Portal - Profile Image component placed at the top of a portal page

The Profile Image component at the top of the page

3

Add a profile section for each group of fields

Drag an FS Portal - Profile Section component onto the page for each logical section. For each one, set:
  • title
  • description (optional)
  • objectSetting — Account or Contact
  • fieldSetApiName — the field set on that object
The property panel for an FS Portal - Profile Section component

Configuring a Profile Section component

4

Publish

Click Publish at the top right to make the profile page live.

​
Example Section Configuration

The following sections are a typical profile layout. The FS_PORTAL_Profile_* field sets ship with the package; you can also create your own field sets on the Account or Contact object and reference them here.
  • Contact Information — objectSetting: Contact, fieldSetApiName: FS_PORTAL_Profile_Contact_Info
  • Address Information — objectSetting: Contact, fieldSetApiName: FS_PORTAL_Profile_Address_Info
  • Account Information — objectSetting: Account, fieldSetApiName: FS_PORTAL_Profile_Account_Info

​
Limitations and Common Pitfalls

Putting an email field in a profile section silently changes the member’s login email. When a member saves an email field through a profile section, fusionCore writes it directly to the platform User.Email, bypassing the normal Experience Cloud change-email verification. The login email changes with no confirmation step. Only include an email field in a profile field set if you intend exactly this behavior.
  • objectSetting must be exactly Account or Contact. Any other value makes the component error instead of rendering. Set it to one of those two objects.
  • fieldSetApiName cannot be blank. A profile section with no field set errors on load. Always point it at a real field set on the chosen object.
  • Clearing a field to blank does not persist. Save skips fields whose value is null, along with calculated and formula fields. A member cannot use a profile section to empty out a value — the previous value remains.
  • Account sections are read-only for most members. Only the Account’s Primary Contact, Billing Contact, or a Person Account can edit an Account section. Other members see it read-only, and a save attempt throws an error. Use Contact sections for data every member should be able to edit.