Cloud Kicks has recently rolled out a new Experience Cloud site for its customers. The site has been activated and the contacts have been enabled as customer users. However, none of the users received their login credentials in an email.
What caused this issue?
One possible cause of this issue is that the sender's email address was changed and not verified. The sender's email address is the email address that appears as the sender of the welcome emails to the customer users. If the sender's email address is changed, it needs to be verified by clicking on a link in a verification email. If the verification is not completed, the welcome emails will not be sent.
Ursa Major Solar (UMS) is using the Customer Account Portal template where both customers and employees can log in to view information about the company. UMS would like the Home page to
showcase internal resources at the top for its employees, and would like self-help resources to be available for lagged-in customers. UMS wants to exclude employee resources from the layout of
the Home page when customers are logged in.
Which functionality should UMS utilize to showcase the Home page in different ways?
Ursa Major Solar would like to expose the custom object SolarPanels to its customer portal. This particular object contains 150 fields, and a majority of the fields are technical codes and internal information.
How should the administrator limit the fields available in the customer portal?
To limit the fields available in the customer portal, the administrator should use Field-Level Security to remove access to the unwanted fields. Field-Level Security is a feature that allows the administrator to control the visibility and editability of fields for different profiles and permission sets. The administrator can use Field-Level Security to hide or make read-only the technical codes and internal information fields for the customer portal profile or permission set.
Ursa Major Solar wants to give customers the ability to add authorized users to view usage, billing, and payment history.
Which permission should be granted to customers to add authorized users?
To give customers the ability to add authorized users to view usage, billing, and payment history, UMS should grant Delegated External User Administrator permission to customers. Delegated External User Administrator is a permission that allows customers to create new users or reset passwords for other customers in their own account. UMS can use Delegated External User Administration, which is a feature that allows UMS to assign specific users as delegated administrators who can manage external users in their own accounts.
Cloud Kicks (CK) has built a site using Salesforce Experience Builder. The CTO of CK wants to give customers the ability to log in to the site using their Google credentials. CK also wants to access customers' basic Google profile data when they log in so the company can serve content that matches customers' interests.
Mow should the Experience Cloud consultant implement this?
This option allows CK to use Google as an external identity provider and enable customers to log in to the site using their Google credentials. CK can also access customers' basic profile data, such as name, email, and picture, by specifying the scopes and attributes in the authentication provider settings. CK can also use the authentication provider to configure single sign-on (SSO) and just-in-time (JIT) provisioning for the site.
Vivienne
2 days agoWenona
2 days agoJustine
4 days agoShannon
17 days agoRima
19 days agoDenise
1 months agoDick
1 months agoElouise
1 months agoLinn
2 months agoAntonette
2 months agoYolande
2 months agoAvery
2 months agoArletta
2 months agoTandra
3 months agoTamra
4 months agoAriel
4 months agoJimmie
4 months agoHuey
5 months agoVeronica
5 months agoRoyal
6 months ago