When the organization-wide default (OWD) sharing setting is set to "Controlled by the Parent" for the Activity object, a standard user with "Full Access" permission on a public calendar may not be able to delete an Event record created on that Public Calendar even when the user is the creator of the Event and has the necessary profile permissions for "Edit Tasks and Events."
The "Full Access" permission on a Public Calendar allows users to view detailed event information, insert events, and edit existing events. It does not grant delete access when the Activity OWD is set to "Controlled by Parent."
If the Event is related or associated to an object record or a Contact or Lead record, the related parent object controls the delete permission for the Event record.
Events on a Public Calendar cannot be deleted by a user unless one of the following conditions is met: the user is the owner of the associated parent record, the user has the "Modify All Data" permission on their profile, or the user has "Modify All Records" on the associated or related object. This behavior occurs because the Activity object's Organization-Wide Default (OWD) sharing setting is set to "Controlled by Parent," meaning the parent record controls delete access for the Event.
The following workarounds are available:
Change the Activity object's Organization-Wide Sharing Setting from "Controlled by Parent" to "Private." With this setting, a user can delete any Event from a Public Calendar as long as the user has "Full Access" permission assigned for that Public Calendar and has "Edit Tasks and Events" enabled on their profile. The Event record is no longer controlled by the associated parent object.
Edit the Event record and remove the Related or Associated Object name from the Event's related field, then delete the Event record. By removing the parent object association, the Event is no longer controlled by the parent's sharing rules.
Salesforce Help - Create and Manage a Public Calendar or a Resource Calendar
000385785

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.