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.