To clarify what users can and can’t do when they have access to a record type, we updated the description text and one of the profile column labels for Step 1 of the New Record Type creation process.

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

Why: The Enable for Profile column header is now Make Available, and the description more clearly outlines what users with access to this record type can do.

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

Customize where your Salesforce org’s utility bar appears on the screen. You can choose to align the utility bar to the bottom right or the bottom left of the screen. The default alignment matches the directionality of the user’s language.

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

Who: Admins with the View Setup and Configuration and Customize Application can modify the utility bar alignment.

How: To change the utility bar alignment:

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

Customize where your org’s utility bar appears on the screen. Display the Submit for Approval action only when a record is eligible for approval. Clearer description text and an updated profile column label for Step 1 of the New Record Type creation process.

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

You can now create entity particle relationships for geolocation field types. Also, the dropdown menu for the metadata relationship field type shows which entities are supported.

• Custom Metadata Types Support Geolocation Field Types Relationships
  Support for entity particle relationships was introduced in Summer ’20, with the exception of geolocation field types. With Winter ’21, you can now create geolocation field type relationships.
• View Supported Relationship Entities When Creating Custom Metadata Types
  When you a create metadata type, the metadata relationship field type menu now shows you which entities are supported. In previous releases, entities for relationships were only shown if they had a Salesforce Classic, Custom Fields setup page. This restriction was removed.

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

The Secure guest user record access setting was enabled in all Salesforce orgs with communities or sites in Summer ’20, but could still be disabled during that release. In Winter ’21, this setting is enabled in all orgs and can no longer be disabled. The Secure guest user record access setting enforces private org-wide defaults for guest users and restricts the sharing mechanisms that you can use to grant record access to guest users.

Where: This change applies to orgs with active communities and sites in Essentials, Enterprise, Performance, Unlimited, and Developer editions.

When: The timelines for the rollout and enforcement of this setting are published in Guest User Security Policies and Timelines.

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

You can now simultaneously update the sharingModel field for an object and create new criteria-based or guest user sharing rules via the Metadata API. Previously, you deployed these changes in separate packages. You still deploy owner-based sharing rules separately from organization-wide default changes.

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

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

The View All Profiles permission is now required when enabling or disabling Einstein Opportunity Scoring and Einstein Lead Scoring. Previously, you needed only the Customize Application and Modify All Data user permissions.

Where: This change applies to Lightning Experience and Salesforce Classic in Enterprise, Performance, and Unlimited editions.

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

A new Email-to-Case threading behavior matches incoming emails with their header information instead of through a Ref ID from the subject or body. New outbound emails don’t contain a Ref ID.

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

How: New orgs default to this new threading behavior. Admins for existing orgs can turn the new behavior on or off with a Release Update, until Salesforce enforces the update in the Winter ’22 release. Existing orgs continue to work based on ref ID until the new behavior is enabled, to give admins time to try out the new functionality before the enforcement date.

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

Now that Knowledge for Lightning Experience includes the ability to change article ownership, you can track that ownership. We added an Owner field to the Knowledge Field History for all article versions.

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

Who: Article history respects field, entity, and record-level security. You must have at least Read permission on the article type or the field to access its history.

How: To track ownership changes of Knowledge articles, make sure that:

• Lightning Knowledge is enabled.
• Field Tracking is enabled for the Knowledge Base.
• The Owner field is turned on for the field tracking.

Changes of ownership are displayed for all article versions that are updated, including online and archived articles and draft articles. A SOQL query on KnowledgeArticleVersionHistory returns two rows for each owner change update:

• User label (old and new) stored in the oldval_first_name and oldval_last_name fields
• User Id (old and new) stored in the oldval_string and newval_string fields.

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

Now you can change the ownership of multiple draft articles simultaneously, including translations.

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 use the Mass Change Owner action, users must have permission to transfer records, manage articles, and have Knowledge object permission to create, read, and edit articles. To be an article owner, the user or queue must have permission to view draft articles. When you use data categories to control record access, the owner needs category-based access.

Why: The Summer ’20 release introduced the ability to change the owner of a draft article in Lightning Knowledge. However, it allowed you to work on only one article at a time.

How: In a list view of Knowledge articles, select the articles you want to change, and select Change Owner.

Note that:

• You must have Change Owner on the Knowledge page layout.
• If you select published and archived articles along with draft articles, the draft articles are changed. The published and archived articles are not. But they can still be changed individually.

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