A hotel group has implemented a Loyalty Member Portal for its program members, but some members are experiencing issues accessing their Loyalty…

For a loyalty program member to access their specific records in an Experience Cloud portal, two key configurations are required. First, the member's Contact record must be enabled as an Experience Cloud user (typically a Customer User), which creates the user record and allows them to log in. This is a foundational requirement for any portal access. Second, because external users have a restrictive data sharing model, a Sharing Set must be configured. A Sharing Set grants users access to records (like Loyalty Program Member, Transaction Journals, etc.) that are associated with their Account or Contact, which is essential for them to view their own loyalty data.

B. This setting is for self-registration and user creation, defining which profiles can be used. It does not affect record access for existing, logged-in users.

C. This option is confusingly worded and incomplete. You enable a Contact as a "Customer User," not an Account. Option D is more accurate and comprehensive.

E. Similar to option B, this setting governs the self-registration process and does not resolve record visibility issues for already-created portal members.

1. Salesforce Help, Give Your Members Access to Loyalty Program Data: This document explicitly states, "To give your members access to their loyalty program data, create sharing sets. Sharing sets give site users access to records that are associated with their accounts or contacts based on their user profiles." This directly supports option A.

2. Salesforce Help, Create a Loyalty Program Member: In the procedure for creating members, a critical step is noted: "To enable the member to log in to the member portal, enable the member's contact record as a customer user." This directly supports the necessity of the action described in option D.

3. Salesforce Help, Control Access to Records Using Sharing Sets: This guide details the function of sharing sets for Experience Cloud sites, explaining they are used to "grant site users access to records that are associated with their accounts or contacts based on their user profiles." This reinforces the rationale for option A as the solution for record-level access.