Use Sharing Sets with Contacts with Multiple Accounts (Beta)

Let’s say you create a community or portal user from a contact that is associated with multiple accounts. You can then create a sharing set that grants access to all records with a lookup to any account that contact is related to.

Where: This change applies to Lightning communities and Salesforce Tabs + Visualforce communities accessed through Lightning Experience and Salesforce Classic. This change applies to Enterprise, Essentials, Performance, Unlimited, and Developer editions.

Note

Note

As a beta feature, Sharing Sets for Contacts with Multiple Accounts is a preview and isn’t part of the “Services” under your master subscription agreement with Salesforce. Use this feature at your sole discretion, and make your purchase decisions only on the basis of generally available products and features. Salesforce doesn’t guarantee general availability of this feature within any particular time frame or at all, and we can discontinue it at any time. This feature is for evaluation purposes only, not for production use. It’s offered as is and isn’t supported, and Salesforce has no liability for any harm or damage arising out of or in connection with it. All restrictions, Salesforce reservation of rights, obligations concerning the Services, and terms for related Non-Salesforce Applications and Content apply equally to your use of this feature. You can provide feedback and suggestions for Sharing Sets for Contacts with Multiple Accounts in the IdeaExchange or the Sharing Sets for CMA group in the Trailblazer Community.

For information on enabling this feature in your org, contact Salesforce.

Who: Users with the following licenses can use sharing sets:
  • Customer Community Login User
  • Customer Community Plus and Partner Community Licenses
  • Customer Community User

How: In Setup, search for Communities Settings and create a sharing set. Under Configure Access, select Contact.RelatedAccount in the User dropdown list and Account in the Target Object field.