The Compliant Data Sharing (CDS) feature lets administrators and compliance managers configure advanced data-sharing rules...

Compliant Data Sharing supplements Salesforce ' s standard record-sharing architecture with participant-based access. Record owners can add participants and assign Participant Roles that determine whether those users receive read-only or read/write access. Salesforce also permits non-owner participants who have Edit access through CDS to manage participants, giving them sharing capabilities comparable to the record owner. Users above the owner can separately retain access through role hierarchy where hierarchy access applies.

Salesforce also imposes a lifecycle dependency between object enablement and Participant Roles. If Compliant Data Sharing must be disabled for a supported object, the participant roles associated with that object must first be removed.

CDS is not limited exclusively to Financial Services objects plus Account and Opportunity. Current Salesforce implementations support additional standard and custom objects and use CDS across multiple Salesforce industry solutions.

For Organization-Wide Defaults, supported objects can use Private or Public Read Only for CDS to provide meaningful incremental access. Public Read/Write makes CDS ineffective because all users already have record access. Therefore, the assertion that OWD must always be Private is too restrictive under the current implementation.