Compliant Data Sharing versus core sharing mechanisms
Key Takeaway
Compliant Data Sharing adds access on top of core Salesforce sharing and can't remove access that other sharing features give. To limit a financial deal to its named participants, share it through participants and turn off role hierarchy-based sharing for Financial Deal.
Compliant Data Sharing is an Agentforce Financial Services feature that lets people share specific records with specific users or teams. A participant role on each share sets the access level. Financial firms need it because they must keep sensitive data, such as material non-public information (MNPI), behind barriers between departments. Compliant Data Sharing adds to core Salesforce sharing (org-wide defaults, role hierarchy, sharing rules and manual sharing) instead of replacing it.
Core Salesforce sharing
Core Salesforce security has two layers. Permission sets and profiles control which objects and fields a user can access. Record-level settings control which individual records a user can view and edit.
| Record-level tool | What it does |
|---|---|
| Org-wide defaults | Set the baseline access users have to each other's records |
| Role hierarchy | Gives users higher in the hierarchy the same access as users below them, regardless of org-wide defaults |
| Sharing rules | Create automatic exceptions to org-wide defaults for sets of users |
| Manual sharing | Lets record owners share with users who have no other access |
The intended pattern is to lock org-wide defaults to the most restrictive level. You then open access selectively with the other record-level tools.
Like the role hierarchy, sharing rules only add access, so they can't be stricter than org-wide defaults. To narrow access instead, use a restriction rule. A restriction rule permanently limits the records a user can read through sharing settings to those that match set criteria.
Unlike a restriction rule, a scoping rule doesn't restrict access at all. A scoping rule only scopes which records users see, so users can still open and report on every record they have access to.
Compliant Data Sharing controls access to records. Field access is a separate layer. Field permissions in permission sets and profiles give the strongest protection for a sensitive field. Page layouts only control field visibility on detail and edit pages.