- Grant portal or community users access to records that are associated with their accounts or contacts using sharing sets.
- Sharing Sets are only available for Customer Community license
- Sharing sets can be used with these user profiles:
- Authenticated Website
- Customer Community User
- Customer Community Login User
- High Volume Customer Portal
- High Volume Portal
- Overage Authenticated Website User
- Overage High Volume Customer Portal User
Example 1: You might want to use a sharing set if you would like to:
- Grant users access to all cases related to their account or contact record.
- Grant users access to all cases related to a parent account or contact that is identified on the user’s account or contact record.
Example 2: shows an access mapping on a sharing set, which grants portal or community users access to all cases associated with the entitlements on their account, even if they are not directly associated with the case.
- Account lookup on portal or community user
- Related account on entitlement
- Entitlement lookup on case
- I want to give all Community users related to Acme access to Projects that are related to Acme. I build a simple sharing set for this. However, some of these Community users also need manual sharing.
Solution: Important note is that Partner license has roles and sharing rules available but basic Customer license does not. Likewise, Apex sharing and manual sharing are not available for Customer license. I need to now separately write and maintain an Apex trigger to share the Projects related to Acme with the Acme Partner Community Users.
- Acme has a Parent Account: Acme HQ. I want all Community users related to Acme HQ to have access to Projects related to Acme HQ or to Acme.
Solution: If these include Partner Community users, I need to add more logic to my Project sharing trigger to additionally share it with Acme HQ users.
- I want to give Community users access to another object–Widgets–related to (but not child to) Projects.
Solution: Now I need another sharing trigger on the Widget object, whereas I could have solved this with a simple Sharing Set if this feature were available for Partner Community licenses.