Say Hello to Salutation Picklist Values in Lightning Experience

Streamline your workflow by managing Salutation picklist values in Lightning Experience. Use the Object Manager to add, delete, activate, deactivate, and replace Salutation picklist values. Previously, you switched to Salesforce Classic to modify them.

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

How: From Setup, use the Object Manager to manage Salutation picklist values on the Individual, Lead, Contact, and Person Account objects.

Say Hello to Salutation Picklist Values in Lightning Experience (salesforce.com)


Limit the Number of Inactive Picklist Values

This update is designed to improve org health and performance by restricting the number of inactive picklist values in a custom picklist field. The panel on the Picklist Settings page in Setup that provided the option to remove the upper bound on inactive picklist values was removed.

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

When: This change was announced in Spring ’23 and is enforced in Summer ’23.

How: Now that this 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 new unrestricted custom picklists have a limit of 4,000 inactive values. Any unrestricted custom picklists that were previously created that have more than 4,000 inactive values remain unchanged.

Limit the Number of Inactive Picklist Values (salesforce.com)


Fields

Improve org health with limits on inactive picklist values. Streamline your workflow by managing Salutation picklist values in Lightning Experience. And refer to your nonbinary customers with the default Mx. Salutation picklist value.

  • Limit the Number of Inactive Picklist Values
    This update is designed to improve org health and performance by restricting the number of inactive picklist values in a custom picklist field. The panel on the Picklist Settings page in Setup that provided the option to remove the upper bound on inactive picklist values was removed.
  • Say Hello to Salutation Picklist Values in Lightning Experience
    Streamline your workflow by managing Salutation picklist values in Lightning Experience. Use the Object Manager to add, delete, activate, deactivate, and replace Salutation picklist values. Previously, you switched to Salesforce Classic to modify them.
  • Reflect the Diversity of Your Customers with Gender-Neutral Salutations
    Honor all your customers by using titles that align with their identities. The Mx. Salutation picklist value is now available by default. You can customize the Salutation field to include other nonbinary or honorific titles specific to your company. Be sure to review any privacy implications before collecting gender-related data.

Fields (salesforce.com)


Automate and Migrate User Access with User Access Policies (Beta)

Automate your users’ assignments to managed package licenses, permission sets, and other access mechanisms based on criteria that you set. Create user access policies that automatically grant or remove access whenever users are created or updated. Or, easily migrate large sets of users to a new access setup in a single operation. Previously, Salesforce enabled user access policies, but you can now enable this beta feature on the User Management Settings Setup page. Also since the last release, you can now set more complex user criteria and monitor recent user access changes.

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

How: From Setup, in the Quick Find box, enter User Management Settings, and then select User Management Settings. Enable User Access Policies (Beta). Then, in the Quick Find box, enter User Access Policies, and then select User Access Policies to create or manage your user access policies.

If Salesforce enabled user access policies for you before the Summer ’23 release, you must enable this feature again on the User Management Settings page.

Automate and Migrate User Access with User Access Policies (Beta) (salesforce.com)


Learn About Data Visibility and Access with Updated Who Sees What Videos

Set up your object, record, and field access to make sure that your users get access only to the data that they need—and no more. The refreshed Who Sees What video series reflects the latest best practices and incorporates more features, including permission set groups and restriction rules.

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

Learn About Data Visibility and Access with Updated Who Sees What Videos (salesforce.com)


See More Information in Reports from the User Access and Permissions Assistant

Reports on users’ assigned permissions contain more details, such as the users’ titles, profiles, and whether they’re active. You can filter on some user attributes to report on a subset of users. It’s now easier to select the user, object, and field permissions that you’re reporting on. We also improved performance for these reports in Salesforce orgs with a large number of users.

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

How: To use this feature, download the app from AppExchange.

See More Information in Reports from the User Access and Permissions Assistant (salesforce.com)


Allow Delegated Admins to Manage Permission Set Group Assignments

Delegated administrators can now manage the assignment of permission set groups for users in their delegated group, giving you more time for other admin tasks.

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

How: From Delegated Administration in Setup, create or select a delegated group. Then in Assignable Permission Set Groups, select the permission set groups that delegated admins can assign to users or remove. Delegated administrators can manage assignments for the permission set groups in their delegated group, but they can’t modify those permission set groups.

Allow Delegated Admins to Manage Permission Set Group Assignments (salesforce.com)


Set Field-Level Security for a Field on Permission Sets Instead of Profiles (Generally Available)

When you create a field, set its field-level security on permission sets instead of profiles. Or, modify the field-level security for an existing field for all permission sets in Object Manager. This change makes it easier to follow the user access control best practice of using permission sets to manage your users’ permissions rather than profiles. This feature, now generally available, includes an enhancement so that you can see each permission set’s object permissions for the field’s object without leaving the page.

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

How: From Setup, in the Quick Find box, enter User Management Settings, and then select User Management Settings. Enable Field-Level Security for Permission Sets During Field Creation. Now, when you create a field, set field-level security on an existing field, or change a custom field’s type, you assign field-level security for permission sets instead of profiles.

Set Field-Level Security for a Field on Permission Sets Instead of Profiles (Generally Available) (salesforce.com)


Permissions

Setting field-level security on permission sets instead of profiles is generally available, making it easier to follow the best practice of using permission sets for managing your users’ permissions. Delegated administrators can manage the assignment of permission set groups.

  • Set Field-Level Security for a Field on Permission Sets Instead of Profiles (Generally Available)
    When you create a field, set its field-level security on permission sets instead of profiles. Or, modify the field-level security for an existing field for all permission sets in Object Manager. This change makes it easier to follow the user access control best practice of using permission sets to manage your users’ permissions rather than profiles. This feature, now generally available, includes an enhancement so that you can see each permission set’s object permissions for the field’s object without leaving the page.
  • Allow Delegated Admins to Manage Permission Set Group Assignments
    Delegated administrators can now manage the assignment of permission set groups for users in their delegated group, giving you more time for other admin tasks.
  • See More Information in Reports from the User Access and Permissions Assistant
    Reports on users’ assigned permissions contain more details, such as the users’ titles, profiles, and whether they’re active. You can filter on some user attributes to report on a subset of users. It’s now easier to select the user, object, and field permissions that you’re reporting on. We also improved performance for these reports in Salesforce orgs with a large number of users.
  • Learn About Data Visibility and Access with Updated Who Sees What Videos
    Set up your object, record, and field access to make sure that your users get access only to the data that they need—and no more. The refreshed Who Sees What video series reflects the latest best practices and incorporates more features, including permission set groups and restriction rules.
  • Automate and Migrate User Access with User Access Policies (Beta)
    Automate your users’ assignments to managed package licenses, permission sets, and other access mechanisms based on criteria that you set. Create user access policies that automatically grant or remove access whenever users are created or updated. Or, easily migrate large sets of users to a new access setup in a single operation. Previously, Salesforce enabled user access policies, but you can now enable this beta feature on the User Management Settings Setup page. Also since the last release, you can now set more complex user criteria and monitor recent user access changes.

Permissions (salesforce.com)


Hide First and Last Name Fields in the SOAP API Is Being Retired

The Hide first and last name fields in the SOAP API for site users when making API calls from within a site with nicknames setting is now retired. To secure the first and last name fields when your users make API calls, enable Enhanced Personal Information Management. Use the instructions at Manage Personal User Information Visibility for External Users to classify personal information fields.

Where: This change applies to Aura, LWR, and Visualforce sites accessed through Lightning Experience and Salesforce Classic in Enterprise, Performance, Unlimited, and Developer editions.


Privacy Preference Center