A financial services firm wants to enable self-service support for policyholders using an Experience Cloud site built on the Customer Service template. Policyholders holding standard Customer Community licenses need to view and manage cases associated with their personal contact record. Currently, the organization's internal sharing model for Cases is set to Private, and internal visibility must remain restricted.
Which two configuration actions should the administrator perform to fulfill these security and access requirements?
- Set the External Organization-Wide Default (OWD) for Cases to Private.Cevap
- Create a Sharing Set that maps the User's Contact to the Contact on the Case object.Cevap
- CCreate a custom profile for external policyholders and grant 'View All' permissions on the Case object.
- DEnable 'Grant Access Using Hierarchies' on the Case object within External Sharing Options.
- EChange the internal Organization-Wide Default for Cases to Public Read-Only.
Cevap
The administrator should set the External Organization-Wide Default (OWD) for Cases to Private and create a Sharing Set that maps the User's Contact record to the Contact field on Case records.
To grant Customer Community users access to their own cases while keeping internal and external access restricted, the administrator must establish an External Organization-Wide Default of Private for Case. Because standard Customer Community users do not have roles, traditional sharing rules do not apply; instead, a Sharing Set must be used to map user attributes (User.Contact) to record attributes (Case.Contact).
Adım Adım Çözüm
Anahtar Kavram
Experience Cloud External Sharing Models and Sharing Sets for High-Volume Portal Licenses