Skip to main content
The FS Portal - Manage Benefits component (fs_portal_manageBenefits) lets a member assign the benefits of a subscription to other contacts on their account. It is part of the unmanaged Portal Components package (no namespace), so you can clone and customize it. The component reads the subscription it should work with from a record id in the page URL (?id=<Purchase Activity UUID>). Members reach this page from the Subscription Hub manage flow, which supplies that id automatically — so place the component on a dedicated page and point the hub’s allocation tile at it.
The rendered Manage Benefits page in the portal, showing the subscription product and dates, the allocation progress bar, a contact search, and a selectable list of account contacts with Back and Save buttons

The Manage Benefits page as a member sees it

​
Setting Up the Manage Benefits Component

1

Create the page

Make sure you have created a page for Manage Benefits.
2

Add the component

On the page, drag and drop the FS Portal - Manage Benefits component.
The FS Portal - Manage Benefits component placed on a portal page

The Manage Benefits component on a portal page

3

Publish

Click Publish to save your changes.
This page is required to use the benefit allocation functionality in the Subscription Hub. Point the hub’s Subscription Benefit Allocation Tile at this page so the Allocate Contacts action lands here.

​
Limitations and Common Pitfalls

  • The page needs a subscription id in the URL. The component loads the subscription from ?id=<Purchase Activity UUID>. The Subscription Hub passes this automatically; opening the page directly without an id leaves the component with nothing to display.
  • Members need both view and manage access. The component loads only for a contact whose role is in the subscription product’s Subscription Visibility (FS_PORTAL_Subscription_Visibility__c) and Manage Subscription (FS_PORTAL_Manage_Subscription__c) settings. Otherwise it reports that the member does not have access.
  • The account must have contacts. If the subscription’s account has no contacts, the component errors. Only contacts on the subscription’s account can be allocated benefits.