Implementation section consists of 22% of total score in the Salesforce Community Cloud Consultant certification exam, covering topics such as license types, limitation, deployment types, integration, rollout and etc. There is a lot to cover, without further ado, lets get started!

NOTE: This post is written in June 2020 and content might be changed/updated overtime. The content is inspired by focusonforce.com.

Guideline for Implementation

• Given a scenario including Community member Persona information, recommend the appropriate license type to meet the requirement.
• Evaluate the infrastructure of a Community.
• Describe capabilities of different deployment types.
• Determine the mobility requirements for a Community.
• Evaluate integration strategies for a given use case.
• Outline the considerations required for a successful Community rollout.
• Given a scenario, determine which limits will influence a Community (for example, Community user limits).
• Explain how to set up a custom domain for a Community.

License Types

• Community License Types:

  • Guest:

    • No license required

  • Employee Community:

    • Lightning Platform Starter
      • access to standard objects:
        • Contacts, Accounts, Assets
        • Knowledge Articles
        • External Objects
        • Reports
        • Dashboards
        • Send Email
        • Tasks and Events and Calendar
        • Files and Content
        • 10 custom objects
    • Lightning Platform Plus
      • everything on Starter, plus:
        • allow access 110 custom objects
    • Employee License needs to be supported by Salesforce Platform user license and Company Community for Force.com permission set license.

  • Customer Community:

    • Customer Community

      • Business-to-consumer experiences with large numbers of external users who need access to case objects or knowledge.
      • The Customer Community can be used with person accounts.
      • Used by communities with high volume of external users who need to access to case objects and/or knowledge articles
      • Access to the following Standard Objects:
        • Contacts, Accounts (Read and Update), Assets, Contracts, Orders, Price Books, Products and Tasks
        • Knowledge Articles (Read Only)
        • Cases, Entitlements, Events, Work Orders, Work Line Items
        • External Objects
        • 10 Custom Objects
          • NOTE: custom objects in publicly available managed packages do not count towards the limit
        • Workflow Approvals (Submit)
      • Licenses should not exceed 10 million users.

    • Customer Community Plus

      • Business-to-consumer experiences with external users who need access to reports & dashboards and need advanced sharing.
      • Used for business-to-consumer experiences when external users need access to reports, dashboards, or advanced sharing.
      • The Customer Community Plus can be used with person accounts.
      • Access to all Customer Community's Standard Objects, plus:
        • Accounts (Read, Update and Create)
        • Tasks (Read, Update, Delete)
        • Reports
        • Dashboards (Read Only)
        • Send Email
        • Workflow Approvals (Approve)
        • Delegated Administrations
        • Events and Calendars
      • Licenses should not exceed 2 million users.
      • Data storage: 2MB (member-based license), 1MB (login-based license)

  • Partner Community:

    • Partner Community:
      • Business-to-business communities that need access to sales data such as partner relationship management.
      • Used in business-to-business community in which access is required to sales data such as partner relationship management
      • Access to all Customer Community Plus's Standard Objects, plus:
        • Leads, Campaigns, Opportunities, Quotes
        • Enterprise Territory Management
      • Data storage: 5MB (member-based license), 1MB (login-based license)
      • Partner Community users can have only up to 3 roles.
      • Licenses should not exceed 2 million users.
      • The Partner Community can't be used with person accounts.
      • NOTE: Partner Community license must be associated with partner-enabled business account.
    • Channel Account
      • Business-to-business communities and portals that calculate their usage based on number of partners instead of number of individual users.
      • Like Partner Community licenses, but the license is priced per partner account
    • Lightning External Apps
      • Highly customized experiences incorporating CRM objects, custom objects, external data, and requiring additional storage.
      • Ideal use cases are dealer, vendor, or supplier portals.
      • Also commonly used for franchise management, marketplaces, and multi-level marketing.
      • The External Apps license can't be used with person accounts.
      • Access to the following Standard Objects:
        • Contacts, Accounts, Assets, Contracts, Orders, Price Books, Products and Tasks
        • Knowledge Articles
        • 100 Custom Objects
      • Data storage: 10MB (member-based license)
    • Lightning External Apps Plus
      • Everything in Lightning External Apps, plus:
        • Cases, Entitlements, Events, Work Orders, Work Line Items
        • Leads, Campaigns, Opportunities, Quotes
        • Reports
        • Dashboards
        • Enterprise Territory Management
        • Delegated Administration
      • Data storage: 45MB (member-based license), 20MB (login-based license)

  • Commerce Portals:

    • Commerce Portals
      • Custom digital experiences to engage any external stakeholder, including Brand Engagement and Customer Loyalty.
      • The Commerce Portals license can be used with person accounts.
      • Access to the following Standard Objects:
        • Contacts, Accounts, Assets, Contracts, Orders, Price Books, Products and Tasks
        • Knowledge Articles
        • External Objects
        • 100 Custom Objects

