The Salesforce Sharing and Visibility Architect Certification is a credential developed for Salesforce professionals who have experience in designing Sharing and Visibility solutions on the Salesforce platform and are looking to verify their expertise. Working experience of the product is important for this certification in particular as it’s designed specifically for professionals who can architect a solution for a particular customer scenario.

In the Sharing and Visibility Architect exam, there are 4 topics covered. Access to Records is the area with the highest weighting at 39%. As it is weighted highest, this is an area that you must focus on to do well in the exam.

Sharing and Visibility Architect Topic Weighting Chart

The following are the core topic areas of the Salesforce Sharing and Visibility Architect certification and what you’re expected to know:

This section of the exam guide has five objectives that cover business scenarios with requirements related to various aspects of sharing and security in Salesforce. These include the use of object and field-level security settings to allow or restrict users’ access to different types of data, hiding data at the user interface level by configuring native features such as record types and tabs, protecting sensitive data using access controls, and programmatic enforcement of security settings in Apex and Visualforce.

This section has various objectives about sharing features that can be used to grant or restrict record access in Salesforce. Organization-wide defaults can be configured to restrict record access at the base level. Record access can be granted to users by using additional sharing features such as role hierarchy, sharing rules, groups, and teams. Object relationships such as master-detail and lookup relationships can also be used to support record access requirements. Records can also be shared with external users, such as customers and partners who access an Experience Cloud site. When record access needs cannot be met using declarative features, programmatic sharing can be utilized. Moreover, record access overrides, such as the ‘View All Data’ and ‘Modify All Data’ permissions, can be used for specific record access requirements.

This section has only one objective about using appropriate access controls to grant access to data that is not standard or custom objects. This data can be folders, content, Chatter data, Knowledge, Ideas, Questions/Answers, or mobile data.

This section contains objectives related to the implications of sharing solutions, license limitations, and testing the sharing model. A security model can be designed to ensure that it is maintainable at a large scale while meeting the requirements of a complex org. License limitations can impact the intended sharing solutions. Sharing and visibility can be validated using various methods. Unit tests can also be used to test programmatic sharing.