You have created a custom object to list all upcoming company events, including speaker bio's and location and now wish to expose this publicly on your Customer Community. How are you are able to edit the public access settings? [Select Two]
A. Go into the Community Page Manager and update the Page Access control to Public
B. Go into the Setup Menu >> Profiles >> edit the object settings on the guest community profile
C. Add the sample code provided on help.salesforce.com to the head markup and add the object name you want to expose publicly
D. Install the Community Object Permissions Manager from the AppExchange for advanced data sharing options
E. Go into the Community Manager and select the objects that are available publicly
F. Go into the Community Builder and navigate to settings and click on the hyperlink to the Guest User Profile
Explanation:
To make the custom object (e.g., "Company Events") publicly accessible on a Customer Community, you need to ensure guest users can view its records. Guest users are unauthenticated users who access public pages without logging in, and their permissions are controlled by the guest user profile associated with the Experience Cloud site. Here’s a step-by-step breakdown of how to achieve this using the correct methods (B and F):
Understanding Guest User Access:
Guest users operate under a special profile created automatically when you enable an Experience Cloud site. This profile (e.g., "[Site Name] Guest Profile") defines what objects and fields guest users can access.
To expose the custom object publicly, you must grant at least "Read" access to the object and its fields (e.g., speaker bios, location) in the guest user profile.
Option B: Setup Menu Approach:
Navigate to Setup > Users > Profiles.
Locate the guest profile for your community (named after your site, e.g., "Customer Community Guest Profile").
Edit the profile’s Object Permissions under "Custom Object Permissions" to enable "Read" access for the "Company Events" object.
Optionally, configure Field-Level Security (FLS) to ensure fields like speaker bios and location are visible to guest users.
Save the changes. This ensures guest users can view the object’s records on public community pages (e.g., via a Lightning component or CMS content).
Option F: Experience Builder Approach:
Go to Setup > Experience Cloud > Workspaces, select your community, and click Builder.
In Experience Builder, click the Settings icon (gear) and look for the Guest User Profile section.
Click the hyperlink to the guest user profile, which opens the profile settings in Setup.
Follow the same steps as in Option B to grant "Read" access to the custom object and configure FLS.
This method is a shortcut to the same guest profile settings, making it efficient for administrators working in Experience Builder.
Additional Considerations:
Sharing Settings: Ensure the organization-wide default (OWD) for the custom object is set to "Public Read Only" or "Public Read/Write" if guest users need broader access. Alternatively, use manual sharing or sharing rules to expose specific records to guest users, as guest users don’t respect user-based sharing rules.
Secure Guest User Access: Starting with Spring ’20, Salesforce enforces secure guest user access, requiring explicit object and field permissions. Ensure compliance with these settings to avoid errors (e.g., "Guest users cannot access this object").
Component or CMS Display: To display the object’s data (e.g., event list), use a Lightning component, Visualforce page, or Experience Cloud CMS content in the community, ensuring the component respects guest user permissions.
License Considerations: Guest user access doesn’t require additional licenses, but ensure the community is configured for guest access (enabled via Setup > Experience Cloud > Administration > Preferences > Allow Guest Access).
Why Other Options Are Incorrect:
A: The "Community Page Manager" doesn’t exist, and page access settings in Experience Builder control audience visibility, not object permissions.
C: Head markup is for branding or scripts, not object permissions.
D: Native Salesforce functionality suffices; no AppExchange app is needed.
E: "Community Manager" is not a standard interface for object permissions.
References:
Salesforce Help: Guest User Security for Experience Cloud Sites – Details on configuring guest user profiles.
Salesforce Help: Set Up and Manage Experience Cloud Sites – Explains guest access and profile management.
Trailhead: Experience Cloud Basics – Covers guest user access and community setup.
Salesforce Help: Secure Guest User Access – Spring ’20 updates on guest user permissions.
Additional Notes:
Both methods (B and F) achieve the same result: editing the guest user profile. Option F is a shortcut from Experience Builder, while Option B is the direct Setup approach.
Ensure field-level security is configured for all relevant fields (e.g., speaker bios, location) to avoid partial data visibility.
Test the public access by viewing the community as a guest user (e.g., use an incognito browser to access the public URL).
Universal Containers has been using WordPress to publish product specifications, and using AEM (Adobe Experience Manager) for web assets. The VP of Sales wants to improve the Partner experience by making these resources available to Partners in their Community. What should the Community Cloud consultant do to meet these requirements?
A. Consolidate work into WordPress and use CMS Connect in the Community
B. Use the native Content Transformation tool to convert the resources into Knowledge articles
C. Create Knowledge articles that link to the relevant documents in both systems
D. Use CMS Connect to bring both sets of resources into the Community
Explanation:
Salesforce CMS Connect allows external CMS systems like WordPress and Adobe Experience Manager (AEM) to integrate content into Experience Cloud sites (Communities). It is specifically designed to surface externally hosted content such as HTML, CSS, JavaScript, and JSON into Salesforce Communities without duplicating or migrating the content.
✅ Why Option D is Correct
CMS Connect supports AEM and WordPress, which are explicitly mentioned in the scenario.
Allows the company to reuse existing content (e.g., product specs, web assets) directly in the Community.
Ensures consistency and efficiency, reducing the need for content duplication or re-authoring.
❌ Why Other Options Are Incorrect
A. Consolidate work into WordPress and use CMS Connect
→ AEM is also a current source; consolidating into WordPress would require a migration which adds unnecessary effort. Doesn't meet the requirement to leverage both systems.
B. Native Content Transformation tool
→ No such tool exists in Salesforce that converts WordPress/AEM content into Knowledge articles. This is not feasible or supported.
C. Create Knowledge articles with links
→ This would be a manual workaround, not scalable or integrated. It leads to a disjointed user experience and doesn't surface content inline in the Community.
✅ Summary
Use CMS Connect (D) to integrate both WordPress and AEM content directly into the Partner Community. This meets the business need without requiring content migration or duplication and provides a seamless partner experience.
📘 Reference:
Salesforce CMS Connect Documentation
Universal Containers is launching a Community with the following requirements:
- Branding requirement is limited to logo and font.
- Configurable Navigation with the option to navigate to custom objects and records.
- Access to articles is limited per Date Category Visibility. Which template should the Salesforce Admin use to build this Community that will natively support these capabilities?
A. Kokua
B. Koa
C. Customer Service (Napili)
D. Aloha
Explanation:
The Customer Service (Napili) template is the best fit because it natively supports all the given requirements:
Branding (Logo & Font):
Napili allows easy branding customization (logo, colors, and fonts) via Community Builder.
Configurable Navigation with Custom Objects & Records:
Supports Tabs and Navigation Menus that can link to custom objects and records.
Article Access Control via Date & Category Visibility:
Native Knowledge integration with Category Visibility and Article Date Restrictions.
Why the Other Templates Are Incorrect:
A. Kokua → Designed for employee engagement, not optimized for external partners/customers.
B. Koa → A Lightning-only template, but lacks built-in Knowledge filtering by date/category.
D. Aloha → Older Tabs + Visualforce template, not as flexible for modern Lightning requirements.
Reference:
Salesforce Community Templates Comparison
Napili Template Features
Universal Containers needs their channel partners to collaborate on Opportunities within their new partner Community based on the Customer Service Template. What is the recommended way to accomplish this task?
A. Create a page layout for leads and assign it to those profiles that have access to the Community.
B. Create a Detail page for invoices and add the page as a Navigation Menu item.
C. Create a Visualforce page for Opportunities and add the page as a Navigation Menu item.
D. Add Opportunities as a Salesforce Object in the Navigation Menu.
Explanation:
To enable channel partners to collaborate on Opportunities within a Partner Community built using the Customer Service (Napili) template, the most straightforward and scalable approach is to expose Opportunities directly as a standard Salesforce object in the community’s navigation.
🔹 Why Option D is Correct:
Salesforce allows standard and custom objects to be added to the Navigation Menu in Experience Builder.
When Opportunities are added this way, users with the correct profile and sharing access can view, edit, and collaborate on records.
This method leverages native Lightning components, avoids custom development, and supports record-level security via Sharing Sets or Role Hierarchy.
🔗 Salesforce Help: Add Standard Objects to Navigation Menu
❌ Why the Other Options Are Incorrect
A. Page layout for leads
Irrelevant—Leads are not part of the Opportunity collaboration requirement.
B. Detail page for invoices
Invoices are unrelated to Opportunities and not mentioned in the scenario.
C. Visualforce page for Opportunities
Unnecessary—Lightning templates support native object exposure without custom Visualforce.
💡 Real-World Scenario
Let’s say Universal Containers wants partners to:
View and update Opportunities tied to their accounts
Collaborate via Chatter or custom fields
Access related records like Quotes or Contacts
Steps to implement:
Go to Experience Builder → Navigation Menu
Add Opportunities as a menu item
Ensure Guest or Partner User Profiles have appropriate object and field-level permissions
Configure Sharing Rules or Sharing Sets to expose relevant records
Bagel World wish to engage with both their partners and customers alike and luckily have just purchased Salesforce. The only difference in the experience is that Partners will have access to their Bagel World Opportunities. What would you recommend to Bagel World?
A. Create 1 Community for both customers and partners
B. Create two Communities and give Partners access to both and only have Opportunities available in the Partner Community
C. Create 1 Community for both Customers and Partners and enable Super User Access for Partners
D. Create 2 Communities 1 Partner Community and 1 Customer Community
Explanation:
Bagel World needs to engage partners and customers via Salesforce Experience Cloud, with partners accessing Opportunities and customers having a different experience. Creating two communities—one for partners and one for customers—is the best approach.
Why Option D:
Tailored Experiences: Partner Community includes Opportunity access (via navigation and sharing rules); Customer Community focuses on customer engagement without Opportunities.
Security: Separate communities simplify access control, ensuring customers cannot access Opportunities.
Ease of Management: Distinct communities reduce configuration complexity and improve user experience.
Implementation: Use Partner Central template for partners (add Opportunity object to navigation, enable Chatter) and Customer Service template for customers. Configure sharing rules for partner Opportunity access.
Why Other Options Are Incorrect:
A. Single Community: Complex to manage Opportunity access with audience targeting; risks data exposure.
B. Two Communities, Partners Access Both: Unnecessary complexity; fragments partner experience.
C. Single Community with Super User Access: Overcomplicates permissions; doesn’t address distinct experiences.
References:
Salesforce Help: Set Up Experience Cloud Sites
Salesforce Help: Partner Central Template
Salesforce Help: Sharing Rules
Why It Meets Requirements:
Two communities provide tailored, secure, and user-friendly experiences for partners (Opportunity collaboration) and customers (engagement without Opportunity access).
Universal Rideshares uses a Custom Object to capture vanpool driver information. The VP of Support wants to give members of the Napili template -based Community access to this information for their vanpools. What is the most efficient way to accomplish this task?
A. Create a Visualforce page for the Custom Object and add it as a tab in Community Management
B. Create a Visualforce page for the Custom Object and add the Custom Object as a Navigation Menu item
C. Create a Detail page for the Custom Object and add it as a tab in Community Management
D. Create a Detail page for the Custom Object and add the Custom Object as a Navigation Menu item
Explanation:
Universal Rideshares wants users of a Napili-based (Customer Service) Community to access a custom object (vanpool driver information). The most efficient, maintainable, and Lightning-native way to do this is:
Use a standard record detail page (Lightning component) for the custom object.
Add that object to the Navigation Menu so it appears in the Community for users who have the appropriate permissions.
✅ Why Option D is Correct
Napili (Customer Service) template supports adding custom objects directly via the Navigation Menu.
No need to use Visualforce or tabs.
You can configure object visibility, detail page layout, and field-level access with clicks, not code.
By adding the object in the Navigation Menu, users can browse, view, and interact with the data directly.
📘 Reference:
Add Salesforce Objects to the Experience Builder Navigation Menu
❌ Why Other Options Are Incorrect
A & B. Visualforce pages
→ Overkill. Visualforce is not needed with Lightning-based communities unless you're doing something very custom. Native record pages are more maintainable.
C. Add detail page via Community Management tabs
→ The “Tabs” concept was primarily used in Classic or older templates. In Napili, navigation is handled through Experience Builder and the Navigation Menu, not via tabs in Community Management.
🔐 Additional Considerations
To make this work:
Ensure that community users’ profile or permission set grants object and field-level access to the custom object.
Ensure sharing rules or manual sharing give record-level access.
You may need to adjust Guest User profile if unauthenticated users need access.
✅ Summary
For a Napili-based Experience Cloud site:
Use native Lightning pages for custom objects.
Add them via the Navigation Menu.
Avoid Visualforce unless absolutely necessary.
What are the two ways to integrate Google Analytics with a template based Community?
A. Setup Menu >> Google Analytics >> Communities
B. Community Builder >> Settings > > Analytics Setup
C. Community Builder >> Settings >> Advanced >> Edit Head Markup
D. Community Builder >> Settings >> Advanced >> Google Analytics Tracking
E. Community Manager >> Settings >> Advanced >> Google Analytics Tracking
Explanation:
Salesforce Experience Cloud (template-based Communities) allows Google Analytics integration in two main ways, both accessed via Experience Builder (formerly Community Builder):
✅ Option C: Edit Head Markup
You can manually paste your Google Analytics tracking script (usually JavaScript) into the of your Community pages.
Path:
Community Builder → Settings → Advanced → Edit Head Markup
This method provides flexibility, such as support for Google Tag Manager, custom analytics logic, or advanced tracking events.
📘 Reference:
Edit Head Markup for Google Analytics
✅ Option D: Google Analytics Tracking Field
Salesforce provides a simple field where you can paste your Google Analytics Tracking ID (e.g., UA-XXXXXX-X).
Path:
Community Builder → Settings → Advanced → Google Analytics Tracking
This method requires minimal setup and automatically embeds the Google Analytics script into your Community pages.
📘 Reference:
Add Google Analytics Tracking ID
❌ Incorrect Options
A. Setup Menu >> Google Analytics >> Communities
→ No such section exists in the Salesforce Setup menu for this purpose.
B. Community Builder >> Settings >> Analytics Setup
→ There is no "Analytics Setup" section in Community Builder settings.
E. Community Manager >> Settings >> Advanced >> Google Analytics Tracking
→ The modern Experience Cloud doesn’t use Community Manager for this. It’s done via Community Builder.
✅ Summary
To integrate Google Analytics in a template-based Community:
Use the Tracking ID field for simple installs (Option D)
Use Edit Head Markup for advanced/custom tracking (Option C)
Universal Containers (UC) is implementing a Customer Community which will have thousands of Accounts with tens of thousands of Community users (Contacts). UC wants to ensure that all Customer Community licensed users are able to access the assets tied to their Accounts. Which action should the Salesforce administrator take when setting up asset sharing to ensure that Community users can see their account assets? Select one or more of the following:
A. Create a sharing rule for each accounts
B. Use Apex managed sharing to grant access to the Community users
C. Implement the role hierarchy on the Customer Community
D. Set up a sharing set that references the Account ID on the asset
Explanation:
To ensure Customer Community users can access assets tied to their Accounts, the most scalable and efficient method is:
Sharing Sets (Recommended for External Communities):
Sharing Sets automatically grant access to records (e.g., Assets) based on a shared relationship (e.g., Account or Contact lookup).
Configure a Sharing Set that links:
Community User Profile (e.g., Customer Community License).
Asset Object, with sharing rule criteria like "Asset.AccountId = User.AccountId".
This ensures users only see assets under their Account without manual sharing rules.
Why the Other Options Are Incorrect:
A. "Create a sharing rule for each account" → Not scalable (thousands of Accounts).
B. "Apex managed sharing" → Overly complex for this use case; Sharing Sets are native and simpler.
C. "Role hierarchy on Customer Community" → Role hierarchy doesn’t apply to external Community users.
Reference:
Sharing Sets for Communities
Asset Sharing in Communities
Universal Containers is building a Lightning Community. A few Community pages have numerous Lightning Components which are taking longer to display. Which step should be taken to improve display time performance of the pages? Select one or more of the following:
A. Enable Progressive Rendering
B. Turn on server-side Caching
C. Enable On-Demand Rendering
D. Turn on client-side Caching
Explanation:
When Lightning Community pages become slow to display due to many Lightning components, Salesforce provides performance optimization features built into Experience Builder to address this:
✅ A. Enable Progressive Rendering
Progressive Rendering defers loading some Lightning components until after the parent component has rendered.
This speeds up the initial page load by reducing how much gets rendered all at once.
Enabled via Experience Builder per component.
Especially useful for components lower on the page or non-critical components.
📘 Reference:
Progressive Rendering Overview
✅ C. Enable On-Demand Rendering
On-Demand Rendering delays rendering a component until it becomes visible in the user's viewport (e.g., via scrolling).
Reduces the page's initial rendering load, improving performance on load and overall user experience.
📘 Reference:
Lightning Components On-Demand Rendering
❌ Why B and D are Incorrect
B. Turn on server-side Caching
There is no admin-controlled setting called "server-side caching" in Experience Builder.
Server-side caching is handled automatically by Salesforce and applies mainly to data, not UI components.
D. Turn on client-side Caching
Similarly, client-side caching is controlled by browser behavior and Salesforce's internal architecture.
There's no switch or toggle for enabling this in the context of component rendering.
✅ Summary
To reduce load time on Lightning Community pages with many components:
Use Progressive Rendering to delay non-critical components.
Use On-Demand Rendering to render components only when they appear in the viewport.
These techniques are declarative, easy to enable, and recommended by Salesforce for optimizing Lightning Community performance.
Universal Containers needs to use their corporate portal to authenticate Community users, allowing users access to the Community after they have successfully logged into the Portal. What should the Salesforce Admin do in the Communities to support this login requirement?
A. Enable Guest User access in Communities to support seamless access to Communities from the Portal
B. Configure Single Sign -on in Salesforce and reuse the federated authentication providers in the Community
C. Add Social -Sign -on to allow users to log in from the Portal without signing into the Community
D. Enable Community login support for employees in the Portal configuration
Explanation:
Universal Containers wants users to authenticate via their corporate portal and access the Salesforce Experience Cloud site without re-logging in. This requires Single Sign-On (SSO).
A. Enable Guest User access (Incorrect): Guest User access allows unauthenticated access, not authenticated login from a portal.
B. Configure Single Sign-on (Correct): SSO enables users to log in via the corporate portal (acting as an Identity Provider) and access the Community seamlessly using SAML or OpenID Connect. Configure SSO in Salesforce Setup and enable the portal’s IdP in Experience Builder.
C. Add Social Sign-on (Incorrect): Social Sign-On uses social providers (e.g., Google), not corporate portals.
D. Enable Community login support for employees (Incorrect): This is not a Salesforce feature and doesn’t address the requirement.
Why B?
SSO integrates the portal’s authentication with the Community, ensuring seamless access.
Reference:
Salesforce Documentation: Single Sign-On for Experience Cloud
Trailhead: Identity for Experience Cloud
Universal Containers needs to create a Community that meets the following requirements:
- Self-Service Support Community, in which customer and partner users are community members
- Partner users help Universal Containers by adding or resolving cases for their customers within the Community
- Partner users need access to some standard objects except Leads, Campaigns and Opportunity Objects
- Partners use Chatter and the Case Feed to communicate with the Universal Containers team and customers Which licence type should a Salesforce Administrator use for these Partner users?
Select one or more of the following:
A. Customer Community Plus licence
B. Partner Community licence
C. Employee Community licence
D. Customer Community licence
Explanation:
Universal Containers needs a Community where both customer and partner users are members, with partner users performing specific tasks like adding or resolving cases, using Chatter and Case Feed, and accessing certain standard objects (excluding Leads, Campaigns, and Opportunities). The task is to select the appropriate license type for partner users. Below, I’ll evaluate each option, explain why it’s correct or incorrect, and provide references aligned with the Salesforce Certified Experience Cloud Consultant exam objectives.
A. Customer Community Plus licence (Incorrect)
What is it? The Customer Community Plus license is designed for external users (typically customers) who need access to cases, custom objects, and some standard objects, with more robust sharing and reporting capabilities than the basic Customer Community license. It supports self-service and case management but is not tailored for partner-specific functionality.
Why it’s Incorrect: While the Customer Community Plus license supports case management and Chatter, it’s primarily for customer-facing users, not partners who collaborate with the company on business processes like case resolution for their customers. It lacks specific partner features, such as delegated administration or access to partner-specific objects (e.g., Accounts for partner relationships), and is less aligned with the partner collaboration requirements described.
Reference: Salesforce Documentation - Customer Community Plus License
B. Partner Community licence (Correct)
What is it? The Partner Community license is designed for external partner users who collaborate with the organization, such as resellers or distributors. It provides access to standard objects like Accounts, Contacts, Cases, and custom objects, as well as Chatter and Case Feed for communication. Partners can manage cases, view related data, and participate in delegated administration, but access to Leads, Campaigns, and Opportunities can be restricted via sharing rules or profiles.
Why it Helps: The Partner Community license meets all requirements:
Self-Service Support Community: Supports partner users in a collaborative community environment.
Case Management: Allows partners to add or resolve cases for their customers, including Case Feed access.
Chatter: Enables communication with Universal Containers and customers.
Object Access: Provides access to standard objects (e.g., Accounts, Contacts, Cases) while allowing restrictions on Leads, Campaigns, and Opportunities through profiles or permission sets.
Partner Collaboration:Tailored for partners managing their customers’ cases, aligning with the scenario’s needs.
Implementation: Assign the Partner Community license to partner users in Setup > Users, configure profiles or permission sets to grant access to Cases, Accounts, Contacts, and Chatter, and restrict access to Leads, Campaigns, and Opportunities. Enable the Community with a template like Partner Central for partner collaboration.
Exam Tip: The Partner Community license is the go-to choice for scenarios involving external partners collaborating on business processes like case management or account-related tasks. Know its capabilities compared to Customer Community licenses.
Reference: Salesforce Documentation - Partner Community License
C. Employee Community licence (Incorrect)
What is it? There is no “Employee Community licence” in Salesforce. This is likely a distractor option, possibly referring to internal user licenses (e.g., Salesforce Platform or standard Salesforce licenses) used for employees, not external partners.
Why it’s Incorrect: The scenario specifies partner users, who are external users, not employees. Internal licenses are not suitable for external users due to cost and functionality mismatches. Even if misinterpreted as a community license, no such license exists for employees in Experience Cloud.
Exam Tip: Watch for non-existent license types in exam questions. If an option doesn’t match known Salesforce licenses, it’s incorrect.
Reference: No reference exists, as this is not a Salesforce license.
D. Customer Community licence (Incorrect)
What is it? The Customer Community license is a lightweight license for external customers needing basic self-service access to cases, Knowledge articles, or custom objects. It has limited functionality, such as read-only access to cases and no support for advanced features like Case Feed or extensive object access.
Why it’s Incorrect: The Customer Community license is too restrictive for partner users. It doesn’t support creating or resolving cases, using Case Feed, or accessing multiple standard objects (e.g., Accounts, Contacts) as required. It’s designed for basic customer self-service, not partner collaboration.
Reference: Salesforce Documentation - Customer Community License
Why B is the Best Choice
The Partner Community licence is specifically designed for external partners collaborating with Universal Containers. It supports case management, Chatter, Case Feed, and access to standard objects (with configurable restrictions on Leads, Campaigns, and Opportunities), perfectly aligning with the scenario’s requirements.
Additional Exam Insights
Scenario Analysis: The key is recognizing that partner users need a license supporting collaborative features (e.g., case management, Chatter) and access to specific objects, which points to the Partner Community license. The exclusion of Leads, Campaigns, and Opportunities can be handled via profiles or permission sets.
Common Pitfalls: Distractors like “Employee Community licence” or choosing Customer Community licenses for partner scenarios are common. Always match the license to the user type (partner vs. customer) and required functionality.
License Comparison:
Customer Community: Basic self-service, limited object access, no Case Feed.
Customer Community Plus: Enhanced customer self-service, supports Case Feed but not partner-specific features.
Partner Community: Designed for partners, supports case management, Chatter, and broader object access.
Related Topics: Be prepared for questions on:
Configuring sharing rules to restrict object access (e.g., denying Leads access).
Setting up Partner Central templates for communities.
Enabling Chatter and Case Feed in Experience Cloud.
Reference:
Salesforce Documentation: License Types for Experience Cloud
Trailhead: Experience Cloud Basics
Northern Trail Outfitters is planning to launch a Community for their partners. Partner Sales Managers need to view Partner Sales Rep records. What is the most efficient way for the Salesforce Admin to fulfil this requirement?
A. Provide Super User Access to Partner Sales Reps
B. Set the number of partner roles to two
C. Create a criteria-based Sharing Rule
D. Enable the Partner Sales Manager as Super Admin
Explanation:
In Salesforce Partner Communities, partner users are organized in a role hierarchy under their Account (Partner Account). By setting up multiple roles per partner account, you enable record visibility up the hierarchy — meaning higher-level users like Partner Sales Managers can see records owned by users beneath them, such as Partner Sales Reps.
✅ Why B. Set the number of partner roles to two is correct
Salesforce allows up to 3 roles per Partner Account:
Partner Executive
Partner Manager
Partner User
By configuring two roles, such as Partner Sales Manager and Partner Sales Rep, the Manager is above the Rep in the role hierarchy.
Salesforce's implicit sharing via role hierarchy ensures that higher roles can automatically see records owned by users in lower roles (e.g., Opportunities, Cases, custom records).
📘 Reference:
Partner User Roles and Sharing
❌ Why the Other Options Are Incorrect
A. Provide Super User Access to Partner Sales Reps
Super User Access allows select users to see records owned by other users in the same account.
It does not support role hierarchy-style access, and it’s not as scalable or structured as roles.
C. Create a criteria-based Sharing Rule
You could use this, but it’s less efficient and more manual than leveraging the built-in role hierarchy, especially when you're already managing roles.
D. Enable the Partner Sales Manager as Super Admin
No such feature exists as “Super Admin” for Community users.
Possibly a misunderstanding of Super User access, which still doesn’t provide true hierarchy-based visibility.
✅ Summary
To let Partner Sales Managers see records owned by Partner Sales Reps:
Use the Partner Role Hierarchy
Set the number of partner roles to at least two
Assign Managers to a higher role than the Reps
This is the simplest, most efficient, and native Salesforce approach for Community user visibility.
| Page 1 out of 24 Pages |