• Member-based License Types vs Login-based License Types:

  • Member-based:
    • Best when users login frequently to community
    • License is purchased for each user accessing in community
    • Examples:
      • Customer Community
      • Customer Community Plus
      • Partner Community
      • Commerce Portals
      • External Apps
  • Login-based:
    • To use a Community login-based license, you first purchase a specific number of logins to be used every month.
    • External users associated with that license consume one login each time they log into a community (logging in multiple times counts one login even if switches between communities)
    • The ratio between the number of monthly logins you purchase and the number of login licenses that are provisioned in your org is 1:20.
      • 1000 monthly logins = 20000 login licenses are provisioned
    • Timeout period for a session is configurable up to a maximum of 24 hours.
    • Best when users do not login frequently.
    • Examples:
      • Customer Community Login License
      • Customer Community Plus Login License
      • Partner Community Login License
      • Commerce Portals Login License
      • External Apps Login License
    • Find out how many logins are consumed in Setup > Login History.
  • Member and Login-based:
    • Mix login-based licenses to cater different user groups in community.

• NOTE: Community license for a user can be used on multiple communities within an org

• Enable Partner User can be used to create partner user on Contact or Account. When enabling partner user, you can choose User License as well as Profile in User Settings:
  

• Enable Customer User can be used to create customer user on Contact. When enabling customer user, you can choose User License as well as Profile in User Settings:
  

Community Infrastruture

• Communities are created for different business requirements to cater access to Salesforce objects and functionalities for external users.
• All Communities can be found at Setup > All Communities with status of Active, Inactive and Preview.
  
• Communities Settings:
  
  • Enable Experience Workspaces
  • Assign new records created by guest users to default owner - if no default owner is chosen, the default record owner is the community owner
  • Display warning for unsupported browsers in Communities
  • Enable ExperienceBundle Metadata API - provide access to Experience Bundle Metadata API, allowing text-based programmatic migration and creation of communities
  • Number of customer roles - the default number of roles created when you add a customer account (default is 1, maximum at 3)
  • Number of partner roles - the default number of roles created when you add a partner account (default is 1, maximum at 3)
  • Allow editing of the Partner Account field on opportunities and leads
  • Enable Partner Super User Access - grant access to data owned by other users on the same partner account
  • Enable report options for external users - enable report options for external users in communities who have permissions to run reports
  • Let customer users access notes and attachments - let customer users access notes and attachments associated with accounts and contacts
  • Allow customer users to change case statuses - affects only Customer Community Plus licenses accessing communities created with Salesforce Tabs + Visualforce
  • Allow community users to see contacts that have not been enabled for communities - users can see contacts from private accounts that they have read access to, when the contact is controlled by parent record
  • Allow using standard external profiles for self-registration and user creation
  • Moderation applies to all feed posts regardless of where they are visible - apply moderation flags and rules to all feed posts, including those visible across multiple communities. When disabled, moderation applies only to community-specific feed posts.
  • Moderation rules can be configured for internal users' feed posts on records - apply moderation rules to internal users' feed posts on records, which may be visible across multiple communities
  • Support links to Visualforce pages from community pages made using Visualforce in the mobile app - keep the Apex prefix in community URLs so link between Visualforce pages resolve in Salesforce. Enabling this setting will keep the Apex prefix in all of your community URLs.
  • Link to community expires in - set the active time for links to the community in welcome email messages (1 day, 7 days, and 180 days)
  • Enable Account Relationship - enable to show Account Relationship objects and associated sharing rules (once enabled, cannot deselect it)
