PranavNagrecha/AwesomeSalesforceSkills / skills/admin/compliant-data-sharing-setup
compliant-data-sharing-setup
VerifiedDeclarative setup of Compliant Data Sharing (CDS) in Financial Services Cloud: enabling CDS per-object in IndustriesSettings, configuring OWDs, creating CDS permissions, adding the Financial Deal Participants related list, and defining Participant Roles. Trigger keywords: ethical walls, compliant data sharing setup, FSC sharing model, isolate banking teams, participant roles. NOT for participant record DML from Apex — use apex/fsc-compliant-sharing-api. NOT for the FSC sharing design decision — use architect/fsc-architecture-patterns.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 15.0 KB |
| references/examples.md | markdown | 5.3 KB |
| references/gotchas.md | markdown | 5.1 KB |
| references/llm-anti-patterns.md | markdown | 6.8 KB |
| references/well-architected.md | markdown | 3.9 KB |
| scripts/check_compliant_data_sharing_setup.pyexecutable | script | 9.5 KB |
| templates/compliant-data-sharing-setup-template.md | markdown | 3.7 KB |
references/well-architected.md
View on GitHub# Well-Architected Notes — Compliant Data Sharing Setup
## Relevant Pillars
- **Security** — CDS is the primary platform mechanism for enforcing ethical walls and regulatory data separation in FSC orgs. Correct setup directly determines whether confidential client data is isolated between business lines. The role-hierarchy bypass, explicit participant assignment model, and per-object enablement flags are all security controls. Misconfigurations (wrong OWD, missing "Use CDS" permission, surviving sharing rules) undermine the intended data boundary and can result in compliance failures.
- **Reliability** — CDS introduces a new failure mode absent in standard sharing: a participant assignment that appears to succeed but produces no access grant (due to wrong OWD or missing Deal Management prerequisite). The setup checklist and validation steps in this skill ensure the configuration is testable and produces verifiable, reproducible access grants before production rollout.
## Architectural Tradeoffs
**CDS vs. Standard Sharing Rules for Team Isolation:**
Standard sharing rules can grant access across hierarchy boundaries but cannot prevent access granted by the hierarchy. CDS inverts this: it removes the hierarchy grant entirely and requires explicit assignment. The tradeoff is operational burden — every access grant must be explicit and maintained. For orgs with stable team structures, this is manageable. For orgs with high user turnover, `ParticipantGroup` (managed via the `fsc-compliant-sharing-api` skill) reduces the maintenance cost significantly.
**OWD Change Timing:**
Changing OWD in production triggers a sharing recalculation that can take minutes to hours depending on record volume. Changing OWD and enabling CDS simultaneously compounds the recalculation scope. The recommended pattern is: change OWD first, let recalculation complete, then enable CDS. This allows each change to be independently validated and rolled back if needed.
**Role-Hierarchy Inheritance Removal Is Irreversible in Practice:**
Once business users and managers have operated under CDS for even a short period, any rollback to role-hierarchy inheritance requires recreating the full participant assignment model using standard sharing rules instead — a non-trivial migration. Treat CDS enablement as a long-term architectural commitment, not a toggle that can be easily reversed.
## Anti-Patterns
1. **Enabling CDS without auditing existing sharing rules** — CDS replaces role-hierarchy inheritance but leaves sharing rules untouched. An org with existing criteria-based sharing rules that grant cross-team access will have an incomplete ethical wall even after CDS is enabled. Always audit and remove conflicting sharing rules as part of the CDS rollout.
2. **Assuming CDS is a superset of standard sharing** — CDS is a parallel mechanism, not an extension. It does not block access granted via other paths (sharing rules, manual shares, or Apex managed sharing). Architects who design ethical walls assuming CDS covers all access vectors will produce gaps that are difficult to detect without explicit cross-mechanism testing.
3. **Skipping the OWD prerequisite step** — CDS without Private or Public Read-Only OWD produces a configuration that appears deployed but functions as if CDS were not present. This is a silent misconfiguration that fails only at runtime access testing, not at deploy time.
## Official Sources Used
- Compliant Data Sharing for Financial Services Cloud — https://help.salesforce.com/s/articleView?id=sf.fsc_compliant_data_sharing.htm
- Compliant Data Sharing Setup (Trailhead) — https://trailhead.salesforce.com/ (page retired — see host index for current equivalent)
- Considerations and Limitations for Compliant Data Sharing — https://help.salesforce.com/s/articleView?id=sf.fsc_compliant_data_sharing_considerations.htm
- Salesforce Well-Architected Overview — https://architect.salesforce.com/docs/architect/well-architected/guide/overview.html
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |