• Each community by default comes with login, logout, password management and self registration pages and Salesforce provides the underlying code (Apex controllers) for all this. Community Builder or Visualforce can be used to customize branding and this default behavior.
  • Brand Community Login Page
    • We can use out own logo, change background colors, add a custom footer, and even change the content on the right side of the login page. We can specify dynamic branding URLs so that the login page is different depending on who logs in and from where.
    • Change logo from community administration page under workspaces.
      • Logo can be from a file or from a URL (fixed or dynamic).
      • For dynamic branding create a URL with dynamic experience ID parameter (expid)
      • Select the background color of the login page. The color you choose appears as the background on the left side of the login page.
      • Enter the right-frame URL to the right-side content of the login page. The right-frame URL can be fixed or dynamic.
      • Enter your text for the community login page footer, up to 120 characters
  • Create Dynamic Branding URLs
    • When using dynamic branding to customize the login experience, it applies to the entire login process: the initial login page plus related pages, such as two-factor authentication or a login flow. You can add dynamic branding to Community Builder, Visualforce, and custom login pages.
    • Use dynamic URLs for your login pages to present a different look and behavior based on the run-time situation
    • Dynamic branding relies on a URL parameter called the experience ID. The {expid} determines what the user experiences. At run time, the {expid} resolves to the current value, and the appropriate URL is created.
    • We can define dynamic branding URLs for logos and right-frames on the Community Workspaces Administration Login & Registration page. They apply to default and custom login pages.
    • The login implementation must set the login URL according to the value of the experience ID. For example, by adding the logic to your login button, when expid=INTERNAL, the login button directs the user to https://universaldistributing.com/brands/expid=INTERNAL.
    • You can also use Visualforce and Apex to create dynamic URLs. Use the Apex getExperienceId method of the System.Site class to retrieve the value of the experience ID. To set the experience ID, use the setExperienceId method, or add an experience ID dynamic parameter to one of these login endpoints.
  • Customize Community Login Experience
    • If your community uses the Salesforce Tabs + Visualforce template, the login page assigned to the community by default is called CommunitiesLogin. Use Community Builder or Visualforce to customize its appearance.
    • If your community uses the Customer Service template, the login page assigned to the community by default is called Login. Use Community Builder to customize its appearance.
    • To update the login behavior for Visualforce and Community Builder pages, update the CommunitiesLoginController Apex controller.
    • If you create a custom login page, you must first modify the CommunitiesLoginController Apex controller and the Site.login() Apex method before you can assign it to a community.
    • If you create dynamic logos and right-frame URLs, modify your login implementation to direct the user to the appropriate login URL based on the run-time situation.
    • You must publish custom Community Builder pages before you can assign them to a community.
    • The login page you select in Community Workspaces overrides other login page assignments in Site.com or Salesforce site settings.
  • Use Login Discovery to Simplify login
    • If you want external users to log in with another identifier than their username, such as a phone number or email address, configure your community with the Login Discovery Page. After users enter the identifier, they are challenged to verify themselves. For example, they might need to enter a verification code sent via email or text. If the user correctly enters the code on the Verify page generated by Salesforce, the user is logged in to your community. If SSO-enabled, Login Discovery can send the user directly to the identity provider login page. With Login Discovery, users can identity themselves using an email address or phone number. It also supports custom identifiers, such as an employee number or federation ID, in Apex.
  • You can provide community members with a custom login page that reflects your org’s style and branding. To change the look, customize the CommunitiesLogin login page, or create your own Visualforce page. To change login behavior, modify the CommunitiesLoginController Apex controller.
  • When community members log out, they’re taken to your community login page by default. You can choose to redirect them to a different location, such as your company website. Specify the URL to which community members are redirected when they log out from your community.
  • You can customize Forgot Password and Change Password pages from the Workspaces Administration Login & Registration page. Or you can create custom password pages in Visualforce. You can also customize the default password templates in Visualforce.
  • Enable self-registration to allow unlicensed guest users to join your community. When your users self-register, you can choose to save them as contacts under a business account or create a person account for each self-registering user.
    • Salesforce creates a user record with the information provided on the self-registration page.
    • The user is assigned the profile that you specified when you set up self-registration.
    • The user is associated with a business account or a person account, depending on how you set up your org.
    • If a user attempts to self-register under a username already in use, they will get an error message. Salesforce administrators will not be notified when the error occurs.
  • You can use the default self-registration page to sign up visitors with a username and password. But to give visitors a simpler, mobile-centric self-registration experience, use the Configurable Self-Reg Page. With this self-registration page, users can sign up with only an email address or phone number, instead of having to create a username and password. With this lightweight sign-up process, you can limit the amount of information that you collect from the users when they sign up. On subsequent logins, you can get more information, building a member’s profile through progressive profiling powered by the login flow.
  • When users sign up for your community with an email address or phone number, Salesforce sends them a verification code and generates the Verify page. The Verify page is where users confirm their identity, and you can replace the default Verify page with your own using Visualforce and a couple of Apex methods. After verifying their email address, external users can log in with one-time password (OTP) via email (passwordless login).
    • Salesforce actually supplies two default Verify pages, one for email and one for SMS verification. For convenience, you can brand the default Verify pages with your logo, colors, and background, but you can’t change the form itself. Here’s the default Verify page for SMS verification.

