Salesforce Exam Financial Services Cloud Topic 1 Question 59 Discussion

Compliant Data Sharing (CDS) is a feature of Financial Services Cloud that allows granular control over access to sensitive data in Account and Opportunity objects. CDS can help financial services companies comply with regulations and policies that restrict data visibility based on user roles. Some considerations regarding CDS are:

Participant Roles provide another way to grant data access without overwriting sharing behavior from existing sharing features. Participant Roles are custom objects that define the possible roles for users who need access to Account or Opportunity records. For example, a Participant Role can be Advisor, Client, Specialist, or Decision Maker. Each Participant Role has an associated access level that determines what data fields the user can view or edit. For example, an Advisor can have full access to all fields, while a Client can have read-only access to some fields.

Compliance managers and Salesforce administrators can enable CDS for Account and Opportunity objects. CDS is not enabled by default in Financial Services Cloud. To enable CDS, compliance managers or administrators need to create an integration definition record for each object that they want to enable CDS for. An integration definition record specifies the object name, the field name that contains sensitive data (such as Notes), the field name that contains the record owner (such as OwnerId), and the field name that contains the record type (such as RecordTypeId).

Role Hierarchy---based sharing is disabled by default in CDS. Role Hierarchy is a feature of Salesforce that allows users to inherit access to records from their managers or peers in the role hierarchy. For example, if a user has access to an Account record, their manager also has access to that record by default. However, in CDS, role hierarchy---based sharing is disabled by default for Account and Opportunity objects. This means that users do not inherit access to records from their role hierarchy unless they are explicitly granted access through Participant Roles or other sharing features.