• Sharing Sets
  
  • Sharing Set grants community or portal users access to any record associated with an account or contact that matches the user's account or contact.
  • Select profiles and objects for the sharing set, then configure the access to the objects:
    
  • You will be seeing both Sharing Set Settings and Share Group Settings on the Sharing Set record page:
    
    • Share Group:
      • Share groups allow you to share records owned by high-volume community and portal users with internal and external users.
      • High-volume users are limited-access community or portal users, intended for orgs with many thousands to millions of external users.
      • Because high-volume users don't have roles, performance issues associated with role hierarchy calculations are eliminated.
      • Use a share group to share records owned by high-volume community and portal users.
      • Add User, Public Group, Roles, Roles and Internal Subordinates, Roles, Internal and Portal Subordinates, Territory, Territory and Subordinates to the Share Group Members:
        
      • View Share Group and Share Group Members:
        
    • NOTE: you need to Activate Share Group before it can be used.
  • Sharing Tool:
    • Convert External User Access Wizard:
      
    • Choose sharing rules or folders to update:
      

Experience Workspace

• Experience Workspace can be used to access the following:

Experience Builder

• Experience Builder can be used to customize the outlook of your community.
  
• Components:
  • Drag and drop components into the page.
  • Types of components available (to name a few):
    
• Theme:
  
  • Manage the colors, images, fonts and theme settings.
• Page Structure:
  
  • Click on the menu item to configure or click Delete button to remove the components on the screen.
