Deployment is significant. The pattern: identify objects requiring compliant sharing, enable the feature, design the Role-on-Account taxonomy, train users on the Participant workflow, build the compliance reports. Each step is mandatory; skipping any reduces the audit-evidence value the feature was deployed for.
- Identify objects requiring Compliant Data Sharing
Coordinate with compliance. The list typically includes Financial Account, custom industry objects holding regulated data, Account-Account Relationship in wealth management orgs.
- Enable Compliant Data Sharing per object
Setup, Financial Services or Industries area, Compliant Data Sharing. Enable for each object identified. Some objects support both standard sharing and Compliant Data Sharing simultaneously.
- Design the Role on Account taxonomy
List the role labels Participants will use (Primary Banker, Wealth Advisor, Trust Officer, Compliance Reviewer). The taxonomy drives the reporting categories regulators ask about.
- Configure attestation clauses for high-sensitivity objects
For shares of client confidential data, configure the attestation text. Coordinate with legal for wording.
- Train users on the Participant workflow
Bankers, advisors, supervisors. The workflow is heavier than standard sharing; training is non-optional.
- Build the compliance reports
Active Participants per Account, shares added per period, attestation completion rate, expired shares per period. These reports are the audit-evidence surface.
- Schedule the quarterly compliance review
Pull the reports, review with compliance, document any anomalies. The cadence is the operational discipline that produces continuous evidence.
Which objects use Compliant Data Sharing. Per-object decision aligned to regulatory scope.
The role labels used on Participant records. Drives reporting categories.
Per-object attestation text recipients acknowledge before access takes effect.
Default expiration on new Participant records. Time-bound by default is the safer pattern.
Whether standard sharing layers still apply on the same object. Some configurations allow both; others require Compliant Data Sharing exclusively.
- Compliant Data Sharing requires Financial Services Cloud or Industries Cloud licensing. Stock Sales Cloud and Service Cloud do not have it.
- The model is heavier than standard sharing. Every share is a record-create action; users and supervisors spend more time on sharing administration.
- Attestation must be configured before the high-sensitivity workflow goes live. Retrofitting attestation after the fact is operationally heavy.
- Default expiration is non-trivial to retrofit. Set the time-bound default at rollout; switching from indefinite to time-bound later requires updating historical Participant records.
- Standard sharing can coexist on the same object depending on configuration. The combined behavior can surprise users; document explicitly.