Salesforce Community Cloud
The Salesforce Community Cloud certification is a credential developed for Salesforce professionals who have experience in implementing Community Cloud solutions on the Salesforce platform and are looking to verify their expertise. Working experience of the product is important for this certification in particular as it’s designed specifically for professionals with knowledge of implementation.
The exam is made up of 60 multiple choice questions
90 minutes to complete
The passing score is 62%
The Salesforce Administrator credential is a prerequisite
Cost is USD $200 and the retake fee is is USD $100 if you are unsuccessful
In Community Cloud, there are 7 topics covered. Implementation is the area with the highest weighting at 22%. As it is weighted highest, this is an area that you must focus on to do well in the exam.
Sharing and Security
Templates and Use Cases
Community Cloud Topic Weighting Chart
The following are the core topic areas of the Salesforce Community Cloud certification and what you’re expected to know:
The implementation topic starts with knowing which license type is appropriate for community member persona. A community license will allow partners and or customers to interact with Salesforce functionality and provide login access to the community. Communities are divided into Customer Communities, Partner Communities, and Employee Communities with different license types available for each.
The infrastructure of a community includes the main components of a community including Experience Workspaces and Experience Builder, preconfigured templates which define the elements and components available and other Salesforce features, such as login pages, the use of reports and dashboards, Lightning components, Chatter, and Salesforce Knowledge.
It is important to know the capabilities of the different deployment types. There are different tools available for deploying a Salesforce community, and you should be familiar with the high-level process for deployment that can be utilized for migrating a community from one org to another, and the metadata types associated with community deployment. Using change sets is considered the best option for deploying a community between related orgs due to its ease of use; however, there are several considerations for using them and other tools can be used such as the Force.com IDE and Force.com migration tool. It is also important to know what needs to be migrated manually.
Communities can be accessed from a mobile device, so you need to be able to determine the mobility requirements for a community. A mobile browser or the Salesforce mobile app may be used to access a community on a mobile device. The app has certain limitations related to communities which are important to know.
Depending on the use case, you will need to be able to evaluate integration strategies for a community. There are various way to integrate Salesforce, such as Salesforce Connect that can be used for the integration of external data with Salesforce which can also be exposed to Communities. A community can also be integrated with third-party applications, such as DocuSign, by downloading it from the AppExchange. Google Analytics can also be integrated with a community to track information, such as user types and search activity.
There are a number of steps required for a successful Community rollout. The rollout framework can be thought of as including four phases—establish, manage, engage, and measure. The implementation strategy includes investing in the resources required to plan and manage the community, establishing community requirements, building the community, planning an engagement strategy, measuring adoption and use, and ongoing management.
Communities are subject to limits due to Salesforce’s multi-tenant environment and license restrictions. The limits that apply to a Customer, Partner or Employee Community include number of users, page views, bandwidth, usage, roles, number of custom objects available and moderation rules.
When setting up a Community, consideration needs to be given to how to share Salesforce object data with users in a community and how to provide record access to high-volume community users, as well as security options related to collaboration, authentication, and setup of a partner or customer Community.
The Community security model includes considerations such as the type of community license which determine which sharing features are available. For example, advanced sharing is not available in a Customer Community. In Customer Communities, sharing sets are the method used to grant users access to records associated with their accounts or contacts. The external sharing model can be enabled for external users. As with internal users, profiles are used with external users to determine the standard and custom object permission, features and capabilities that can be accessed by the user.
A Public community can be set up using a guest user profile and visibility settings. The guest user profile can be used to open up or limit access to a community’s content. All community pages can be made publicly visible by default. It is also possible to set access level for each community page regardless of the community’s default visibility.
In a Tabs + Visualforce layout, appropriate tabs can be exposed to the community users based on needs. The tabs function similar to those in an internal Salesforce org, exposing Visualforce pages, web links or objects.
In a Community, topics can be setup and configured. Topics can be mapped to Knowledge articles using data categories. Topics can be used to structure community articles and content. There are two kinds of topics, navigational topics and feature topics. Feature topics are shown on the community home page as a tile. In Experience Workspaces > Content Targeting > Automatic Topic Assignment, a topic can be assigned to all articles that are published under a specific data category. All articles that are then created under that data category will be assigned the mapped topic. Topics can be added or removed from articles in the Article Management section of Experience Workspaces > Content Targeting.
There are 4 main steps to configure and set up Knowledge within a Community. First, security settings to access Knowledge need to be configured in profiles or permission sets. Then, for Tabs + Visualforce communities, the Knowledge tab needs to be added. Then Data Categories are setup to organize Knowledge articles and allow access to users via profiles and permission sets. Finally data categories and channels are set in each article to control which articles are available to the community.
There are various options available for setting up Community logins to meet community user login requirements. Self-registration can be set up to allow guest users to join a community. Social Login can be set up to allow users to log in using a third-party account. An organization’s existing single sign-on capability can be extended to a Community using SAML. It is also possible to brand a login page and customize login experience of a user. Other options include specifying a custom logout URL and choosing custom Change Password and Forgot Password pages.
Setting up email for community users involves customizing to include a logo and footer, as well as have specified templates to match company wording and image. As well as the Welcome email, custom templates can be created and selected for the forgot password, change password and case comment emails.
Experience Builder is used to customize Communities using a template design. It can be used to customize the look and feel of a community and match it with company branding. Logos and header colors can be added, as well as the color scheme.
Experience Builder can be used to customize navigation in a community. The menu can be used to effectively guide users through the community. The menu can include links to community pages, URLs, navigational topics or Salesforce objects. Headers can also be created to further nest groups of items in the menu.
Salesforce features can be used in a community to deliver targeted web or data content to users. Salesforce Files Connect allows access to external data sources such as Google Drive. CMS Connect is a way of connecting a Content Management System to a community for reusing its assets. Page variations are used to create different versions of a community page which can be assigned to different audiences and groups.
Components are customized and configured in the Community Page Builder. A number of standard template components are available to add to Community pages. Components can be dragged and dropped from the Components list onto the page in the Community Page Builder. Each component has properties that can be customized in the page editor.
Different types of components that can be installed and setup for pages in a community, using Experience Builder. Standard components are available in several categories and are ready to use out of the box. Custom components are similar to those used on Lightning App pages and are written using code. AppExchange components can be downloaded and added to enhance a community.
There are various multilingual capabilities in Communities. The different ways to set up a multilingual community provide accessibility to a larger range of users. Community members have their language set by their profile, but guest users can use their browser language or choose for themselves. Some content is translated automatically, but custom content will need to be translated on a page by page basis.
Managing a community involves determining how to add various members to a community depending on user access requirements, setting up moderation, recommendations, reputation levels and setting up community dashboards and insights.
Every topic objective explained thoroughly.
The most efficient way to study the key concepts in the exam.
Test yourself with complete practice exams or focus on a particular topic with the topic exams. Find out if you are ready for the exam.
Copyright 2019 - www.FocusOnForce.com
Copyright 2019 - www.FocusOnForce.com