You are here:
Define Groups and Relationships Between Individuals and Groups
Set up details about the types of groups and relationships common to your organization. To describe groups with greater nuance, use categories and subtypes. Create common role and relationship definitions for contacts and accounts.
Required Editions
| Available in: View supported product editions. |
| User Permissions Needed | |
|---|---|
| To edit picklists: | Customize Application |
| To create party role relationships: | View permissions information. |
Define Group Categories and Subtypes
Party relationship groups designate a business account as a household or a group, which you select from the object's Type field. To further categorize groups, create values for the Category and Subtype picklists. These fields help you report on different classifications of groups and better understand group relationships.
- From the object management settings for party relationship groups, go to Fields & Relationships.
- Click Category.
- In Category Picklist Values, click New.
- On separate lines, enter the values for the picklist. For example, enter Live Together and Eat Meals Together.
- Save your changes.
- Repeat these steps to create values for the Subtype picklist field. For example, create the Subtype values Nuclear Family and Extended Family.
Define Roles for Individuals in Groups
Use the Role field on an account-contact relationship to describe an individual’s relationship to a group or organization. Create picklist values to suit your needs.
- From the object management settings for account contact relationship, go to Fields & Relationships.
- Click Roles.
- In Roles Picklist Values, click New.
- On separate lines, enter the values for the picklist. For example, enter Primary Advisor and Preferred Technician.
- Save your changes.
Define Relationships Between Individuals and Relationships Between Groups
Party role relationships describe relationships between two accounts or between two contacts. Create and maintain party role relationships that describe the relationships between individuals, organizations, households, and groups.
Some party role relationships require inverse records to represent both sides of a relationship. Mapping an inverse relationship is optional but helpful to capture different transactions between parties and review a relationship from either party’s record page. For example, create inverse party role relationships for parent-child relationships in a household, or for a vehicle repair shop and the vehicle owner’s household. In the parent-child example, create a parent-child party role relationship, and a child-parent party role relationship to map the relationship in both directions. Both of these party role relationships can be created at the same time by selecting Create Inverse Role Automatically.
Other relationships, such as the relationship between colleagues or neighbors, don’t require inverse party role relationships. In these situations, you need only one party relationship role, because a colleague-colleague or neighbor-neighbor party role relationship represents both sides of the relationship.
- From the App Launcher, find and select Party Role Relationships.
- Click New.
- Enter a role name, such as Father or Parent Company.
- Enter a related role name, such as Daughter or Subsidiary Company.
- Select a relationship object name. For a father-daughter relationship, for example, select Contact Contact Relationship. For a parent-subsidiary relationship, select Account Account Relationship.
- To create the inverse role relationship (of daughter-father, in our example), select Create Inverse Role Automatically.
- Save your changes.
