Which action should not be taken when ensuring data visibility across multiple teams in Salesforce?

The selection of private sharing settings for all objects to restrict access does not contribute to effectively managing data visibility across multiple teams in Salesforce. Private sharing settings limit visibility to only the record owner and users above them in the role hierarchy. While this approach can enhance security for sensitive information, it is counterproductive when the goal is to ensure that multiple teams can access the data they need to work collaboratively.

Employing private sharing settings would create potential barriers to visibility, requiring additional configuration to open access through sharing rules or additional user permissions, ultimately leading to complexity and potential inefficiencies within the organization.

Conversely, the other options represent strategic methods to manage and facilitate data visibility. Public groups can be utilized to combine users with common access needs, enabling a more efficient sharing process. Criteria-based sharing rules enable organizations to dynamically adjust access rights based on specified conditions, ensuring relevant teams have access to pertinent data. Lastly, leveraging role hierarchies allows for a natural flow of data access down the hierarchy, ensuring team members can see records owned by their subordinates without unnecessary complications. Thus, while security through restrictions has its place, using private sharing settings universally hinders the goal of effective cross-team visibility.