Multi-Person Event
A Multi-Person Event in Salesforce is a calendar Event that has more than one person attached to it, beyond just the organizer who owns it.
Definition
A Multi-Person Event in Salesforce is a calendar Event that has more than one person attached to it, beyond just the organizer who owns it. Each invited person, whether an internal user, a contact, or a lead, gets stored on a related EventRelation record. That child record holds the invitee's identity and tracks whether they accepted, declined, or have not yet responded. The parent Event still carries the subject, the start and end times, the location, and the description.
This is how Salesforce represents real meetings with several attendees, such as a sales rep sitting down with a buying committee, an account team kickoff, or a quarterly business review with a client. The model is built on the standard Event and EventRelation objects, so the attendee list is queryable, reportable, and syncable. Email and calendar integrations like Einstein Activity Capture can also create these events automatically when a user schedules a multi-attendee meeting in Outlook or Gmail, pulling the attendee list and response data back into Salesforce.
How Salesforce stores attendees and their responses
The Event and EventRelation object pair
A Multi-Person Event is not a separate object type. It is a regular Event record that happens to have several EventRelation children. The Event holds the shared meeting details: subject, start time, end time, all-day flag, location, and description. Salesforce documentation describes EventRelation as a person (a user, lead, or contact) or a resource, such as a conference room, that is invited to an event. One Event can have many EventRelation rows, which is what makes the attendee list possible. Each EventRelation row points back to its Event through EventId and to the invited record through RelationId. A flag called IsInvitee marks whether that row is an actual attendee versus a plain relationship, and IsWhat separates people from related business records. When you open an event in the UI and see a list of attendees with green, red, or grey status icons, you are looking at a rendered view of those EventRelation rows. Querying EventRelation directly is the cleanest way to pull a full attendee roster with responses for a given meeting.
Internal users versus external contacts and leads
EventRelation can point at three kinds of people, and the kind matters. An internal Salesforce user is invited as a colleague, and the event lands on that user's own Salesforce calendar. A contact or a lead is an external attendee, someone outside your org who is not a licensed user. Both paths produce EventRelation rows, but the notification mechanics differ. Internal users see the meeting inside Salesforce and can respond there. External contacts and leads are reached by email invitation when that capability is turned on, and their replies feed the response status back. Because the records being linked are different objects, access rules apply differently too. Salesforce notes that once you add other attendees to an event, the Assigned To field becomes read-only, since the assigned user might not have access to every contact or lead tied to the invitees. Keeping internal and external attendees clear in your head helps when you debug why one person got a calendar entry and another got an email.
Reading response status: accepted, declined, undecided
Every invitee carries a response that the organizer can see at a glance. Salesforce exposes this through filtered views of EventRelation. AcceptedEventRelation represents participants whose status is Accepted for a given event. DeclinedEventRelation represents the ones who said no. UndecidedEventRelation covers those who have not answered yet. These are not new tables you maintain. They are read paths into the same underlying invitee data, sliced by response. For a single meeting, the organizer just reads the attendee panel. The real value shows up at scale. A sales operations analyst can report across thousands of EventRelation rows to measure meeting acceptance rate, no-show patterns, and per-rep meeting volume. Those numbers often correlate with pipeline health, so they are worth tracking. One caution: response data is only as good as the invite path. If an event was logged manually rather than sent as a true invitation, the status may sit at the default and never update, which can skew a report if you do not filter for it.
Shared Activities and the multi-contact limit
Before you can relate several contacts to one event, an org setting has to allow it. The setting is Shared Activities, enabled under Activity Settings with the option labeled Allow users to relate multiple contacts to events and tasks. Once it is on, a user can relate up to 50 contacts to a single event or task, but only one lead. Without Shared Activities, an event links to a single primary contact or lead through the Name (Who) field, which is too thin for a real multi-attendee meeting. This setting is famously one-directional. Salesforce lets you enable it, but turning it back off is not a casual toggle, so treat the decision as permanent and switch it on early in an org's life. The 50-contact ceiling is generous for normal sales meetings but worth remembering for large events or webinars, where you might model attendance through a different object such as Campaign Members instead of stuffing every name onto one Event.
Sending invitations from Lightning Experience
Out of the box, adding people to an event in Salesforce relates them as attendees, but it does not necessarily email them a calendar invite. To make events actually send invitations, an admin sets up that capability for Lightning Experience users, after which a rep can add attendees on the event and have invitations go out. Salesforce also provides a way to restrict event email invites to internal Salesforce users only, which some organizations turn on to avoid emailing external contacts by accident. When invitations are enabled, the flow feels familiar: open or create the event, add the people you want, and save. Attendees who are users see it on their calendar, and external attendees receive an email they can accept or decline. Admins should decide deliberately whether external email invites are appropriate for their org, since an event tied to several customer contacts could otherwise send unexpected mail. Pairing this with clear naming conventions on events keeps the sent invitations professional and on-brand.
Auto-capture, sync, and event series
Most reps do not build Multi-Person Events by hand. They schedule meetings in Outlook or Gmail, and a capture tool mirrors them into Salesforce. Einstein Activity Capture syncs the user's connected calendar, so a multi-attendee meeting created in email shows up in Salesforce as a Multi-Person Event with EventRelation rows already created for each attendee. The sync keeps both sides aligned as details change. Salesforce Inbox adds in-context scheduling, letting a rep propose times from an email and create the event records when the prospect picks a slot. Meetings that repeat have their own handling. In Lightning Experience and the mobile app they are called event series, while Salesforce Classic calls them recurring events. A repeating meeting generally produces an occurrence for each instance, and each occurrence carries its own set of invitees and responses. That means an attendee can decline a single Tuesday without dropping out of the whole series, which matters when you report on attendance week by week.
Set up Shared Activities and event invitations
Multi-Person Events depend on two org settings working together: Shared Activities, so an event can hold many contacts, and event invitations, so attendees actually receive a calendar invite. Configure both in Setup before asking reps to schedule multi-attendee meetings.
- Open Activity Settings
In Setup, use Quick Find to open Activity Settings. This is where the activity-wide toggles live for events and tasks.
- Enable Shared Activities
Select the option to allow users to relate multiple contacts to events and tasks, then save. This unlocks the multi-contact attendee list (up to 50 contacts, one lead). Plan for it to stay on permanently.
- Turn on event invitations for Lightning Experience
Follow the Salesforce setup for sending invitations to attendees from Lightning Experience so that adding people to an event sends them a calendar invite rather than just relating them.
- Decide on external email scope
Choose whether reps may email external contacts and leads, or restrict event email invites to internal Salesforce users only. Set this based on your org's outreach policy.
- Validate with a test meeting
Create an event, add one internal user and one external contact, save, and confirm the user sees a calendar entry and the contact receives an email invitation that updates the response status.
The Shared Activities switch. Enables up to 50 contacts and one lead per event or task. Effectively one-way, so enable it early.
Lets reps email calendar invitations to attendees added on an event, instead of only creating attendee relationships.
Blocks event email invitations from going to external contacts and leads, keeping invites internal.
- Shared Activities is practically permanent once enabled, so confirm the decision before switching it on in a production org.
- Adding other attendees makes the Assigned To field read-only, because the owner may not have access to every invited contact or lead.
- Without event invitations enabled, adding attendees relates them in Salesforce but never emails them a calendar invite.
- Response status only updates when the meeting went out as a real invitation; manually logged events can leave invitees stuck at the default status.
Prefer this walkthrough as its own page? How to Multi-Person Event in Salesforce, step by step
Trust & references
Cross-checked against the following references.
Straight from the source - Salesforce's reference material on Multi-Person Event.
Hands-on resources to go deeper on Multi-Person Event.
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. Which object stores each invitee and their response status on a Multi-Person Event?
Q2. On a Multi-Person Event, which setting lets a single Event relate to many Contacts plus one Account at once?
Q3. How are external Contacts and Leads invited to a Multi-Person Event handled differently from internal Users?
Discussion
Loading discussion…