Universal Containers (UC) has 200 distributors that use Partner Community licenses. Partners cannot see each other's data, but UC is also trying to…

Partner Super User access is the most scalable and appropriate solution for this requirement. This feature is specifically designed to grant users in a partner account (like a manager) access to data owned by other users who are in the same role or a role below them within the same partner account's role hierarchy. It avoids the creation of numerous sharing rules, which would be unmanageable across 200 distributors. You enable the feature once for the community and then grant "Super User" access to the specific manager-level users, allowing them to see all relevant case and container records for their subordinates at their specific distributorship.

A. Create an ownership based sharing rule.

This is not scalable. To maintain data segregation, each of the 200 distributors would require its own set of roles and a corresponding sharing rule, leading to significant administrative overhead.

C. Create sharing sets.

Sharing sets grant access to records based on the user's account affiliation, but they typically grant this access to all users with a specific profile, not just to users in a managerial role.

---

1. Correct Answer (B): Salesforce Help Documentation, "Give Super User Access to Your Partners and Customers".

Quote/Concept: "Partner super users can access more data and user records than other partner users. Super users have access to data owned by other partner users who have the same role or a role below them in the account role hierarchy. Partner super user access applies to cases, leads, custom objects, and opportunities." This directly supports using Super User access for hierarchical visibility within a single partner account.

2. Incorrect Answer (A): Salesforce Help Documentation, "Sharing Rules".

Quote/Concept: "Sharing rules are used to extend sharing access to users in public groups, roles, or territories." The documentation illustrates that rules are configured to share records from a source group to a target group. For 200 distinct partner accounts, this would necessitate 200 separate role hierarchies and 200 corresponding sharing rules to maintain data silos, which is not a scalable architecture.

3. Incorrect Answer (C): Salesforce Help Documentation, "Control Access Using Sharing Sets".

Quote/Concept: "Use a sharing set to grant high-volume community or portal users access to any record associated with an account or contact that matches the user’s account or contact... You configure sharing sets to grant access to users based on their profile." This confirms that sharing sets grant access based on profile and account/contact lookup, not on a user's specific role (e.g., manager) within the account hierarchy.