Unified Client Profiles in Salesforce FSC: How Customer 360 Actually Works
Person Accounts, Households, ARC graphs, Rollups, Timeline — a technical breakdown of every layer that builds the FSC client profile, and what admins and developers need to configure each one.
Why the Client Profile Matters
In a standard Salesforce org, customer data lives in Accounts and Contacts — two separate objects with a simple lookup relationship. That works fine for most B2B sales motions. But financial services operate differently. A single client may hold multiple bank accounts, belong to a household with shared financial goals, have relationships with lawyers, accountants, and advisors, and carry life events (marriage, retirement, inheritance) that trigger product opportunities.
The FSC Unified Client Profile is Salesforce’s answer to this complexity. It is not a single feature — it is an architecture. It combines an extended data model, relationship objects, aggregation logic, and a stack of Lightning components that together render a true 360-degree view of a financial client. Understanding how these layers connect is essential for anyone administering, developing on, or certifying in Financial Services Cloud.
Person Accounts vs. Individual Model
The very first architectural decision in any FSC implementation is how you will represent a person. FSC supports two approaches, but only one is recommended for new implementations.
Person Accounts
Combines account and contact fields into a single object experience. To end users, a person account record appears and functions as a single record.
- Uses the standard Account object extended with custom fields and record types
- Enabled by default in FSC trial orgs and new installations
- Better support for B2C activities
- Related to opportunities, cases, events, tasks, and calls
- Supports Person Account and Institutional record types
Individual Model
Uses a combination of separate Account and Contact objects, coupled in a unified object view through a Primary Contact field.
- Creates both an account and contact record when you create an individual
- Supported only for legacy FSC orgs with existing implementations
- Can surface as “duplicate” records in global search and list views
- Cannot have required fields on the Contact object
- Migration path to Person Accounts is available
Prerequisites for Person Accounts
Before enabling Person Accounts, admins must create a Use Person Account custom setting (singular — not “Use Person Accounts”). After enabling, remove all Individual record type assignments from profiles and enable person account record types for relevant profiles. Do not deactivate the Individual record type for Account or Contact — just remove the assignments.
Groups and Households
Once you have clients modeled as person accounts, the next layer is organizing them into groups. In FSC, a group is a collection of individuals whose relationships and shared attributes are important to how you serve them. The most common group type is a Household, but you can create custom group types (trusts, partnerships, business entities) to fit your needs.
FSC uses Party Relationship Groups to organize members under a household and to connect related households or associated business accounts. A group is modeled as a type of account record (with a Household record type), and people and businesses are related to it through the Account Contact Relationship object.
What Lives on a Group Record
Each group member has a role within the household — Client, Spouse, Dependent, or a custom role you define. One member is designated as the Primary Member, and each member can have a Primary Group setting that controls which household their data rolls up to. Related contacts (lawyers, accountants, tax planners) and related accounts (businesses, trusts) can also be associated with the household without being full members.
Modeling Relationships
Beyond grouping clients into households, FSC models one-to-one relationships between people and businesses. These relationship objects help advisors and bankers understand spheres of influence, professional connections, and organizational affiliations.
| Relationship Object | What It Connects | Association Types |
|---|---|---|
| Account-Contact Relationship | A person to an organization (or household) | Roles like Client, Spouse, Dependent; supports Primary Group and Rollup settings |
| Account-Account Relationship | An organization to another organization | Group (parent-subsidiary), Member (e.g., trust holding assets), Peer (non-hierarchical partner) |
| Contact-Contact Relationship | A person to another person | Custom roles with reciprocal role mapping (e.g., Advisor/Client, Spouse/Spouse) |
Each relationship type supports Reciprocal Roles — when you create a relationship from Person A to Person B as “Advisor,” FSC automatically creates the inverse relationship from Person B to Person A as “Client.” This is stored in the InverseRole__c field on the Reciprocal Role object.
Actionable Relationship Center (ARC)
ARC is the visual engine that brings all of these relationships to life. It renders interactive, navigable graph visualizations of how clients, households, businesses, and related parties are connected — directly on Lightning record pages.
Two Versions of ARC
FSC ships two versions. The New ARC (introduced Summer ’22) lets admins build custom relationship graphs using the ARC Relationship Graph component, ARC Details Panel, ARC Highlights Panel, and ARC Einstein Relationship Insights component. The Original ARC uses the ARC Financial Services Cloud component and provides preconfigured, view-only graphs. Both versions use the same permission set.
How Admins Configure ARC Graphs
Admins create graphs in Setup under Actionable Relationship Center. Each graph starts with a root node (typically Account or Contact) and branches into child nodes that represent related objects. For each node, you configure the object, relationship type (Lookup, Many-to-Many), junction object, lookup fields, and filter criteria. You then configure the Display tab (which fields appear on the card) and Actions tab (which record actions users can perform).
FSC also provides preconfigured templates: a B2C Graph that shows members, related households, and household accounts, and a B2B Graph that shows subsidiaries, employees, opportunities, and cases. These templates can be used as starting points and customized further.
Group, Member, and Peer.
ARC Node Types in FSC
| Node Type | Purpose | Root Node Object |
|---|---|---|
| Group Relationships | Shows accounts contained within a parent account (e.g., subsidiaries) | Account |
| Related Accounts | Shows non-hierarchical account associations (e.g., peer businesses) | Account |
| Member Relationships | Shows accounts tied to a parent (e.g., trusts holding assets) | Account |
| Members | Shows person accounts fulfilling roles for an account (e.g., household members) | Account |
| Related Contacts | Shows contacts fulfilling roles for a person (e.g., advisor, lawyer) | Contact |
| Household | Shows household accounts a person belongs to | Contact |
Record Rollups
Rollups are the aggregation layer that makes the household view meaningful. They pull related records from individual members and display them at the group level, giving advisors and bankers a consolidated financial picture of an entire household.
Client-level rollups work by default — no setup required. Group-level rollups must be explicitly enabled, and when you do, all corresponding records are stamped with the Primary Group in the Household__c lookup field.
Objects Supported by Group-Level Rollups
Group-level rollups aggregate data across Financial Accounts, Financial Goals, Assets and Liabilities, Referrals, Events, Tasks, Opportunities, Cases, Claims, Claim Participants, Insurance Policies, and Insurance Policy Participants. Not all objects are enabled for group-level rollups by default — for insurance-related objects, cases, opportunities, and referrals, admins may need to add picklist values to the Rollups__c field on the Account Contact Relationship object.
Household__c field after enabling group-level rollups. Any modification to this field can cause inconsistent rollup data across the household.
Profile Lightning Components
The client profile is not a single page — it is an assembly of Lightning components that admins configure on record pages using Lightning App Builder. Each component surfaces a different dimension of the client’s 360-degree view.
Timeline Configuration
Timeline is enabled once per org and cannot be disabled after activation. Admins create timeline configurations by selecting a base object (like Account) and adding up to five related objects per base object. For each related object, you configure the Title, Subtitle, Timestamp, and Summary fields that appear on the timeline. If the base object is Account, the component can also show the age of the customer at the time each event occurred by referencing the Birthdate field.
Events and Milestones
The Events and Milestones component shows Person Life Events on person account and contact pages, and Business Milestones on account pages. Admins can create custom event types and milestone types, mark certain event types as unique (for once-in-a-lifetime events like birth), hide sensitive event types, and configure contextual actions that trigger from specific events. The hover card (expanded lookup card) is customizable through compact layouts.
Financial Accounts Layer
The financial accounts layer models the actual products a client holds — bank accounts, investment accounts, insurance policies, and loan accounts. FSC provides this through two paths: standard objects (available without the managed package) and managed package objects.
The standard Financial Account object is the central record, and each financial account must have at least one active Financial Account Role with the type Primary Owner — otherwise data loading errors can occur. Financial Holdings track individual positions within investment accounts. The FSCFinancialAccountsSummary component gives service agents a consolidated view of all financial accounts, transactions, and record alerts for a client in a single component.
For orgs using the standard console apps, the Financial Account Management Standard Objects setting must be enabled in Setup. This setting activates the standard financial account objects for use within the Retail Banking, Wealth Management, and Commercial Banking console apps.
Admin Setup Checklist
Here is the recommended sequence for setting up the unified client profile in a new FSC org:
| Step | Action | Where |
|---|---|---|
| 1 | Enable the Contacts to Multiple Accounts feature | Setup → Account Settings |
| 2 | Enable and configure Person Accounts | Setup → Custom Settings → Use Person Account |
| 3 | Create user profiles (clone Standard User for Advisor, Personal Banker, etc.) | Setup → Profiles |
| 4 | Enable Financial Account Management Standard Objects | Setup → Financial Account Management |
| 5 | Set up ARC permissions and create relationship graphs | Setup → Actionable Relationship Center |
| 6 | Enable group-level rollups (if using households) | Setup → Record Rollup Settings |
| 7 | Enable Timeline and configure related objects | Setup → Timeline |
| 8 | Add Events and Milestones related lists and components to page layouts | Lightning App Builder |
| 9 | Enable and configure Interaction Summary settings | Setup → Interaction Summary Settings |
| 10 | Assemble the client profile page by adding components in Lightning App Builder | Lightning App Builder → Record Page |