SHARING-AND-VISIBILITY-ARCHITECT practice question 9 of 15

Universal Containers (UC) has affiliates who sell containers in countries where UC does not have a local office. UC uses a Partner Community to…

Full set: 78 questions

Domain Programmatic Sharing

Universal Containers (UC) has affiliates who sell containers in countries where UC does not have a local office. UC uses a Partner Community to manage the sales cycle in those countries. One of its affiliates has grown substantially and restructured its internal sales team with the following structure: Sales VP —> Director of Sales —> Sales Manager —> Sales Reps. Sales Reps should not see each others’ opportunities, and visibility of deals should open up within a Sales Rep's hierarchy. What is the main problem an architect should address in this situation?
Answer options
A: The Channel Manager role cannot be shared with Partner Community.
B: Partner User roles are limited to three Ievels. Correct answer
C: Partner Community does not support Role Hierarchy.
Correct Answer:
B. Partner User roles are limited to three Ievels.
Explanation

The primary issue is a platform limitation. The affiliate's organizational structure requires a four-level role hierarchy (VP → Director → Manager → Rep) to manage record visibility. However, Salesforce Experience Cloud for Partners restricts the number of roles that can be created for any single partner account to a maximum of three. This technical constraint directly prevents the implementation of the required four-level hierarchy using the standard partner role functionality. The architect must devise an alternative solution, such as using groups or a custom sharing model, to accommodate the client's visibility needs.

Why Incorrect

A. The Channel Manager is an internal Salesforce user role for managing partners; the problem lies within the partner's own user role structure, not the internal management role.
C. Partner Community does support a role hierarchy for partner users. The problem is not the absence of this feature but the specific limitation on its depth (three levels per account).

References

1. Salesforce Help, Set Up Partner Roles: "You can create up to three roles for your partner accounts. The roles are created for all partner accounts that you enable. The roles appear on the partner account record, where the partner account owner can assign them to partner users." This directly confirms the three-role limit.

2. Salesforce Help, Who Sees What in Experience Cloud Sites, Partner Role Hierarchy: "Partner roles are a bit different from your internal Salesforce roles. Every partner account has its own role hierarchy... You can add up to three role levels for your partner accounts (for example, Partner User, Partner Manager, and Partner Executive)." This section explicitly details the functionality and its three-level limitation.

3. Salesforce Architects, Record-Level Sharing for External Users: "Each partner account has its own role hierarchy with up to three levels. When you enable the first external user on a partner account, Salesforce creates this three-level role hierarchy." This architect-level documentation reinforces the platform constraint.

Scroll to Top