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]
An administrator is logged into Data Loader with their own credentials to insert new Business Account records into their Salesforce environment. They forget to specify the Account Owner field in the import file.
Assuming there are no other issues, what should happen when the administrator uploads the import file?
When using Data Loader to insert new records into Salesforce, if the Account Owner field is not specified in the import file, the default owner will be the user who is logged into Data Loader. In this case, since the administrator is logged into Data Loader with their own credentials, they will be assigned as the owner of all the new Business Account records. This behavior is consistent with the standard Salesforce rule that every record must have an owner.
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]
Rolland
18 minutes agoKayleigh
13 days agoKrissy
1 months agoIn
2 months agoLeota
2 months agoRoslyn
3 months agoMelodie
3 months agoDelsie
3 months agoMaryann
3 months agoEloise
3 months agoSophia
3 months agoCharlotte
3 months agoLoreta
3 months ago