Multi-Person Event
A Multi-Person Event in Salesforce is a calendar Event that includes multiple invitees beyond the event organizer.
Definition
A Multi-Person Event in Salesforce is a calendar Event that includes multiple invitees beyond the event organizer. Each invitee receives a calendar invitation; the platform tracks the response (Accepted, Declined, Tentative) per invitee on the EventRelation child object. The Event record itself holds the organizer''s details, the time and location, and the meeting subject; the EventRelation records hold the invitee list and their response statuses.
Multi-Person Events are the standard way Salesforce models meetings with multiple attendees: a sales rep meeting with five prospects, an account team kickoff with the customer, a quarterly business review with the client''s executive team. The model distinguishes between Salesforce internal users (User invitees) and external attendees (Contact or Lead invitees). The Einstein Activity Capture and Outlook/Gmail integrations auto-create Multi-Person Events when users schedule meetings in their email calendars, syncing the attendee list and response data back to Salesforce.
How Multi-Person Events model meetings in Salesforce
Event and EventRelation objects
Multi-Person Events use the Event standard object for the meeting metadata (subject, start time, end time, location, description) and the EventRelation standard object for each invitee. The relationship is parent-child: one Event has many EventRelations. Each EventRelation holds the invitee''s ID (User, Contact, or Lead) and their response status.
Internal vs. external invitees
EventRelation records distinguish internal Salesforce Users from external Contacts or Leads. Internal Users receive Salesforce-side calendar invitations; external Contacts and Leads receive email-based invitations. The two paths track responses differently; internal users update their Salesforce calendar, external attendees update via email reply.
Response tracking
The Response field on EventRelation captures each invitee''s status: Not Responded, Accepted, Tentative, Declined. The event organizer (the Event''s OwnerId) sees the response tally on the Event record. Reports on EventRelation aggregate response data across many events for meeting-acceptance-rate analytics.
Einstein Activity Capture sync
Einstein Activity Capture (EAC) syncs the user''s email-side calendar (Outlook, Gmail) with Salesforce. Multi-attendee meetings in the email calendar appear in Salesforce as Multi-Person Events with auto-created EventRelations for each attendee. The sync is bidirectional; updates in either system propagate.
Salesforce Inbox Insert Availability
Salesforce Inbox''s Insert Availability feature creates Multi-Person Events from inside Gmail or Outlook. The rep proposes meeting times in an email reply; the prospect clicks a slot; the platform creates the Event and EventRelation records, syncing the calendar invitation to all attendees.
Shared Activities setting
The Shared Activities setting (Setup, Activity Settings) controls whether an Event can relate to multiple Contacts and one Account simultaneously. Without Shared Activities, an Event links to one Who (Contact or Lead) and one What (Account, Opportunity, Case). With it, an Event has many Whos via the EventRelation object plus one What. Most modern orgs enable Shared Activities.
Group Events and event recurrence
Salesforce Events support recurrence patterns (every Monday at 10am for 3 months). Recurring Events generate one Event record per occurrence by default; the recurrence is tracked on the parent record. Each occurrence has its own EventRelation set, letting attendees decline individual occurrences without affecting the rest of the series.
Configure and use Multi-Person Events
Multi-Person Events are the standard meeting model. Configuration involves enabling Shared Activities and tuning the page layouts.
- Enable Shared Activities
Setup, Activity Settings, check Allow Users to Relate Multiple Contacts to Tasks and Events. The setting activates the EventRelation model for multi-attendee scenarios.
- Add EventRelation related list to layouts
Edit the Event page layout. Add the Attendees related list (showing EventRelation records) so users can see and manage invitees.
- Configure Einstein Activity Capture
Setup, Einstein Activity Capture, enable EAC for users who schedule meetings via Outlook or Gmail. EAC auto-creates Multi-Person Events on calendar sync.
- Train users on Insert Availability
Salesforce Inbox''s Insert Availability is the most-used multi-attendee scheduling flow. Walk users through using it from Gmail or Outlook.
- Build response-rate reports
Reports on EventRelation surface meeting acceptance rate, no-show rate, and per-rep meeting volume. Useful for sales-leadership pipeline-velocity analysis.
- Configure permissions
Users need read or edit access to EventRelation to see and manage attendees. Confirm permission sets cover the relevant profiles.
- Shared Activities is a one-way setting. Once enabled, the multi-Contact model is permanent; rolling back requires data work.
- Internal vs. external attendee paths differ. Internal users get Salesforce calendar invitations; external attendees get email invitations. Test both paths.
- Recurring events generate one record per occurrence by default. Series management can be confusing; document the org''s approach.
- EAC bidirectional sync needs careful configuration. Conflicts can produce duplicate events or missing attendees.
Trust & references
Cross-checked against the following references.
- Salesforce ActivitiesSalesforce Help
- Shared ActivitiesSalesforce Help
Straight from the source - Salesforce's reference material on Multi-Person Event.
- EventRelation ObjectSalesforce Developers
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 a Multi-Person Event?
Q2. Why the parent-child structure?
Q3. How do multi-person events sync externally?
Discussion
Loading discussion…