Sharing and Visibility Architect - Certification Goal
Lessons
Permissions to Standard Objects, Custom Objects, and Fields
- Given a scenario, recommend the right level of object permissions needed to provide the appropriate access to a set of users.
- Given a scenario, recommend the correct level of field permissions needed to provide the appropriate access to a set of users.
- Given a scenario, recommend the appropriate mechanism to hide data at the user interface level.
- Given a scenario, determine the appropriate access controls to protect sensitive data (e.g. PCI, PII or HIPAA).
- Given a scenario, recommend the appropriate programmatic solution to ensure security settings are enforced.
Access to Records
- Given a set of conditions, recommend the appropriate Organization Wide Defaults to restrict access to records.
- Given a set of conditions, recommend a solution that leverages the Role Hierarchy to support the Record Access requirements.
- Given a set of conditions, determine how Sharing rules can be implemented to support the record access requirements.
- Given a set of conditions, determine how groups can support the record access requirements.
- Given a set of conditions, determine how Teams can support the record access requirements.
- Given a set of conditions, determine the correct object relationships that support record access sharing requirements.
- Given a set of conditions, determine how programmatic sharing supports the record access requirements.
- Given a set of conditions, determine what sharing mechanism is appropriate to share records with External Users.
- Given a set of conditions, determine how Record Access Overrides support the record access requirements.
Last Saturday, I cleared my Sharing And Visibility Designer Exam.
Can’t thank enough FOF team for their material, it prepared me well for the exam .
You guys are amazing.
Awesome news, Neha! Congratulations on clearing the exam! We are glad to know that we are able to help! Cheers!
Ref.: “External Account Hierarchies” vs “External Account Roles”
——————————————————————————-
Hello Martin / Anna,
I am trying to compare the 2 Salesforce standard features mentioned in the Ref.
>>External Account Roles:
I think that the purpose of the following 3 tier external “Account Roles “is to create an external role hierarchy:
– Customer or Partner “Executive” (positioned above “Manager”);
– Customer or Partner “Manager” (positioned above “User”);
– Customer or Partner “User” (Lowest role);
–> With this standard feature, accessibility to records rolls up the above mentioned hierarchy from “User” to “Executive” AND further up to the Owner of the Account (Customer or Partner) AND further up to the users with internal Roles ABOVE the owner’s Role.
So far so good. This functionality is not new.
>> External Account Hierarchies:
After enabling this feature with a simple checkbox on Setup > Digital Experiences > Settings > Enable External Account Hierarchy, a new object with the API name “ExternalAccountHierarchy” becomes available/visible on the Setup > Object Manager.
–> The purpose of this new object “ExternalAccountHierarchy” is still unclear to me.
Could you possibly describe 2 Use Cases / Scenarios where it would make sense to use each of the 2 features and WHY would it be justified to use one instead of the other?
Thank you very much.
Ted
An external account hierarchy allows sharing data owned by users with roles in child accounts with the parent accounts in the hierarchy. It can be used when a parent company requires access to data owned by the users of its subsidiary companies. On the other hand, the customer/partner role hierarchy only provides data access to users associated with one specific account.
Ref: “Implicit Sharing” of type “Site or Portal”
——————————————————-
Hi Martin and Anna,
I have a question regarding an explanation given by Salesforce.com relative to the “Implicit Sharing” of type “Site or Portal” in its documentation here: https://developer.salesforce.com/docs/atlas.en-us.draes.meta/draes/draes_object_relationships_implicit_sharing.htm; there, Salesforce describes “Implicit Sharing” of type “Site or Portal” like this: “Access to a site or portal account and all associated contacts for all site or portal users under that account” (*).
To me, this recalls the purpose of using “Sharing Set” where, often, we need to grant access to a record to external users WITHIN its same Account. for example, all external users WITHIN a Customer Account need to have access to all cases WITHIN that Account, regardless of who owns each Case.
Based on (*) Salesforce definition of “Implicit Sharing of type Site or Portal” it sounds like it would implicitly grant precisely that (access to a record related to the same Account associated to the external user). I think I am misunderstanding this definition given by Salesforce.
I think I am clear on the purpose of “Sharing Set” but I am not clear about the definition of “Implicit Sharing” of type “Site or Portal” which, to me, sounds like is overlapping the purpose of “Sharing Set”.
For sure, I am missing something. Can you help me to understand how “Implicit Sharing” of type “Site or Portal” lives together with “Sharing Set”? Do both complement each other?
Thank you very much.
Ted
Please see the information on the following help page:
https://help.salesforce.com/s/articleView?id=sf.sharing_across_objects.htm&type=5
“An account’s portal or site user has Read Only access to the parent account and to all of the account’s contacts.”
A sharing set can be used to grant Read/Write access to related records.
Good courses. I have passed the exam Sharing and Visibility Designer
Hello Volodymyr! That’s great news. It’s a great honor for us to be a part of your Salesforce journey and preparations. Cheers to that!
Hello, I have a question about Practice Exam of Sharing and Visibility Designer (Declarative Sharing Part 1) 13th question. In the question it is said that custom profile was created and the question is how to remove access to edit Shipment records. The correct answer is B: create a muting permission. But does the muting permission can be applied to profile settings?
A muting permission set cannot be applied to a profile. It can be used in a permission set group to remove one or more permissions in the permission set group. You can then assign the permission set group to specific users. Please check the help page below to learn more.
https://help.salesforce.com/s/articleView?id=sf.perm_set_groups_muting.htm&type=5
Thank you very much, I passed the exam yesterday and this course was very helpful!
Hi Cathy! Thank you for the positive feedback regarding our materials. Congratulations on passing SVD. Job well done! We are happy for your achievement!
Thank you very much for all useful material about this exam. I passed the certification exam and now I’am Salesforce Certified Application Architect. Your course and practice exams are amazing!
Thank you Marco for the compliment. It’s nice to hear that you passed the Sharing and Visibility Designer Certification. We are happy to know that the materials have helped you prepare. Cheers!
I passed sharing and visibility designer a couple of days back. The study material is awesome! Keep up the good work FoF! Onto the next one ‘Data Architecture and Management Desginer’. Looking forward for more certification courses towards System architecture/B2B/B2C Solution Architecture.
Congratulations on passing the SVD Certification exam, Kalyan. We are glad to hear that the study materials were able to help you prepare well. Best of luck on your DAMD Certification, we know you will make it! Cheers!
I’ve passed Sharing & vis. Designer, thanks to the team and this is really a great material compared to trailmixes in trailhead and all.
Hi Anil! Awesome thing to share today! We are glad to hear that you have passed the SVD Certification! We are happy to know that FOF has helped you reached your goal.
I cleared Sharing and Visibility Designer Certification last week. Thanks FocusonForce for great study material.
Awesome news, Parag! Congratulations on clearing the exam! We are glad to know that we are able to help! Cheers!