Sharing, Visibility, and Licensing Flashcards
External site members should not be able to see each other in a customer site.
‘Site User Visibility’ can be deselected on the Sharing Settingspage in order to ensure that external site members cannot see each other.
The external members of a site who belong to the same customer or partner account should be able to see each other, but other external users should not be able to see each other.
‘Site User Visibility’ can be deselected on the Sharing Settingspage in order to ensure that external site members cannot see each other. On the same page, ‘Portal User Visibility’ can be selected to ensure that external users in the same customer or partner account can see each other.
The members of a particular site should be able to see each other, regardless of whether they belong to the same account.
‘Site User Visibility’ can be selected on the Sharing Settingspage in order to enable an option that would allow site members to see each other. In the Preferences section of Administration, ‘See other members of this community’ can be selected to ensure that the members of the site can see each other.
All of the external users of a site who are assigned to a particular profile should be able to see all of the other users in the org.
The ‘View All Users’ permission can be enabled in the profile of the site’s external users.
The external users of an Experience Cloud site should not be able to view certain personal information fields in user records, including Username, Address, Email, Mobile, and Phone.
The ‘Enhanced Personal Information Management’ setting can be enabled on the ‘User Management Settings’ page in Setup. This setting blocks view and edit access to 30 personal information fields. The fields that should be hidden can be configured as personal information by adding ‘PersonalInfo’ in the Compliance Categorization area. The same can be removed for the fields that should be visible.
Support agents of Cosmic Service Solutions require access to cases created by customers in the customer site of the company.
A share group can be created to share case records owned by users with the Customer Community license with the role of support agents.
Support agents of Cosmic Service Solutions typically create cases on behalf of customers. These cases need to be made accessible to the customers in the customer site.
A sharing set can be created by navigating to ‘Settings’ under ‘Digital Experiences’ to grant customers access to cases associated with their contact record.
Users with the role Team Manager who have a Customer Community Plus license require access to all cases created within their account for all contacts of the Account.
A sharing set can be used to grant access to all cases that have the same account as the Team Manager user.
All opportunities related to a particular account need to be shared with users with the Partner Community license. They should have Read/Write access to it.
Sharing rulescan be created for the Partner Community license type. In this case, a criteria-based sharing rule can be created to share all opportunities with a certain Account ID. The ‘Read/Write’ access level can be specified while creating the rule.
Partner users of a site need to be provided access to all cases, leads, opportunities, and records of custom objects belonging to users in their accounts at the same role or below them in the role hierarchy.
In this case, the Partner Super User Access can be enabled by navigating to Digital Experiences | Settings. Super user access can then be granted to a partner user by clicking ‘Enable Super User Access’ from the contact for the user on the partner account.
A single record of the ‘Performance’ custom object needs to be shared with an Employee site user.
Manual Sharingcan be used to share a specific record with an Employee site user.
Cosmic Enterprises uses a private external sharing model. A sales manager of the company needs to share an opportunity with a group of four partner users and provide ‘Read/Write’ access to it.
Opportunity Team Sharing can be used to share a specific opportunity with a group of up to five partner users. ‘Read/Write’ access can be provided to the users.
Cosmic Enterprises is setting up an Experience Cloud site. The external users of the site would require access to leads, campaigns, and opportunities. The Salesforce Administrator of the company needs to determine the user profile that should be assigned to the external users.
The default user profile with the Partner Community license allows access to leads, campaigns, and opportunities.
Customers of an Experience Cloud site being set up by Cosmic Solutions require read and edit access to their own accounts only.
A private external sharing model can be used for accounts, and the Customer Community profile can be assigned to the customers.
Partners with the Partner Community default profile need to read, create, and edit campaigns in the site.
In addition to the access provided by the profile, partners would also require the ‘Marketing User’ permissionon their user records in order to create and edit campaigns.
Cosmic Solutions has a custom object named ‘Hobby’. Only external users with the Customer Community Plus profile should be able to read, create, and edit records of this custom object. In addition, external users should not be able to view ‘Hobby’ records owned by other external users.
Since profiles determine access to Salesforce custom objects, access to the custom object can be added to the Customer Community Plus profile. The external sharing model for the object can be set to ‘Private’ to ensure that external users cannot access each other’s records.
A Salesforce Administrator needs to grant all external user profiles access to the Salesforce mobile app.
Since the Salesforce mobile app is available for all external user profiles, all external users can be granted access to the Salesforce mobile app on their user records. The ‘API Enabled’ profile permission needs to be granted to access the community via Salesforce for Android and Salesforce for iOS.
Cyril Corporation is setting up a new Experience Cloud site for partners who require access to Territory Management features.
The default user profile with the Partner Community licensecan be assigned to site users, since it is the only one that can access Territory Management functionality.
Cosmic Solutions has set up a partner site. Partner accounts have been set up with three roles. One of the partner users with the ‘Partner Executive’ role requires access to all records owned by users with the same role, as well as ‘Partner Manager’ and ‘Partner User’ roles.
Super user accesscan be granted to the user who requires access to data owned by users with the same role, as well as roles below them. The user can be enabled as a super user by clicking ‘Enable Super User Access’ on the contact record for the user.
Users of a particular partner account belonging to the ‘Partner User’ role require read access to all the records of a custom object called ‘Suggestion’ on which the value of the ‘Status’ field is set to ‘New’. Several records owned by high-volume site users.
A criteria-based sharing rulecan be created for this requirement. The partner users’ role can be selected by choosing ‘Portal Roles’. While defining the role, ‘Include records owned by users who can’t have an assigned role’ should be selected to ensure that records owned by high-volume site or system users are included.
All users with the ‘Customer Manager’ role on an account require access to cases owned by internal users with the ‘Support Manager’ role.
An ownership-based sharing rulecan be created for this requirement. Cases owned by users with the ‘Support Manager’ role can be shared with users with the ‘Customer Manager’ role.
Cosmic Solutions has a large number of accounts with only one site member. They want to avoid a large number of roles so it does not affect performance.
Account Role Optimizationcan be used, which will apply one person role for the single site users instead of creating multiple roles based on the account.
A company uses a custom object to store comments created by the users of its customer site. Guest users of the site need Read Only access to all the comments that have been marked as visible using a custom checkbox field. They should have access to comments owned by high-volume site users, such as external users who have been assigned to the Customer Community or External Apps license.
A guest user sharing rule can be created to give guest users access to comments based on custom criteria which can include the custom checkbox field. An option can be selected in the rule to include records owned by high-volume site users.
Cosmic Travels has built a partner site which can be accessed by internal and partner users. Internal users who access the site should be able to view all the opportunity records regardless of their ownership. But partner users should only be able to view the opportunities owned by them.
The internal organization-wide default setting of the Opportunity object can be set to Public Read Only to allow internal users to view all the opportunities. The external organization-wide default setting of the object can be set to Private to ensure that external users such as partners cannot view opportunities owned by others.