Get more detail about who has access to a record. Enhanced Personal Information Management is now enforced, replacing Hide Personal Information in User Management Settings, and the setting that hides site users’ names in the SOAP API is retired.

• Enable Stronger Protection for Your Users’ Personal Information (Release Update)
  Enable Enhanced Personal Information Management to prevent external users, such as portal or community users, from accessing other users’ personal information. This feature, which replaces the Hide Personal Information setting, secures more personally identifiable information (PII) user record fields. You can also decide which custom and standard user fields are considered PII. This release update was first available in Spring ’22 and was scheduled to be enforced in Winter ’23, but we postponed the enforcement date to Spring ’23.
• Learn Who Can Access Records and Why
  Understanding who can access a record is critical to securing record access in your organization. Check out a record’s sharing hierarchy to view who it’s shared with. You can also see the user’s reason for access and find out if a user’s access is blocked by a restriction rule.
• Recalculate Account Sharing Rules Faster
  To improve performance, Salesforce is changing the way that automatic sharing calculation works behind the scenes for case and contact objects. We no longer store child implicit share records between accounts and their child case and contact records. Instead, the system dynamically determines whether users can access child case and contact records when they try to access them. Not storing the child implicit share records speeds up ownership and sharing rule recalculation for accounts.

Sharing (salesforce.com)

Boost data quality, build trust, and engage with customers in the ways they self-identify with gender-inclusive fields. Pronouns and Gender Identity are now included as optional picklist fields on the Lead, Contact, and Person Account objects. Use the vetted, default value sets or add your own picklist values to get a full picture of your constituents. Be sure to review any privacy implications of collecting this data before adding the new fields to your page layouts.

Where: This change applies to Lightning Experience, Salesforce Classic, and all versions of the mobile app in all editions.

How: From Setup, use the Object Manager to manage field-level security, add or edit picklist values, and add the new fields to your page layouts.

Capture Inclusive Data with Gender Identity and Pronouns Fields (salesforce.com)

This update is designed to improve org health and performance by restricting the number of inactive picklist values in a custom picklist field. We plan to remove the Remove upper bound on inactive picklist values panel from the Picklist Settings page in Setup in Summer ’23.

Where: This change applies to Lightning Experience and Salesforce Classic in all editions.

How: After the Remove upper bound on inactive picklist values panel is removed, you can’t remove the upper bound on inactive picklist values, and the maximum number of inactive picklist values for unrestricted picklists is 4,000. Any unrestricted custom picklists that were previously created without limits to the number of inactive values remain. Any new unrestricted custom picklists have a limit of 4,000 inactive values.

Prepare for Changes to the Picklist Settings Page (salesforce.com)

Save time managing your picklists. You can now delete, activate, deactivate, or replace multiple custom picklist field values at once. Previously, you modified them one at a time. This feature is available only for custom picklists with predefined values. This feature is generally available.

Where: This change applies to Lightning Experience and Salesforce Classic in all editions.

How: Go to the custom field definition page for the picklist field. In the Values and Inactive Values sections, there’s a checkbox next to each picklist value. You can select multiple values and use one of the new buttons: Delete Selected, Deactivate Selected, Replace Selected, or Activate Selected.

Bulk Manage Picklist Values (Generally Available) (salesforce.com)

Manage your inactive picklist values and enforce limits on inactive values for custom picklists to improve system performance and overall health. You can now bulk delete inactive unused picklist values. Previously, custom picklists with many inactive values were difficult to maintain because you had to delete inactive values one at a time. This feature is available only for custom picklists with predefined values. This feature is now generally available.

Where: This change applies to Lightning Experience and Salesforce Classic in all editions.

How: From the Inactive Values section of the picklist field, click Delete Unused Values. After you delete unused values, if a picklist is unbound and the total number of inactive values falls below the limit, the picklist is set to bound.

Clean Up Inactive Picklist Values (Generally Available) (salesforce.com)

Manage your inactive picklist values, and save time managing your custom picklists. Bulk deleting of all the inactive values for a picklist field is generally available. The ability to delete, activate, deactivate, or replace multiple custom picklist field values is generally available. Pronouns and Gender Identity are included as optional picklist fields on the Lead, Contact, and Person Account objects.

• Clean Up Inactive Picklist Values (Generally Available)
  Manage your inactive picklist values and enforce limits on inactive values for custom picklists to improve system performance and overall health. You can now bulk delete inactive unused picklist values. Previously, custom picklists with many inactive values were difficult to maintain because you had to delete inactive values one at a time. This feature is available only for custom picklists with predefined values. This feature is now generally available.
• Bulk Manage Picklist Values (Generally Available)
  Save time managing your picklists. You can now delete, activate, deactivate, or replace multiple custom picklist field values at once. Previously, you modified them one at a time. This feature is available only for custom picklists with predefined values. This feature is generally available.
