Contacts to Multiple Accounts

Why Contacts to Multiple Accounts Matters

In the real world, one person rarely belongs to only one organisation. A consultant may advise five companies, a physician may have admitting privileges at three hospitals, a board member may sit on several boards, and a franchise owner may operate multiple locations. Before this feature existed, administrators had two poor choices: create duplicate contact records (one per account) or shoehorn the relationship into a custom junction object that users found confusing. Both approaches fragment activity history, create data quality problems, and break reporting.

Contacts to Multiple Accounts solves this by letting a single contact record be associated with many accounts while still keeping exactly one primary account. For the Advanced Administrator exam, this topic sits inside the Advanced Security and Access and Data and Analytics Management areas because it touches on sharing behaviour, object relationships, page layouts, reporting, and data model design decisions. Expect scenario-based questions that test whether you can recognise when this feature is the right answer and whether you understand its limitations.

What Contacts to Multiple Accounts Is

Contacts to Multiple Accounts is a standard Salesforce feature (available in Group, Professional, Enterprise, Performance, Unlimited, and Developer editions, in both Lightning Experience and Salesforce Classic) that introduces a junction object called Account Contact Relationship (API name: AccountContactRelation). This object sits between Account and Contact and allows many-to-many relationships.

Key terminology you must know:

Direct relationship: The relationship between a contact and its primary account, defined by the standard Account Name (AccountId) lookup field on the Contact record. Every contact that is related to any account has exactly one direct relationship.

Indirect relationship: Any additional relationship between the contact and another account, stored as an Account Contact Relationship record. A contact can have unlimited indirect relationships.

Account Contact Relationship (ACR) record: The junction record that stores relationship details. Note that when the feature is enabled, Salesforce also creates an ACR record for the direct relationship, flagged with the Direct checkbox set to true, so that the Related Contacts list shows both direct and indirect contacts in one place.

How It Works

1. Enabling the feature
Go to Setup, search for Account Settings, and select Allow users to relate a contact to multiple accounts. Once enabled, Salesforce makes the Account Contact Relationship object available. Important: if you later disable the feature, all indirect relationships are permanently deleted. Direct relationships are unaffected. This is a classic exam trap.

2. Page layout configuration
Enabling the feature does not automatically change the user experience. The administrator must add two related lists:
- Related Contacts on the Account page layout (this replaces or supplements the standard Contacts related list and shows both direct and indirect contacts, with a Direct column and a Roles column).
- Related Accounts on the Contact page layout (shows all accounts the contact is related to).
If a question says that users enabled the feature but cannot see any way to add additional accounts to a contact, the answer is almost always that the related lists were not added to the page layouts.

3. Standard fields on Account Contact Relationship
- Account and Contact lookups
- Roles: a multi-select picklist (default values include Business User, Decision Maker, Economic Buyer, Economic Decision Maker, Evaluator, Executive Sponsor, Influencer, Technical Buyer, and Other). Administrators can add custom role values.
- Direct: a read-only checkbox that is true for the primary account relationship
- Start Date and End Date
- Active: a checkbox indicating whether the relationship is current
- Relationship Strength (when certain features are enabled)

4. Customisation capabilities
The Account Contact Relationship object supports custom fields, custom page layouts, validation rules, Apex triggers, and Flow automation. It does not support roll-up summary fields on the Account or Contact that summarise ACR records, and you cannot create custom report types with ACR as the primary object in all cases (you use the standard relationship report types instead). It also does not support its own sharing rules, record types, or field history tracking in the way most custom objects do. Remember the phrase: you can extend it, but you cannot share it independently.

5. Creating relationships
From the Related Contacts list on an account, a user can click Add Relationship to relate an existing contact (creating an indirect relationship) or create a new contact (which creates a direct relationship to that account). From the Related Accounts list on a contact, a user can add an indirect relationship to another account. A contact must already have a primary account before indirect relationships can be created; a private contact (no account) cannot be related to accounts indirectly.

6. Changing the primary account
When a user changes the Account Name field on a contact, the old direct relationship does not disappear. It is converted into an indirect relationship, and the new account becomes the direct relationship. Users can then remove the old indirect relationship if it is no longer relevant.

7. Deletion behaviour
- Deleting an account deletes the contacts that have it as their direct (primary) account, exactly as before the feature existed.
- Deleting an account also deletes all indirect relationship records pointing to it, but the related contacts themselves are not deleted because they live under a different primary account.
- Deleting a contact deletes all of its ACR records.
- You cannot remove a direct relationship from the Related Contacts list; you can only remove indirect ones. To change the direct relationship you must edit the Account Name field on the contact.

8. Sharing and visibility (the Advanced Security and Access angle)
This is the area where the exam goes deepest. The key principles are:
- Contact visibility is still governed by the Contact organisation-wide default (OWD), sharing rules, role hierarchy, and manual sharing, or by the primary account if Contact OWD is set to Controlled by Parent. Indirect relationships do not grant access to the contact. A user who can see an account will see the names of indirectly related contacts in the Related Contacts list only if they also have Read access to those contacts.
- To view an Account Contact Relationship record, a user needs Read access to both the account and the contact.
- To create or edit an indirect relationship, a user needs Edit access on the account and at least Read access on the contact.
- There are no sharing rules, manual shares, or OWD settings for the Account Contact Relationship object itself. Access is derived entirely from the parent records.
- Account Teams and Account sharing rules that grant contact access via the primary account apply only through the direct relationship, not through indirect ones.
If a scenario says that sales reps can see an indirectly related account but not the contact on it, check the Contact OWD and sharing model rather than looking for an ACR sharing setting that does not exist.

