This article explains why the Interaction Summary Lightning component or the Actionable Relationship Center (ARC) graph in Salesforce Financial Services Cloud (FSC) may not display correctly or may return access-related errors for some users.
Users may experience issues such as being unable to view, create, or edit Interaction Summary records, seeing a blank or incomplete ARC graph, receiving an access error, or noticing that the component displays differently compared to users with administrative access. In some cases, actions such as New may be unavailable, or the information displayed may differ between users.
These issues can occur in Lightning Experience across supported Salesforce editions with FSC enabled and are commonly caused by differences in user permissions, licenses, object or field access, sharing settings, or component configuration.
1. Missing Permission Set or Permission Set License
> Features like Interaction Summary and ARC are tied to specific FSC permission sets (such as Financial Services Cloud Basic or Financial Services Cloud Standard) and their associated Permission Set Licenses. If a user's profile doesn't include these, they simply won't see the component, records, or the New button — with no meaningful error message.
2. Missing Object or Field-Level Security (OLS/FLS)
> Even if the permission set is assigned, the user's profile or permission set may not grant Read (or Create/Edit) access to the Interaction Summary object or its key fields. This explains why some users in the same role have access while others don't.
3. "View data as an admin" component attribute is enabled
> If an admin has set the View data as an admin attribute on the Interaction Summary or ARC component in the Lightning App Builder, the component renders only for System Administrators. Non-admin users will see a blank or empty view with no error, which makes this particularly hard to diagnose.
4. ARC Relationship Graph configuration
The ARC component requires its own configuration — including defined relationship types and node access — before it renders correctly for non-admin users. If the relationship graph was configured while logged in as an admin and not tested as a standard user, gaps in visibility are expected.
005388246

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.