Loading

Change Organization-Wide Sharing Settings

Publish Date: Aug 21, 2024
Description
The purpose of this article is to discuss best practices when making organization-wide sharing changes. These changes require a recalculation of all record access levels in your organization and can cause adverse effects such as:
  • Contention lock errors ("The record you are trying to edit is temporarily unavailable").
  • Group membership lock errors ("Group Membership Locked").
  • Negative performance impacts on your organization.
  • Ownership Data Skew when user owns more than 10,000 records of an object.
Resolution

When making an org-wide sharing change, it's always best to plan and prepare before making these changes. The specific changes to do this for are:
  • Org-Wide Default change (that is, changing default access levels from Private to Public Read/Write).
  • Large-scale Role Hierarchy modifications.
  • Creation of multiple sharing rules.
  • Large-scale Public Groups maintenance (adding or removing members, deleting groups, and so on).
 
For all customers, we recommend that the following are done:
  • Test the change in a full data sandbox to ensure the change behaves as expected.
  • Plan a maintenance window during off-peak hours (with low user activity), such as at night, a weekend, or a holiday.
 
​​​​​ For our enterprise customers with very large organizations, we recommend the following (in addition to the above):
  • Plan maintenance windows during a weekend, holiday, or period of extended low user activity.  
  • Log a case with Salesforce.com Support to understand the overall impact on your org and instance.  Alternatively, it's best to work with a consultant or Salesforce partner to review these changes. 
  • For information on sharing related features and design concepts that can assist in streamlining your maintenance activities, review Record-Level Access: Under the Hood and Sharing Default Access Settings.
Knowledge Article Number

000387251

 
Loading
Salesforce Help | Article