Transfer Ownership of Published and Archived Articles

The Spring ’20 release introduced the ability to change a draft article’s owner in Salesforce Lightning. You can change the ownership of published and archived versions at the same time you change a draft version’s owner.

Where: This change applies to Enterprise, Essentials, Performance, Developer, and Unlimited editions of Knowledge with Lightning Knowledge enabled. Not available in Salesforce Classic.

Who: To change the ownership of an article, you must:

  • Be a Knowledge user.
  • Have the Manage Article user permission.
  • Have Read and Edit permissions for the article.

Why: With this enhancement, you can change the ownership of any version of any article. For example, this is useful if the owner of a published article no longer works at your company.

How: With a draft article that also has archived or published versions, the Change Owner button on the record’s home enables you to change the other versions.

  • To transfer the article owner’s published version for the language of the current draft, select Transfer the published version owned by the draft owner.
  • To transfer the article owner’s archived versions for the language of the current draft, select Transfer the archived versions owned by the draft owner.
  • To transfer all published and archived versions owned by anyone for the language of the current draft, select Transfer all versions (owned by anyone).

https://help.salesforce.com/s/articleView?id=release-notes.rn_knowledge_transfer_ownership.htm&release=228&type=5

Use Knowledge Sharing with Guest Users and High-Volume Community Users

We enhanced standard sharing for Knowledge to make sharing work the way it does for other Salesforce objects. Use criteria-based record-sharing rules to control which articles are exposed to your community’s guest users. Use sharing groups and sharing sets to share articles owned by High-Volume Community Users and portal users. Lightning Knowledge only.

Where: This change applies to Enterprise, Essentials, Performance, Developer, and Unlimited editions of Knowledge with Lightning Knowledge enabled. Not available in Salesforce Classic.

Why: Sharing for High-Volume Community Users is new for Knowledge for Summer ’20.

Although Guest User sharing was available with Knowledge in the Summer ’20 release, sharing in Knowledge followed external sharing rules. Now, normal Guest User security policies apply to Knowledge.

How: In Knowledge Settings, enable Lightning Knowledge and standard Salesforce sharing. For Guest User sharing, go to Setup->Sharing Settings, and set Secure guest user record access.

For sharing with High-Volume Community Users, use sharing groups and sharing sets.

https://help.salesforce.com/s/articleView?id=release-notes.rn_knowledge_sharing_guest_hvcu.htm&release=228&type=5

Renamed Two-Factor Authentication User Permissions and Labels in Setup

For all Salesforce products, we retired two-factor authentication (2FA) terminology and moved to the industry standard term of multi-factor authentication (MFA). To align Lightning Experience and Salesforce Classic with this change, we renamed two-factor authentication user permissions. And we renamed all two-factor and 2FA references throughout Setup and Salesforce documentation, including Salesforce Help, the Salesforce Security Guide, and Salesforce Developer Documentation. This update is a terminology change only—all functionality remains the same.

Where: This change applies to Lightning Experience and Salesforce Classic in Essentials, Group, Professional, Enterprise, Performance, Unlimited, Developer, and Contact Manager Editions.

What: In Setup, we updated two-factor authentication user permission names. We also updated labels for 2FA-related checkboxes, picklist options, and tooltips, descriptions, and other in-app messages.

How: These user permission names were updated:

https://help.salesforce.com/s/articleView?id=release-notes.rn_mfa_rebranding.htm&release=228&type=5

Drive Your Multi-Factor Authentication Implementation from One Place

It’s time to add another layer of protection for your Salesforce accounts. Meet the Multi-Factor Authentication Assistant, your hub for all the recommended steps, tools, and resources to roll out MFA to your users. The Assistant guides you through the entire process—from evaluating your requirements and planning the project to launching MFA and supporting users’ post-rollout needs.

Where: This change applies to Lightning Experience in Essentials, Group, Professional, Enterprise, Performance, Unlimited, and Developer editions.

When: The new Multi-Factor Authentication Assistant is available in Setup for all orgs on a rolling basis between September 18, 2020 and October 17, 2020.

Who: To use the Assistant, you must have the View Setup and Configuration and Customize Application user permissions.

Why: For easier manageability, the Multi-Factor Authentication Assistant breaks up your MFA project into three phases. Each phase provides step-by-step instructions and resources that give you guidance and best practices.

In each phase, steps are organized in stages that keep things organized, help you monitor your progress, and inspire confidence that nothing important is overlooked.

How: Access the Multi-Factor Authentication Assistant from Setup in Lightning Experience. At the top of the menu, click Multi-Factor Authentication Assistant.

https://help.salesforce.com/s/articleView?id=release-notes.rn_mfa_assistant.htm&release=228&type=5

Winter 21 Summary

In this edition of the blog rather than include both the summary of changes and detail we have just included the summary and hyperlinks to the detail in actual release notes when there is additional detail. This release appears to be a bit lighter than the last few releases in terms of the volume of security & permissions updates. However, there are still a lot. Our particular favourites in terms of enhanced security functionality are the Multi-Factor Authentication Assistant, Multi-Factor Authentication Assistant a great value add for Sys Admins that are more Salesforce gurus than general IT security experts, the ability to Deploy Organization-Wide Defaults and Criteria-Based Sharing Rules together (simultaneously update the sharingModel).