Sharing sets and share groups for patient and member site users
Key Takeaway
A sharing set gives high-volume users access to records. A share group lets other users see the records that high-volume users own.
In Agentforce Health, patients and members use a private Experience Cloud site. Unlike other users, site users with high-volume licenses have no roles, so role hierarchies, public groups and owner-based sharing rules don't work for them. So you use a sharing set to give them access to records linked to their own account or contact, and a share group to let other users see the records they own.
Who high-volume users are
A high-volume user holds one of these licenses:
- External Apps
- Customer Community
- High Volume Customer Portal
- Authenticated Website
Having no roles removes the performance cost of role hierarchy calculations.
The built-in record access of high-volume users is narrow:
- They see their own account and contact through implicit sharing.
- They get Read access to the account they belong to.
- They can reach records whose org-wide default is Controlled by Parent, through the parent.
- They can reach objects whose org-wide default is Public Read Only or Public Read/Write.