Setting up Relationship Group Members in Financial Services Cloud spans creating the Relationship Group, adding individual Members with roles, configuring rollups, and establishing the privacy controls. The walkthrough below covers the standard sequence for a typical wealth management household setup.
- Create the Relationship Group Account
From the Accounts tab, create a new Account with the Relationship Group record type. Enter the household name (typically the surname followed by Household, like Smith Household). Assign the primary advisor and any specialists. Save the record. Verify the household page layout shows the Members related list and the rollup fields for assets, revenue, and other aggregated metrics.
- Add Members with roles
From the Members related list, add each Contact or Account that belongs to the household. Set the Role for each Member: Primary Member for the lead client, Spouse for their partner, Child for dependents, and so on. Set the effective date if the relationship has a specific start. Save each Member record. The household page should now show the family structure with each role visible.
- Configure privacy and visibility
For each Member, configure the privacy settings: which information is visible at the household level versus restricted to specific individuals. Default settings work for most households; sensitive scenarios (children, complex families) require explicit configuration. Train the advisor on the privacy settings so they respect each Member's preferences when reviewing household data or generating reports.
- Validate rollups and reporting
Add sample financial data to each Member: investment accounts, insurance policies, banking relationships. Confirm the household-level rollup fields aggregate correctly. Test reports filtered by household and by individual to confirm both views work. Spot-check the privacy settings by impersonating a member to confirm they see only what they should. Iterate on the configuration based on what the validation reveals.
Required for the FSC-specific objects, record types, and features including Relationship Groups.
The parent Account record with the Relationship Group record type that anchors the household.
The role values that describe each member's relationship to the household, configured as picklist values or custom values.
The Apex triggers or Flow automation that maintains household-level rollup fields.
Per-member visibility configuration that respects each member's privacy preferences within the household.
- Compliance reporting is still per individual, not per household. The household view is for advisor productivity, not for regulatory submission.
- Household changes (divorce, death, marriage) have data implications that the standard model may not handle without custom logic.
- Privacy settings are easy to skip during initial setup. Skipping them creates household views that expose information members did not consent to share.
- Rollup logic for complex households (nested groups, cross-household relationships) often requires custom code. Plan for it during initial data model design.
- Cross-household relationships (trusts, partnerships, blended families) need explicit modeling. The default single-household structure does not handle them.