• Settings:
  • General:
    
    • Enable Public Access - let guest users view asset files on public pages by default, you can adjust this setting in Administration | Preferences.
      • When enabled Public Access, SEO panel will be displayed.
    • Set the community title
  • Theme:
    
    • Change a theme to suit your business needs:
      
    • Activate theme:
      
    • Configure theme layouts:
      
      • Edit current layout or create new one
        
  • Languages:
    
    • Set default community language
    • Add other languages:
      
    • Import translation XML:
      
    • Export content for translation:
      
    • Configure translation using Google Cloud Translation API.
  • Navigation:
    
    • Navigation Menu can be created and set in Experience Builder.
  • SEO:
    
  • CMS Connect:
    
  • Advanced:
    
    • Set Google Analytics Tracking ID
    • Add markup to the <head> of every community page
    • Option to display all components, regardless of page type (some components might require specific parameters from the page and won't work unless you manually configure them)
    • Option to improve the performance of community
  • Security:
    
    • Clickjack Protection:
      • prevent user interface redress attacks by controlling where your community pages can be framed on a website:
        • Allow framing by the same origin only (Recommended)
        • Allow framing by any page (No protection)
        • Don't allow framing by any page (Most protection)
        • Allow framing of site or community pages on external domains (Good protection)
    • Content Security Policy (CSP):
      • Strict CSP: Block Inline Scripts and Script Access to All Third-party Hosts (Recommended)
      • Allow Inline Scripts and Script Access to Whitelisted Third-party Hosts
        • Lightning Locker can be enabled to isolate lightning components that belong to one namespace from components that belong to other namespaces.
      • Allow Inline Scripts and Script Access to Any Third-party Host (Less secure)
    • Trusted Sites for Scripts:
      • Add trusted sites
        
  • Developer:
    • Lightning Community Templates makes it easy to export your customized community and use it to jump-start new projects, or package and distribute it as a solution for others to use. Save time by building once, then reusing.
  • Updates:
    
    • Make sure you are using the latest stable version of your template.

Moderation

• View reports for flagged posts, comments, messages, and files.
• You can also see a report of all posts that are pending review and set up moderation rules for this community.

Content Management

• Organize, manage and build Collections for your Community Site.

Gamification

• Use Recognition Badges, Mission Badges, and Reputation to keep your members engaged with your community.
  • Recognition Badges:
    
    • Create new Recognition Badges:
      
  • Missions:
    
    • Create new Mission:
      
  • Settings:
    
    • Enable Recognition Badges
• Give Recognition Badges in Lightning Communities permission can be enabled to give badges to community members:
  
• Recognition Badges component can be added on User Profile to show badges:
  

Dashboards

• View dashboards and monitor information about groups, members, feed activity, moderation, topics, and license usage for this community.
  • Dashboards:
    • Map Labels with Dashboards:
      
  • Engagements:
    • Map Labels with Report Folders:
      

Administration

• Administration page can be used to update the community's basic setup:
  • Settings:
    
    • Activate or deactivate community
    • Choose templates:
      • Help Center
        • Self-Service
        • Curated Knowledge
        • Case Deflection
        • Guest Case Creation
      • Customer Account Portal
        • Record Management
        • Third-Party Integration
        • Streamlined Profile
        • Knowledge Base
      • Customer Service
        • Self-Service
        • Collaboration
        • Customization
        • Intelligence
      • Build Your Own
        • Customizable
        • Flexible
      • Partner Central
        • Onboarding
        • Channel Sales
        • Collaboration & Support
        • Analytics
      • Aloha
        • Salesforce Identity
        • Third-Party Integration
      • Salesforce Tabs + Visualforce
        • Standard & Custom Objects
        • Visualforce
        • Salesforce
  • Preferences:
    
    • Show nicknames - nicknames display in place of first and last names for all community members
    • Optimize images for mobile devices - scale down image when viewing on mobile device
    • Give access to public API requests on Chatter - let guest user access to Lightning Components and Visualforce Pages that need Chatter API for full functionality
    • Enable direct messages
    • Users can send and receive private messages - private messages from all communities are delivered to the Message Inbox.
    • Allow discussion threads - Users can reply to answers and previous replies
    • Let guest users view asset files and CMS content available to the community - guest users can access shared file assets and published CMS content that has been made for community use, even if it isn't actually used (automatically enabled if public access is enabled at the page or community level in Experience Builder).
    • See other members of this community - let community members see who else is in this community
    • Let guest users see other members of this community - let guest users see who else in their community, including non-guest users
    • Gather Community 360 data - Community 360 data includes most recently viewed articles and cases.
    • Use custom Visualforce error pages - use custom Visualforce error pages instead of default Visualforce error pages
    • Show all settings in Workspaces - show all settings that are hidden by default based on how you set your community
    • Allow members to flag content - flagged content will be sent to community moderator for review
    • Allow members to upvote and downvote - replace "Like" on questions and answers with upvote and downvote button
    • Enable setup and display of reputation levels - reputation levels and corresponding point system can be set up. The higher the point, the higher the reputation level.
    • Enable knowledgeable people on topics - Knowledgeable people are displayed in key areas, such as topic detail pages.
    • Suggest topics in new community posts - suggest topics when members post in a community
    • Show number of people discussing suggested topics - show number of people discussing topic suggestions when members post in a community
    • Maximum file size in MB - maximum size for files uploaded to the community (3MB - org's maximum file size).
      • NOTE: if you leave it empty or enter 0, it will be defaulted to 2048MB
    • Allow only these file types - limit the file types that can be uploaded to the community
  • Members:
    
    • All users with selected profiles or permission sets are members.
    • Community Role Labels can be changed:
      • Customer
      • Partner
      • Employee
  • Contributors:
    
  • Tabs:
    
    • Tabs will show in communities using the Standard Tabs + Visualforce template and determine community navigation in mobile app.
  • Branding:
    
    • Customize the community using Standard Tabs + Visualforce template. Some options such as Header Background Color, will also apply on the Login page and in the app.
  • Login & Registration:
    
    • Customize community's login experience, including page s used to log in users, verify identities, reset passwords, register members, and for login flows.
    • Branding Options:
      • Logo Type - choose File or URL
      • Background Type - choose Color or Image URL
      • Login Button - color of login button
      • Right Frame URL - display iframe by providing the URL
      • Footer Text - display text display at the bottom of login and related pages
    • Login Page Setup:
      • Login Page Type:
        • Default Page - a branded login page that prompts for username and password
        • Login Discovery Page - prompt for email, phone or custom user identifier.
        • Visualforce Page - let you choose a custom login page
        • Experience Builder Page - replace the login page with one built with the Experience Builder design tool
      • Allow internal users to log in directly to the community - internal users must be members of a community to log in directly from community login page
      • Select logo options to display on login page:
        • xxx username and password
        • trailhead SAML SSO setting
      • Logout Page URL:
        • Full URL - enter the complete URL of a Visualforce page or webpage that loads after a user logs out. If none is defined, a login page will be displayed.
      • Password Pages:
        • Forgot Password:
          • Default Page
          • Experience Builder Page
          • Visualforce Page
        • Reset Password:
          • Default Page
          • Visualforce Page
            -Registration Page Configuration
        • Allow external users to self-register
  • Emails:
    
    • Set Sender From Name
    • Set Sender Email Address
    • Set Chatter Email Logo
    • Set Chatter Email Footer Text
    • Send welcome email on new member added
    • Set Forgot Password Email Template
    • Set change Password Email Template
    • Set new Case Comment Email Template
    • Set User Lockout Email Template
    • Set One-Time Password Email Template
  • Pages:
    
    • Set home page for community
    • Set service unavailable page
  • Reputation Levels:
    
    • NOTE: Manage Communities permission is required, and the user must be member of the community in order to access this.
  • Reputation Points:
    
    • NOTE: Manage Communities permission is required, and the user must be member of the community in order to access this.
  • Rich Publisher Apps:
    

Guided Setup

• Configure features and integrations with step-by-step instructions:
  
• Examples of Guided Setup for Market Development Fund:
  

Deployment Types

• Change Sets
  • Migrate Lightning Communities and Salesforce Tabs + Visualforce
  • NOTE: not all settings and features are supported, that includes but not limited to: navigational and featured topics, languages, dashboards, etc.
• Force.com Migration Tool
• Force.com CLI
• Workbench
• Metadata API
• Lightning Bolt Solution
  • Lightning Bolts are Industry solution templates built by an ecosystem of partners, helping you get to market faster.
  • Lightning Bolts contain industry process flows, Apps, Lightning Components, and Communities, all integrated seamlessly with the Salesforce platform and CRM.
  • A Lightning Bolt Solution can be added to a package.
• Metadata types that can be migrated:
  • Network - configuration elements such as Reputation, Membership
  • CustomSite - domain and page section information, such as indexPage, siteAdmin, and URL
  • SiteDotCom - a binary file of community layout (same as Site.com Export)

Mobility Requirements

• Access communities in Salesforce App
  • Mobile User checkbox on User Settings Page:
    • Select this option so you automatically use Salesforce mobile web when you log in to Salesforce from a supported mobile browser.
    • If you turn this option off, your mobile browser is directed to the full Salesforce site instead.
    • NOTE: this option will be available if you have enabled Salesforce mobile web in Setup > Mobile Apps > Salesforce Settings:
      
  • API Enabled Permission - Allow access any Salesforce.com API
• Mobile Publisher
  • Mobile Publisher can be used to create fully branded version of Lightning Community.
  • Get started with Mobile Publisher:
    1. Sign up for mySalesforce program
       
    2. Select Community to brand (up to 5 apps per org)
    3. Create Mobile Publisher project and upload your branded items
    4. Install a special managed package for your app
    5. Test your app and once it is approved, Salesforce will submit the app to Google Play or Apple Store.
• External users can navigate to community URL and append one/one.app to the end of URL to login with community credentials.
• Internal users can use App Launcher to switch between Salesforce App.
• 'Hide On Mobile' can be set on Lightning Component to hide components from mobile user view.
• Navigation menu for community does not include all the items from internal org, for example, here is the list of items that are unavailable to tabs:
  • Knowledge Articles
  • Events
  • Reports
  • Today

Integration Strategies

• Salesforce Connect
  • Sales Connect can be used to connect to external system where there is large amount of data and user only require to access small amount of data in real time.
  • Create External Object and set up External Data Source, map fields and relationships and ensure that user has accessed to objects and fields.
• Google Analytics
  • Google Analytics can be set in Experience Builder > Settings > Advanced.
• Integrate with 3rd Party Apps
  • Custom Lightning Components can be added in Experience Builder.

Rollout Strategies

• Different Phases of Community rollout:
  • Establish Phase
    • Define goals and requirements
      • Define business goals
      • Identify member requirements and determine engagement
      • Understand community requirements
    • Build Community
      • Create community
      • Add members
      • Add components and enable features such as Chatter, Knowledge , etc.
      • Setup configuration and customization
      • Create contents, post questions, etc.
      • Testing with pilot group
    • Launch Community
      • Plan for how the Community will be released and published
      • Define marketing requirements and conduct campaigns
      • Define training and communication requirements
      • Manage members
      • Publish and market Community
  • Manage Phase
    • Manage the community with a cross functional approach including stakeholders, partners and company departments
    • Create reports and dashboards
    • Create knowledge content and stuff
    • Make use of topics, reputation and recommendations
    • Community Manager typical job activities:
      • Prepare strategy and measure
      • Work with all departments
      • Identify development requirements
      • Oversee moderation and collaboration
      • Build engagement
      • Ensure the community success
  • Engage Phase
    • Promote engagement as well as external measures
    • Create onboarding strategy and marketing strategies, such as events and loyalty programs.
    • Establish and promote community etiquette
    • Make use of gamification or reward or recognition features
    • Make use of Chatter and groups for communications
  • Measure Phase
    • Measure the success of community rollout in engagement, adoption or business value metrics. Examples of metrics:
      • Active users
      • Active groups
      • Active contributors
      • Response times
      • Page access count
      • Case deflection
      • Increase membership and time spent in community, and also return visits
    • Provide feedback to stakeholders

Community Limits

• Community Limits:

  • Number of communities per org: 100 (without buying more licenses)
    • Active, inactive and preview communities count towards the limit.

• User Limits:

  • Number of users in Customer Community: 10 million
  • Number of users in Partner/Customer Community Plus: 2 million (lower limit due to the roles associated with an account)

• Bandwidth Limits:

  • Developer Edition: 500MB (per rolling 24 hour period per community)
  • Performance, Enterprise and Unlimited: 1GB (Sandbox), 40GB (Production)
  • NOTE: the bandwidth limit is calculated for non-authenticated users only.
  • NOTE: the bandwidth is based on the number of MBs served and received from origin (web server that hosts the community site) or cache server (CDN server that serves cache community pages)
  • Overages can be purchased from Salesforce.

• Maximum Page Views Limits:

  • Page View is a request for an unauthenticated/guest community user to access a community page.
    • A request from an authenticated/license user is not counted.
    • Cached page views are counted.
    • Overages are calculated on yearly basis and can be purchased from Salesforce.
    • Page View includes:
      • Custom login pages
      • Any page associated with the community
      • Custom community web address
      • Community force.com domain
    • Page View does not include:
      • AJAX request
      • System pages, such as login, logout, forgotten password, etc.
      • Error pages
      • Authorization required error page
      • Images in HTML field
      • Attachments and documents
      • REST API calls
  • Enterprise Edition: 500k page views per month
  • Performance and Unlimited: 1 million page views per month
  • No limits on number of guest users accessing public community pages, but there is a limit on number of page views for guest users per month based on the edition.

• Service Request Time Limits:

  • Service Request Time is the total server time in minutes needed to generate community pages which is calculated for non-authenticated users
  • Developer Edition: 10 mins (per rolling 24 hour period per community)
  • Performance, Enterprise and Unlimited: 30 mins (Sandbox), 60 hours (production) (per rolling 24 hour period per community)

• Email Limits:

  • Email on every post will be disabled if more than 10000 members using this setting.
  • All members will be changed to Daily Digest option.

• Custom Object Limits:

  • Customer Community, Customer Community Plus, Partner Community, Lightning Platform Starter: 10
  • Lightning External Apps Starter, Lightning External Apps Plus: 100
  • Lightning Platform Plus: 110

• Role Limits:

  • Default number of roles per org: 5000 (contact Salesforce for more)
  • Role types in community: Executive, Manager and User
    • NOTE: system default is one (change in Setup > Community Settings)

• Record Access Limits:

  • Sharing Set can be used to give Customer Community users access to their own records and related records.
  • Share Group can be used to give internal users access to records created by Customer Community users.
  • Role Hierarchy can be used to give Community Customer Plus and Partner Community users to view records owned by users below hierarchy.
  • Super User Access can be used to give Community Customer Plus and Partner Community users to view records owned by other users in an account at the same level or below (available for cases, leads, opportunities and custom objects only)
  • Sharing Rules, Public Groups and Manual Sharing can also be used to share access with the users.

• API Usage Limits:

  • Customer Community: 0 (per day)
  • Customer Community Plus, Partner Community: 200 per member per day (member-based license), 10 per member per day (login-based license)
  • License External Apps: 200 per member per day (login-based license)
  • License External Apps Plus: 1000 per member per day (member-based license), 400 per member per day (login-based license)
  • Lightning Platform Starter: 200 per member per day (Enterprise or Unlimited Edition)
  • Lightning Platform Plus: 1000 per member per day (Enterprise Edition), 5000 per member per day (Unlimited Edition)
  • NOTE: Community API limits are added on top of Salesforce API limits.

• Reports and Dashboard Limits:

  • Report and Dashboard permissions can only be given to Customer Community Plus and Partner Community users.
  • NOTE: users cannot schedule, create, edit or view reports in Unified Public Report Folder.

• Navigation Topics Limits:

  • Number of topics (parent): 25
  • Number of subtopics: 10
  • Maximum of 5 levels of topics can be created, each with 10 subtopics, for total of 2775 navigational topics.
    • NOTE: additional 5 levels can be created via Chatter REST API or Chatter in Apex

• Moderation Limits:

  • Keyword List Criteria: 30 keyword list criteria per org
  • Member Criteria: 100 member criteria per org
  • Rule: 30 rules for entire org (not per community), including content and rate rules

Custom Domain

• Custom Domain can be used to set up sites and communities.
  
  • Custom domain allows the website to run under customer's own breanding and get better exposure in SEO and stuff.
• Custom URLs can be set up to host multiple sites and communities on same domain.
  
• Custom Sites allows you to create public website and applications that are directly integrated with your Salesforce org.
  
  • NOTE: Custom Sites and Custom Domains can have many-to-many relationship defined by Custom URLs.
  • Site Primary Custom URL can be set so that the site uses the custom URL in emails and secure site access.
• Steps to set up Custom Domain in Salesforce:
  1. Create a domain and set CNAME record for DNS in domain hosting provider.
     
     • You can choose to run with HTTP or HTTPS:
       • Salesforce serves the domain over HTTPS, on Salesforce's servers, using your HTTPS certificate
       • Salesforce serves the domain over HTTPS, using a Salesforce content delivery network (CDN) partner and a shared HTTPS certificate
       • A non-Salesforce host or service serves this domain over HTTPS
       • Salesforce serves the domain over HTTP without support for HTTPS access
  2. Set up Custom URL to map the custom domain to the community.
     
• Steps to attach CA-Signed Certificate to a custom domain for a community:
  1. Create CA-Signed Certificate in Salesforce from Setup > Certificate and Key Management:
     
     • Exportable Private Key can be selected so that your private key is included with certificates you export to a keystore.
     • Key Size can be set as 2048 or 4096.
       • Certificates with 2048-bit keys last one year and are faster than certificates with 4096-bit keys.
       • Certificates with 4096-bit keys last two years.
  2. Click to download Certificate Signing Request (CSR):
     
  3. Use the CSR key to get the signed certificate from SSL certificate provider (ex: namecheap.com)
  4. Download the signed certificate and upload signed certificate to Salesforce.
• My Domain:
  
  • My Domain can be used to add subdomain to Salesforce org. Example: abcompany.my.salesforce.com
  • NOTE: My domain has nothing to do with Community Cloud.
  • It is required for using features such as Single Sign-On (SSO) with external identity providers, social sign-on with authentication providers like Google, Facebook, etc.

---

Well, that's a lot to digest and I hope it can be useful! See you in next post!

Post was published on 12 Jun 2020, last updated on 14 Jun 2020.

Like the content? Support the author by paypal.me!