Discover Group Membership

Note Group Membership is different from the Householding feature, which is used in other Industries clouds such as Financial Services Cloud and Health Cloud. Net Zero Cloud uses only a subset of the Group Membership objects. Refer to these clouds’ documentation for more information.

A group is a collection of individuals whose relationships and shared attributes are important to how you serve them. For example, a group could consist of a household with family members and their relationships to professional service providers.

You can also use groups to organize individuals in other contexts, such as:

• Members of a professional or trade association
• Individuals who live in the same building or housing complex
• Your top customers or supporters

Consider a two-person household with a relationship to a business. Sam and Leah Mason are married, share a household, and use the financial advisory services of Cumulus Cloud Bank. Here's how you model the relationships between Sam, Leah, and Cumulus Cloud Bank by using the group membership objects.

Let’s explore what each object represents in this example.

Note In Salesforce Help and other documentation, the word account by itself always refers to both business accounts and person accounts. We use the terms business accounts and person accounts when there are differences between the two types of accounts.

Business Account

Represents groups or organizations. In this example, one business account represents the Mason household, and the other business account represents Cumulus Cloud Bank. Business accounts can also represent a neighborhood, professional association, or another organization.

Party Relationship Group 

Designates a business account as a household or group and stores details about that group, such as its financial information. In this example, a household party relationship group relates to the Mason household business account to designate it a household and store details about its finances.

Person Account 

Represents individuals. Enabling person accounts is required to use the Group Membership guided flows. In this example, Sam and Leah each have a person account that contains both account and contact details.

Account Contact Relationship 

Relates a person account and a business account. In this example, Sam and Leah each have an account-contact relationship that connects their person accounts to their Mason household business account.

Contact Contact Relationship 

Relates person accounts to each other. Use two contact-contact relationships to map an inverse relationship, such as spouses. In this example, two contact-contact relationships connect Sam and Leah's person accounts. 

Account Account Relationship 

Relates business accounts to each other. Use two account-account relationships to map an inverse relationship, such as a customer and a business. In this example, two account-account relationships connect the Mason household business account with Cumulus Cloud Bank's business account. 

Party Role Relationship 

Describes account-account and contact-contact relationships. In this example, two party role relationships related to Sam and Leah's contact-contact relationships describe their relationship as Spouse-Spouse. In addition, Client-Advisor and the inverse Advisor-Client party role relationships describe the Mason Household and Cumulus Cloud Bank account-account relationships.