Salesforce Release

Winter ’20 Community Highlights


The list of Winter ’20 features below apply to Community enhancements.

There are additional Winter ’20 features available to Salesforce Classic only, Lightning Experience and Salesforce Classic, Lightning Experience only, Mobile Enhancements, Other Enhancements in the Winter ’20 Release Highlights post.

Note: These features are not listed in any specific order.

  1. Partner and Customer Community users can use Lightning Experience to send individual emails via list email to each recipient versus one email to the entire group, to campaign users or from contact, lead or person account list views.
  2. (Generally Available) Salesforce CMS Features:
    • Create and manage content in Salesforce CMS with Chatter REST API or Apex and add it to Salesforce Tabs + Visualforce communities.
    • Create and manage custom content types with their own content detail page.
    • Add languages to new and existing CMS workspaces.
    • Manage translated content in your CMS workspace.

Note: To use Salesforce CMS, enable it in the Custom App Settings screen. Set CMS Workspaces tab to Default On for each profile who needs access to manage it.

  1. Lightning Communities Enhancements:
    • Use Flexible Layout pages to give you the maximum control over your community pages. You control the number of columns, sections, height and width of each.
    • Assign contributors to an assigned community by roles (Experience Admin, Publisher, Builder and Viewer). Previously, administrative access was required to make most community updates and across all communities.
    • Create and manage different navigation menus, reuse menu components in multiple menus, as well as set up different theme layouts.
    • Character limits are enforced in Questions so the community user will know when they’ve reached the 255 character limit, rather than when the user clicked on ‘Ask.’
    • Improved navigation between Topics and the detail page. When you click back from a topic detail page, you will be returned to the page that shows the question that you clicked, not back to Page One.
    • Use the ‘Customer Access’ option on a file’s sharing detail page to share the file on the record accessible to community users.
    • Delegated external user administrators are able to assign permission sets to other external users on their account.
    • The new global site tag (gtag.js) standard will automatically be used for new communities, so you have access to the most recent tracking features and integrations from Google. Manually update to the newest community template for communities created pre-Winter ’20 to take advantage of this latest feature.
    • Customize account selling teams on communities.
    • Filter for opportunities on the list view by my team’s opportunities.
    • Teams can use the ‘Team Member Access’ action to view team members’ access to records.
    • (Generally Available) The navigation Tile Menu component is now available for use.
    • Configure the header (list actions, list searches, refresh, charts, filter buttons, object names and image icons) for the record list component.
    • Case detail page variations and components are retiring Winter ’20. Instead, use generic record pages and components and tie them to the case object. Note: You can still use them if they are already being used in your community. However, if you remove them, you cannot add them again.
  2. Guest User Security Enhancements:
    • On the Sharing Settings screen, check the security setting “Secure guest user record access” to prevent the guest unauthenticated from access objects, guest users from being added to groups or queues, as well as prohibits manually sharing with them.
    • New communities created after Winter ‘20, the guest user visibility and community user visibility are turned off by default. You decide whether guest users can see other members of this community.
    • ‘View All Users’ and other permissions disabled in Guest User Profiles by default for all orgs created after Winter ’20.
    • Assigning records created by a Guest user to an internal user is a security best practice. On the Communities Settings screen, check ‘Reassign new records created by guest users to the default owner.’
    • Share records with unauthenticated users. Note: This can only be done by going to the Sharing Settings screen, and selecting the ‘Guest user access, based on criteria’ radio button when creating a sharing rule.
  3. Sharing and Security Enhancements:
    • (Critical Update, Enforced) For Communities and Portals, you can ‘Hide personal information’ from the User Record  by selecting that option on the User Management Settings.
    • (Critical Update, Enforced) Communities now require TLS 1.2 for HTTPS Connections, enforced in Winter ’20 on October 25, 2019. Note: You should verify that your browser access, API integrations, and other Salesforce features are compliant with TLS 1.2.
    • In the Identity Verification Setup screen, check the setting to enable email confirmations when a community user changes their email address before the email address changes in Salesforce.
    • Certain permissions have been disabled or removed by default from Community profiles to tighten up security.
    • Set external access levels on more standard objects.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s