MOCK Questions

  1. Universal Containers (UC) has an existing Customer Community. UC wants to expand the self-registration capabilities such that customers receive a different community experience based on the data they provide during the registration process. What is the recommended approach an Architect Should recommend to UC?
    1. Create an After Insert Apex trigger on the user object to assign specific custom permissions.
    2. Create separate login flows corresponding to the different community user personas.
    3. Modify the Community pages to utilize specific fields on the User and Contact records.
    4. Modify the existing Communities registration controller to assign different profiles.
  2. Universal Containers (UC) has a Customer Community that uses Facebook for Authentication. UC would like to ensure that Changes in the Facebook profile are reflected on the appropriate Customer Community user: How can this requirement be met?
    1. Use the updateUser method on the registration Handler Class.
    2. Develop a scheduled job that calls out to Facebook on a nightly basis.
    3. Use information in the signed Request that is received from facebook.
    4. Use SAML Just-In-Time Provisioning between Facebook and Salesforce.
  3. Universal Containers (UC) is building a customer community and will allow customers to authenticate using Facebook credentials. The First time the user authenticating using facebook, UC would like a customer account created automatically in their Accounting system. The accounting system has a web service accessible to Salesforce for the creation of accounts. How can the Architect meet these requirements?
    1. Create a custom application on Heroku that manages the sign-on process from Facebook.
    2. Use JIT Provisioning to automatically create the account in the accounting system.
    3. Add an Apex callout in the registration handler of the authorization provider.
    4. Use OAuth JWT flow to pass the data from Salesforce to the Accounting System.
  4. Universal Containers (UC) would like its community users to be able to register and log in with Linkedin or Facebook Credentials. UC wants users to clearly see Facebook &Linkedin Icons when they register and login. What are the two recommended actions UC can take to achieve this Functionality? Choose 2 answers
    1. Enable Facebook and Linkedin as Login options in the login section of the Community configuration.
    2. Create custom Registration Handlers to link Linkedin and facebook accounts to user records.
    3. Store the Linkedin or Facebook user IDs in the Federation ID field on the Salesforce User record.
    4. Create custom buttons for Facebook and inkedin using JAVAscript/CSS on a custom Visualforce page.
  5. Universal containers (UC) wants to implement a partner community. As part of their implementation, UC would like to modify both the Forgot password and change password experience with custom branding for their partner community users. Which 2 actions should an architect recommend to UC? Choose 2 answers
    1. Build a community builder page for the change password experience and Custom Visualforce page for the Forgot password experience.
    2. Build a custom visualforce page for both the change password and Forgot password experiences.
    3. Build a custom visualforce page for the change password experience and a community builder page for the Forgot password experience.
    4. Build a community builder page for both the change password and Forgot password experiences.
  6. Universal containers (UC) is setting up their customer Community self-registration process. They are uncomfortable with the idea of assigning new users to a default account record. What will happen when customers self-register in the community? Reverify
    1. The self-registration process will produce an error to the user.
    2. The self-registration page will ask user to select an account.
    3. The self-registration process will create a person Account record. (if person accounts are enabled)
    4. The self-registration page will create a new account record.
  7. Universal containers (UC) would like to enable self – registration for their salesforce partner community users. UC wants to capture some custom data elements from the partner user, and based on these data elements, wants to assign the appropriate profile and account values. Which two actions should the architect recommend to UC? Choose 2 answers
    1. Modify the communitiesselfregcontroller to assign the profile and account.
    2. Modify the selfregistration trigger to assign profile and account.
    3. Configure registration for communities to use a custom visualforce page.
    4. Configure registration for communities to use a custom apex controller.


Leave a Reply

Your email address will not be published. Required fields are marked *