The past two previous discussions were primarily based on the Sharing model and managed programmatic sharing on the Salesforce platform. This post will be focused on recalculating apex managed sharing. What does it mean to recalculate sharing? Sharing Recalculation Salesforce automatically recalculates sharing for all records on an object when its organization-wide sharing default access level changes. The recalculation adds managed sharing when appropriate. Also, all types of sharing are removed if the access they grant is considered redundant.

This post is a direct continuation from the last post, detailing sharing on the Salesforce platform. In this second part series, coding examples will be provided to cement the whole programmatic sharing in Salesforce. Sharing Naming Convention To access sharing programmatically, you must use the share object associated with the standard or custom object for which you want to share. For example, AccountShare is the sharing object for the Account object, ContactShare is the sharing object for the Contact object.

What is sharing in Salesforce? Sharing is the act of granting a user or group of users permission to perform a set of actions on a record or set of records. Sharing access can be granted using the Salesforce user interface and Lightning Platform, or programmatically using Apex. This post is apart of the Salesforce Platform Developer 2 certification journey, specifically Salesforce Fundamentals and as such will be based on programmatic sharing within apex.