Shared Activities
A Shared Activity is a single task or event in Salesforce that is related to more than one contact at the same time.
Definition
A Shared Activity is a single task or event in Salesforce that is related to more than one contact at the same time. With the feature turned on, one meeting or call can link to up to 50 contacts and one lead, instead of forcing you to log a separate record for each person.
The feature exists because a real meeting usually has more than one attendee. Shared Activities keeps that reality in your data. One activity record shows up in the timeline, related lists, and reports for every contact it touches, so you do not lose history or count the same conversation many times.
How Shared Activities changes the way Salesforce stores a meeting
The problem it solves
Out of the box, a task or event can name only one contact in its Name field. That single link is the WhoId. If a rep runs a discovery call with five people from the same account, they have two bad options. They can log one activity and pick a single contact, which hides the other four attendees from history. Or they can create five near-identical activities, which inflates activity counts and makes reporting noisy. Neither choice reflects what actually happened in the room. Shared Activities removes that trade-off. After an admin enables the feature, reps relate up to 50 contacts and one lead to the same task or event. The activity then appears under Open Activities and Activity History on every related contact, not just the primary one. Managers reviewing account engagement see one clean record for the meeting, attributed to everyone who joined. This matters most for orgs that measure activity coverage, because accurate attendee data is the difference between trustworthy engagement metrics and guesswork.
Primary contact and the Name field
Even though many contacts can ride on one activity, Salesforce still designates one of them as the primary contact. The primary contact is what shows in the activity Name field, and it is what search and many list views filter on. Think of it as the headline attendee while the rest sit in a related list underneath. The primary contact is not just cosmetic. If a rep deletes the primary contact from the activity, Salesforce promotes the next contact on the related list to become the new primary automatically. The activity is never left without a primary as long as at least one contact remains. This behavior keeps older reports and integrations that read the Name field from breaking when the attendee list changes. A practical tip follows from this design. Choose the most important stakeholder as the primary contact when you log the meeting, because that name carries the most weight across summary views, the activity timeline header, and any process that still reads a single WhoId rather than the full attendee set.
TaskRelation and EventRelation under the hood
When Shared Activities is on, Salesforce stores the extra attendees in two junction objects. Tasks use TaskRelation and events use EventRelation. Each row links one activity to one related record, whether that record is a contact, the single allowed lead, or a what record like an account or opportunity. A field on these objects marks whether the related record is a who (a person) or a what (an object the activity is about), so one structure handles both attendee lists and parent records. These junction objects carry an important constraint that catches developers off guard. Once Shared Activities is enabled, TaskRelation and EventRelation do not support Apex triggers, workflow rules, or validation rules. You can still query them with SOQL and read them through the API, but you cannot fire automation directly when a relationship row is created or removed. If your design depends on reacting to an attendee being added, you plan around this by watching the parent Task or Event instead, or by querying the relation objects on a schedule. Change Data Capture does publish change events for these relationships, which gives near real time downstream sync without triggers.
Enabling it is effectively one way
An admin turns the feature on with a single checkbox in Activity Settings labeled Allow users to relate multiple contacts to events and tasks. The click is easy. The consequences are not trivial, which is why teams treat this as a one way decision. After you save the setting, Salesforce processes existing activities in the background. The work usually finishes within one to two hours, but it can take up to 48 hours or more in a large org. During that window you may see relationships still settling, so plan the change for a quiet period rather than the middle of a busy quarter close. The harder truth is on the reverse side. Disabling Shared Activities after reps have used it does not gracefully unwind the data. Every activity that has more than one related contact or lead loses all of those relationships except the primary record. That loss is permanent. Salesforce documentation steers you to contact Support before any disable attempt on an active org. For practical purposes, enable it once, early, and do not plan to turn it back off.
Reporting on who attended
The payoff for enabling Shared Activities shows up in reporting. Because each contact carries the shared task or event in its own activity history, you can build reports that show every person tied to a meeting, not just the headline name. The relevant report type is Activities with Contacts, which exposes the related contacts on each activity so coverage and frequency calculations include the full attendee list. This is where the feature earns its keep for revenue teams. You can answer questions that a single contact link cannot, such as how many distinct contacts in an account a rep has actually met with this quarter, or which decision makers have gone untouched. One caveat is worth setting expectations on. A shared activity related to several contacts is still one activity record. Some teams expect it to fan out into one row per contact in every report, and certain report types do not behave that way. Use the Activities with Contacts report type when you specifically need per contact attribution, and validate the row counts before you build dashboards on top of the numbers.
Limits and edge cases to remember
A few boundaries shape how you use the feature day to day. The hard ceiling is 50 contacts per activity, which is generous but real, so very large invite lists need to be trimmed or split. Only one lead can be related to a given activity, because leads are not designed for the same multi link treatment as contacts. If a meeting involves both leads and contacts, the contacts get the shared treatment and a single lead can ride along. Recurring tasks are the notable exception. You cannot relate multiple contacts to a recurring task, so a repeating to do that should involve several people needs a different approach, often individual activities or a non recurring task per occurrence. Email logging tools, calendar sync connectors, and managed packages also interact with TaskRelation and EventRelation, so when you evaluate an integration, confirm how it reads and writes the attendee list. Finally, remember that the primary contact still drives anything that reads a single Name value, so legacy automations and exports may only see one person unless you update them to read the full relation set.
How to enable Shared Activities
Shared Activities is enabled from Activity Settings in Setup. It is a single checkbox, but it is treated as a one way change, so confirm the timing and the consequences before you save. You need a profile with the Customize Application permission.
- Open Activity Settings
From Setup, type Activity Settings in the Quick Find box and select Activity Settings.
- Select the option
Check the box labeled Allow users to relate multiple contacts to events and tasks.
- Save and let it process
Click Submit. Salesforce processes existing activities in the background, usually within one to two hours but sometimes up to 48 hours.
- Add the related list
On Contact, Task, and Event page layouts, surface the related contacts list so reps can add and view attendees.
- Confirm reporting
Use the Activities with Contacts report type to check that activities now show every related contact, not just the primary.
The single setting that turns Shared Activities on across the org. Enabling it is effectively permanent.
The contact shown in the activity Name field. Deleting it promotes the next contact on the related list to primary.
Up to 50 contacts and 1 lead can be related to one task or event.
- Disabling the feature on an active org permanently drops every related contact except the primary one. Contact Salesforce Support first.
- TaskRelation and EventRelation do not support Apex triggers, workflow, or validation rules once Shared Activities is on. Plan automation around the parent Task or Event.
- You cannot relate multiple contacts to recurring tasks.
- Processing after enablement can take up to 48 hours, so schedule the change during a quiet window.
Trust & references
Cross-checked against the following references.
- Enable Shared ActivitiesSalesforce
- Considerations for Enabling Shared ActivitiesSalesforce
Straight from the source - Salesforce's reference material on Shared Activities.
Hands-on resources to go deeper on Shared Activities.
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What is Shared Activities?
Q2. How many contacts can share one activity?
Q3. Is enabling Shared Activities reversible?
Discussion
Loading discussion…