9. Activities, opportunities, and roll-ups
Activities (tasks and events) logged against a contact roll up to the contact's primary account only. They do not roll up to indirectly related accounts. Opportunity Contact Roles remain a separate mechanism; relating a contact to an account does not add them to any opportunity. The feature is about organisational affiliation, not deal participation.

10. Person Accounts
If Person Accounts are enabled, Account Settings offers additional options to relate person accounts to business accounts (for example, an individual who is an employee of a company) and to relate contacts to person accounts (for example, a household relationship). These relationships use the same Account Contact Relationship object.

11. Reporting
The standard Contacts and Accounts report type returns only direct relationships. To report on indirect relationships, use the report types that include Account Contact Relationships, such as Accounts with Related Contacts and Contacts with Related Accounts, or build a custom report type using Account Contact Relationship as a related object. List views on Contact cannot filter on indirect account relationships because the relationship lives on the junction object, not on the contact record.

12. Experience Cloud and external users
External users (customer and partner community users) can see related contacts and related accounts subject to their sharing access. For partner users, this can be useful for showing which partner contacts are associated with which end-customer accounts, but the same rule applies: access is derived from Read access to both parent records.

Common Use Cases the Exam Likes
- A consultant or contractor who works with several client companies
- A physician affiliated with multiple hospitals or clinics
- A board member or advisor connected to several organisations
- A franchise owner managing multiple franchise locations, each a separate account
- A parent related to multiple children who are each person accounts (education or healthcare)
- A procurement manager who buys on behalf of several subsidiaries that are modelled as separate accounts

Exam Tips: Answering Questions on Contacts to Multiple Accounts

Tip 1: Recognise the trigger phrases. When a scenario describes one individual who is associated with, works for, advises, or represents more than one company, and the business wants to avoid duplicate contacts, the answer is Contacts to Multiple Accounts. Phrases like without creating duplicate records, maintain a single contact record, or relate the same person to several accounts are strong signals.

Tip 2: Distinguish it from look-alike features.
- Account Hierarchy links accounts to other accounts (parent and child), not contacts to accounts.
- Account Teams and Opportunity Teams relate internal users to records, not external contacts.
- Opportunity Contact Roles relate contacts to a specific deal, not to an account.
- Person Accounts represent an individual as an account, not a contact with multiple affiliations.
- Duplicate Rules prevent duplicates but do not model many-to-many relationships.
If a distractor option proposes a custom junction object, remember that the standard feature is preferred because it is declarative, supported, and already integrated with the Related Contacts and Related Accounts lists.

Tip 3: Remember the one-primary rule. A contact always has exactly one direct (primary) account. Any answer that implies a contact can have two primary accounts or no primary account while having indirect relationships is wrong.

Tip 4: Know the setup steps in order. Enable the setting in Account Settings, then add the Related Contacts related list to the Account layout and the Related Accounts related list to the Contact layout. Optionally customise the Roles picklist and add custom fields to the Account Contact Relationship object. Questions that say the feature is enabled but users cannot see it are testing the page layout step.

Tip 5: Memorise the deletion and disable consequences. Disabling the feature deletes all indirect relationships. Deleting an account deletes its direct contacts but only removes indirect relationships, leaving indirectly related contacts intact. Changing a contact's primary account converts the old relationship to indirect.

Tip 6: Apply the sharing rule of thumb. There is no sharing model for the Account Contact Relationship object. To see a relationship, a user needs Read access to both the account and the contact. To create one, the user needs Edit on the account and Read on the contact. Indirect relationships never extend record access to the contact. When a question involves visibility problems, look at Contact OWD and sharing rules, not at the ACR object.

Tip 7: Watch for activity and roll-up traps. Activities roll up only to the primary account. Roll-up summary fields cannot be built on ACR records. If a scenario demands counting related contacts per account including indirect ones, the correct answer involves a report or Flow, not a roll-up summary field.

Tip 8: Choose the right report type. Standard Contacts and Accounts reports show direct relationships only. For indirect relationships, choose a report type built on Account Contact Relationships.

Tip 9: Read the edition and interface details. The feature works in both Lightning Experience and Classic and is available in Group edition and above. Any answer claiming it is Lightning-only or Enterprise-only is incorrect.

Tip 10: Eliminate overly complex answers. Advanced Administrator questions reward the simplest declarative solution that fully meets the requirement. If Contacts to Multiple Accounts satisfies the scenario, it beats custom objects, Apex, or duplicate records every time.

Quick Review Summary
- Feature name: Contacts to Multiple Accounts; object: Account Contact Relationship (AccountContactRelation)
- Enabled in Setup under Account Settings
- One direct (primary) account per contact; unlimited indirect accounts
- Related lists: Related Contacts (Account) and Related Accounts (Contact)
- Standard fields: Roles, Direct, Start Date, End Date, Active
- Supports custom fields, validation rules, triggers, and Flows; no roll-ups, no independent sharing
- Visibility requires Read on both account and contact; creation requires Edit on account
- Activities roll up to primary account only
- Disabling deletes all indirect relationships
- Use ACR-based report types for indirect relationship reporting

Master these points and you will be able to identify the feature in a scenario, configure it correctly, explain its sharing behaviour, and avoid the common distractors the exam uses.