Salesforce Decode
Salesforcedecode
Back to questions
Financial Services CloudArchitect (Hardest)householdrelationship-groupsfsc

Design household and relationship group architecture in FSC

Real World Scenario

A wealth management firm serves families with multiple generations, trusts, and business entities. Advisors need unified household view while respecting privacy between family branches.

Expected Answer

• Use Account Account Relationship and Contact Contact Relationship for non-traditional hierarchies • Household record or Relationship Group bundling members with roles Primary Member Spouse Dependent • Roll-up financial metrics at household level for AUM and revenue reporting • Sharing via Relationship Group member access not overly broad OWD • Separate households when divorce or legal partition requires data isolation • Integration MDM golden household key mapped to FSC Relationship Group • Advisor book assignment at household grain not only primary Contact

Follow-Up Questions & Answers

Click to expand — each follow-up includes a direct, interview-ready answer

Main difference: use case and scale. Use Account Account Relationship and Contact Contact Relationship for non-traditional hierarchies. Household record or Relationship Group bundling members with roles Primary Member Spouse Dependent. Pick based on your integration pattern and team capability. FSC household is relationship graph not Account tree—architect role-based visibility before loading data. Document the decision in an ADR and align with enterprise standards.

Architect Perspective

FSC household is relationship graph not Account tree—architect role-based visibility before loading data.