Account Contact Relationship
An Account Contact Relationship in Salesforce (AccountContactRelation in the API) is a standard junction object that links a Contact to multiple Accounts beyond the Contact's single primary AccountId.
Definition
An Account Contact Relationship in Salesforce (AccountContactRelation in the API) is a standard junction object that links a Contact to multiple Accounts beyond the Contact's single primary AccountId. Each Account Contact Relationship holds a ContactId, an AccountId, an IsActive flag, an IsDirect flag (true for the Contact's primary Account, false for secondary relationships), a Roles multi-select picklist, an optional StartDate and EndDate, and Org-wide-default sharing inherited from the parent records. This object solves the long-standing limitation that a Contact can have only one primary Account: with Account Contact Relationships enabled, a single Contact (for example, a board member who serves on the boards of three different organizations) can be related to multiple Accounts simultaneously, each with its own role and active period. Salesforce automatically creates one direct Account Contact Relationship for the Contact's primary AccountId; admins or users add additional indirect relationships as needed. The object is foundational to Salesforce industry clouds (Financial Services Cloud, Health Cloud, Nonprofit Cloud) where person-to-organization relationships are routinely many-to-many.
In plain English
“An Account Contact Relationship lets one person (a Contact) be linked to several companies (Accounts) at once. By default, a Contact only belongs to one Account, but board members, consultants, and split-affiliation people often work for multiple organizations — this junction object captures all of those affiliations with a role and date range for each.”
Worked example
A consultant named Priya works directly for ConsultCo (her primary employer) but also serves on the advisory board of two startups, FinTechCo and HealthCo. In Salesforce, Priya is a single Contact with her primary AccountId set to ConsultCo, which automatically creates a direct Account Contact Relationship. The admin then adds two indirect Account Contact Relationships: one linking Priya to FinTechCo with Role = "Advisor" and Active = true, and one linking her to HealthCo with Role = "Board Member". When a sales rep at the company looks up FinTechCo, Priya appears in the Related Contacts list with her advisor role displayed. When Priya leaves FinTechCo's board two years later, the admin sets that Account Contact Relationship's IsActive to false rather than deleting it, preserving the historical affiliation.
Why Account Contact Relationship matters
The Account Contact Relationship object is enabled by default in modern orgs but historically required an explicit setting toggle (Setup > Account Settings > Allow users to relate a contact to multiple accounts). Once enabled, every Contact automatically gets one direct Account Contact Relationship for its primary AccountId, with IsDirect = true. Admins cannot delete or significantly alter this direct relationship — it is system-managed and synced with the Contact's AccountId field. Indirect relationships (IsDirect = false) are user-created and freely editable.
Account Contact Relationships have their own sharing model and their own page layout. Visibility rules combine the parent Contact and parent Account access — a user must be able to see both records to see the relationship between them. Custom fields on Account Contact Relationship are common (relationship type, ownership percentage, referral source) and are reportable through a dedicated Account Contact Relationships report type.
In Person Account orgs, Account Contact Relationships behave somewhat differently because every Person Account is both an Account and a Contact. Person-to-Person relationships are typically modeled through a separate Contact Contact Relationship object (in Financial Services Cloud) or through industry-cloud-specific junctions, not through Account Contact Relationship. Mixing Person Accounts and Business Account relationships in the same data model requires careful planning to avoid duplicate or contradictory affiliations.
How organizations use Account Contact Relationship
Tracks which procurement contact at a parent corporation also has buying authority at three subsidiary entities. One Contact is linked to four Accounts through Account Contact Relationships, each with its own role and access scope, so each subsidiary's account team sees the same person without creating duplicate Contact records.
Models a single financial advisor who manages relationships with multiple client households. Each household is an Account, and the advisor Contact links to all of them through Account Contact Relationships with different role values (primary advisor, secondary, in-transition), driving service ownership and commission attribution.
Captures an alumnus's affiliations with multiple campus organizations — fraternity, sports team, donor circle, alumni board — by creating one indirect Account Contact Relationship per affiliation with start and end dates that reflect their tenure with each group, supporting accurate engagement reporting and event-targeting.
Trust & references
Straight from the source — Salesforce's reference material on Account Contact Relationship.
Discussion
Loading discussion…