• Prepare for Changes to the Picklist Settings Page
  This update is designed to improve org health and performance by restricting the number of inactive picklist values in a custom picklist field. We plan to remove the Remove upper bound on inactive picklist values panel from the Picklist Settings page in Setup in Summer ’23.
• Capture Inclusive Data with Gender Identity and Pronouns Fields
  Boost data quality, build trust, and engage with customers in the ways they self-identify with gender-inclusive fields. Pronouns and Gender Identity are now included as optional picklist fields on the Lead, Contact, and Person Account objects. Use the vetted, default value sets or add your own picklist values to get a full picture of your constituents. Be sure to review any privacy implications of collecting this data before adding the new fields to your page layouts.

Fields (salesforce.com)

Save time by managing picklist values in bulk. Enhance your case and lead record pages with Dynamic Forms. See who can access records and why, and better protect your users’ personal information with improvements to sharing.

• Fields
  Manage your inactive picklist values, and save time managing your custom picklists. Bulk deleting of all the inactive values for a picklist field is generally available. The ability to delete, activate, deactivate, or replace multiple custom picklist field values is generally available. Pronouns and Gender Identity are included as optional picklist fields on the Lead, Contact, and Person Account objects.

Customization (salesforce.com)

Enhanced domains are deployed for you unless you postpone that automatic deployment. And you can monitor more My Domain settings in Setup Audit Trail.

• Deploy Enhanced Domains (Release Update)
  To comply with the latest browser and security standards, enable and deploy enhanced domains. With enhanced domains, your company-specific My Domain name is included in the URLs that Salesforce hosts for your org. Consistent domain formats improve the user experience and standardize URLs for use in custom code and API calls. Also, with enhanced domains, your users can access Salesforce from browsers that block third-party cookies. Because this update affects application and login URLs, including Experience Cloud sites, Salesforce Sites, and Visualforce pages, we recommend that you deploy enhanced domains before this update is enforced. This update, originally named Enable Enhanced Domains, was first made available in Summer ’21.

• Monitor More My Domain Settings
  With new events in the Setup Audit Trail, you can track when an admin saves a change to your My Domain details, cancels a provisioned My Domain change, or removes a previous My Domain. The audit trail also captures when a user enables Salesforce Edge Network. When an admin deploys a new My Domain, the audit trail includes the new My Domain name and whether enhanced domains are enabled. Also, several existing events related to other My Domain settings are updated for clarity.

Domains (salesforce.com)

With new events in the Setup Audit Trail, you can track when an admin saves a change to your My Domain details, cancels a provisioned My Domain change, or removes a previous My Domain. The audit trail also captures when a user enables Salesforce Edge Network. When an admin deploys a new My Domain, the audit trail includes the new My Domain name and whether enhanced domains are enabled. Also, several existing events related to other My Domain settings are updated for clarity.

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

Why: Here’s an example of the Setup Audit Trail with some new and updated events for changes to My Domain settings.

Monitor More My Domain Settings (salesforce.com)

To comply with the latest browser and security standards, enable and deploy enhanced domains. With enhanced domains, your company-specific My Domain name is included in the URLs that Salesforce hosts for your org. Consistent domain formats improve the user experience and standardize URLs for use in custom code and API calls. Also, with enhanced domains, your users can access Salesforce from browsers that block third-party cookies. Because this update affects application and login URLs, including Experience Cloud sites, Salesforce Sites, and Visualforce pages, we recommend that you deploy enhanced domains before this update is enforced. This update, originally named Enable Enhanced Domains, was first made available in Summer ’21.

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

When: Salesforce deploys enhanced domains in Spring ’23. You can postpone that automatic deployment via a My Domain option. In Summer ’23, Salesforce deploys enhanced domains in orgs without the feature deployed. You can disable this feature until Salesforce enforces this update in Winter ’24. Orgs created in Summer ’22 or later get enhanced domains by default.

To get the major release upgrade date for your instance, go to Trust Status, search for your instance, and click the maintenance tab.

How: Before you update production, we recommend testing all My Domain changes in a sandbox. A message on the My Domain Setup page indicates whether enhanced domains are scheduled to be automatically deployed in Spring ’23. In that case, admins also see a reminder to enable this feature.

To complete this update, from Setup, in the Quick Find box, enter Release Updates, and then select Release Updates. For Deploy Enhanced Domains, follow the testing and activation steps.

To postpone the automatic deployment of enhanced domains until Summer ’23, disable a My Domain setting before the org gets Spring ’23. In the Routing section of the My Domain Setup page, click Edit, then deselect Automatically deploy enhanced domains with Spring ’23, and save your changes. Repeat this step in each org where you want to postpone the deployment.

Deploy Enhanced Domains (Release Update) (salesforce.com)