Skip to main content
Conga Support

Implications of Enabling Shared Contacts

The Shared Contacts feature allows users to relate a single Contact to multiple Accounts (households, businesses, etc.). Formerly, users would have to create duplicate Contacts to accomplish this same goal. With this new feature, each contact still has a primary account, but its other accounts become indirect relationships.

So what are the implications here?

How Shared Contacts Affect Activities

There are several ramifications of the Shared Contacts feature, but the one we’ll address in this post primarily relates to Activities. If you use Salesforce Tasks for workflows, you are likely used to relating a Task to a Contact (via the Name field) and then viewing those activities on that Contact’s Account. (Conga Orchestrate uses the Task’s Related To field to link it to a specific process object.) This is Salesforce’s default behavior — rolling those activities up to the Contact’s Account automatically for easy viewing.

Per Salesforce documentation:

“By default, the Related To field on an activity determines which account the activity appears on. Often that account ends up being the contact’s primary account, but this behavior doesn’t always make the most sense. For example, if users can relate a contact to multiple accounts, the contact’s primary account isn’t always relevant to the activity. It might make more sense for the activity to appear on one of the contact’s secondary, or indirect, accounts. You can turn off this default roll up behavior from the Activities Settings page, but be aware of the implications.”

So associating a Contact to many Accounts causes all of those activities to show on that Contact’s primary Account even if the activity doesn’t seem to logically belong there. In this case, users may think there are too many activities displayed.

For users who disable this roll-up behavior, the Contact’s activities will no longer show at the Account level. Here, users may miss seeing those activities.

Correctly Associating Tasks

We have a couple potential solutions. If the default roll-up behavior is enabled, we can use a formula field to help distinguish tasks that are associated with the primary Account from those that are not.

If the roll-up behavior is disabled, we recommend a solution using a custom Account lookup field that will allow only that Account’s activities to display in a separate related list.