ARC requires both a configured Relationship Graph metadata record and a page-layout placement. The configuration takes about an hour for a first graph; subsequent graphs reuse most of the work.
- Assign the Industries permission set
Setup, Permission Sets. Find the relevant Industries permission set (Financial Services Cloud Standard, Health Cloud, etc.) and assign it to users who should configure or view ARC.
- Open the ARC Configurator
Setup, search for ARC Configurator, then create a new Relationship Graph. Name it after the use case (e.g. Household Graph, Care Team Graph).
- Define nodes and edges
Add the central object as the root node. Add related objects as nodes and define each edge: lookup, indirect (ACR), reverse, or junction. Keep depth shallow on the first pass; you can extend later.
- Configure card content and actions
For each node, pick which fields to display on the card and which Lightning Quick Actions to expose on hover. The Quick Actions must already exist on the object.
- Drop the ARC component on the Lightning record page
App Builder, edit the Lightning record page for the central object, add the Actionable Relationship Center component, and bind it to the Relationship Graph created above. Save and activate the page.
- ARC requires the Industries permission set licence. Users without it will not see the component, even in App Builder.
- Wide or deep graphs can blow the page-load budget. Keep depth shallow; build one graph per use case rather than one mega-graph.
- Quick Actions shown in ARC are the standard Lightning Quick Actions on the object. Removing a Quick Action elsewhere also removes it from ARC.
- Indirect relationships through Account Contact Relationship only show up if the multi-Account contacts feature is enabled. ARC does not work around that setting.