Cumulus Insurance has a franchise business model with a large number of franchisees who operate independently but report to regional managers who are Cumulus employees. The company would like the franchise owners and their employees to have access to the Cumulus Salesforce Financial Services Cloud (FSC) instance. The company plans to use the Role Hierarchy and sharing rules to implement this. What should the architect at Cumulus Insurance be aware of for this solution?
The architect at Cumulus Insurance should be aware of the limitation that the administrator can define up to 300 total sharing rules for each object when using the Role Hierarchy and sharing rules to implement the franchise business model. Sharing rules are a way of granting additional access to records based on criteria, such as record owner, role, or field values. The Role Hierarchy is a way of organizing users into a hierarchy that reflects the reporting structure of the company. The Role Hierarchy and sharing rules can be used together to control the access and visibility of records for different users in Financial Services Cloud. However, there is a limit of 300 sharing rules per object, which means that the administrator may need to use other methods, such as public groups or manual sharing, to grant access to records beyond this limit.
[Sharing Rules]
[Role Hierarchy]
[Sharing Rule Limits]
Which three permission sets grant access or extend permissions for record alerts in Financial Services Cloud (FSC)?
Record alerts are a feature of Financial Services Cloud that let users create and display alerts on record pages to highlight important information or actions. Record alerts are based on OmniStudio, a low-code platform for building digital experiences in Salesforce. To access or extend permissions for record alerts in Financial Services Cloud, users need to have one of the following permission sets:
Cumulus Insurance has a franchise business model with a large number of franchisees who operate independently but report to regional managers who are Cumulus employees. The company would like the franchise owners and their employees to have access to the Cumulus Salesforce Financial Services Cloud (FSC) instance. The company plans to use the Role Hierarchy and sharing rules to implement this. What should the architect at Cumulus Insurance be aware of for this solution?
The architect at Cumulus Insurance should be aware of the limitation that the administrator can define up to 300 total sharing rules for each object when using the Role Hierarchy and sharing rules to implement the franchise business model. Sharing rules are a way of granting additional access to records based on criteria, such as record owner, role, or field values. The Role Hierarchy is a way of organizing users into a hierarchy that reflects the reporting structure of the company. The Role Hierarchy and sharing rules can be used together to control the access and visibility of records for different users in Financial Services Cloud. However, there is a limit of 300 sharing rules per object, which means that the administrator may need to use other methods, such as public groups or manual sharing, to grant access to records beyond this limit.
[Sharing Rules]
[Role Hierarchy]
[Sharing Rule Limits]
A financial institution is concerned about contacting clients or sharing their data when they have requested not to be contacted.
Which action should the consultant take in Financial Services Cloud to address the institution's concern?
Use the Consent API: This is an API that lets users query, create, update, or delete consent records for customers who have given or withdrawn their consent for certain types of communication or data-sharing.
Protect your Salesforce organization: This involves setting up organization-wide sharing settings, encryption, field-level security, and other measures to ensure that only authorized users can access or modify customer data according to their consent preferences.
Consent Management for Financial Services Cloud
Set Up Tracking and Storage of Certain Data Privacy Preferences
[Use the Consent API]
[Protect Your Salesforce Organization]
An insurance company aims to improve a call center's productivity. A detailed analysis discovered that agents spend a lot of time capturing data while adding and updating beneficiary details. Capturing premium payment details (payment date and frequency) is another time-consuming task. Which action should a Financial Services Cloud consultant take to resolve the issue?
A Financial Services Cloud consultant can suggest utilizing Insurance Flow Templates to resolve the issue of improving the call center's productivity and reducing the time spent on capturing data for beneficiary details and premium payment details. Insurance Flow Templates are prebuilt flow templates that guide users through the steps of creating or updating insurance policies and beneficiaries in Financial Services Cloud. The templates can be customized to suit the specific needs and requirements of the insurance company. By using Insurance Flow Templates, the call center agents can streamline their data entry process and provide better service to their customers.
[Insurance Flow Templates]
[Customize Insurance Flows]
In
21 days agoLeota
26 days agoMelodie
1 months agoDelsie
1 months agoMaryann
2 months agoEloise
2 months agoSophia
2 months agoCharlotte
2 months agoLoreta
2 months ago