Because X (formerly Twitter) has enacted changes to its API terms, the Twitter connector for Account Engagement is no longer available as of October 31, 2023.
Where: This change applies to all Account Engagement editions.
In Salesforce orgs created on February 8, 2024 or later, after you enable digital experiences, records shared with the Roles and Internal Subordinates group through sharing rules or other features remain accessible only to those internal users. In orgs created before February 8, 2024, records shared with internal users are still made available to external site users automatically, and you must use the Convert External User Access wizard to secure access.
Where: This change applies to Aura, LWR, and Visualforce sites accessed through Lightning Experience and Salesforce Classic in Enterprise, Performance, Unlimited, and Developer Editions.
Why: For orgs created before February 8, 2024, the previous behavior is applied when you enable digital experiences, so that records shared with the Roles and Subordinates group are automatically shared with Roles, Internal and Portal Subordinates. To secure your org’s data, you must remove access for external users with the Convert External User Access wizard and manual updates.
Record Access Is Secure by Default after Enabling Digital Experiences (salesforce.com)
The Salesforce-managed app for the Twitter authentication provider is being retired in Spring ’24. To ensure that your users can still log in to your Experience Cloud site via single sign-on (SSO) with X (formerly known as Twitter), update your authentication provider configuration.
Where: This change applies to LWR, Aura, and Visualforce sites accessed through Lightning Experience and Salesforce Classic in Enterprise, Performance, Unlimited, and Developer editions.
Built-In Salesforce-Managed App for the Twitter Authentication Provider Is Being Retired
For Salesforce Customer Identity, take advantage of security and usability updates and a new authorization flow.
Where: These changes apply to LWR, Aura, and Visualforce sites accessed through Lightning Experience and Salesforce Classic. Most of the changes are available in Enterprise, Performance, Unlimited, and Developer editions, except for the update to headless identity flows, which is available only in Enterprise, Unlimited, and Developer editions.
Identity and Access Management Enhancements for Experience Cloud (salesforce.com)
To help prevent code injection attacks, Salesforce plans to update the system-defined trusted URLs that define your site’s content security policy (CSP) in Winter ’25. Prepare for this change by reviewing the impacted resources and updating your trusted URLs.
Where: This change applies to Aura, LWR, and Visualforce sites accessed through Lightning Experience and Salesforce Classic in Enterprise, Performance, Developer, and Unlimited editions.
Prepare for updates to format requirements for trusted URLs that define your site’s content security policy, which are designed to help prevent code injection attacks. Learn about security and usability updates and a new authorization flow for Salesforce Customer Identity. The Salesforce-managed app for the Twitter authentication provider is no longer supported.
You now see a confirmation message when you select the multi-select picklist field type when creating a custom field. The message reminds you to review the limitations of multi-select picklist fields before proceeding. We delivered this feature thanks to your ideas on IdeaExchange.
Where: This change applies to Lightning Experience and Salesforce Classic in all editions.
How: Multi-select picklists can be useful for user interface and data standardization. However, they provide limited reporting capabilities and can be difficult to use in automation and formulas. Use multi-select picklists only in specific situations where their use maximizes their benefits. This confirmation message ensures that you’re aware of potential issues when using this field type.
You now see a confirmation message that reminds you to review multi-select picklist field limitations.
You can now reference user picklist fields, groups, and queues in your policies’ user criteria filters, making it easier to automate your users’ assignments to package licenses, permission sets, and other access mechanisms. An improved user interface also makes creating and managing policies faster and easier. This feature continues to be available in beta in Spring ’24.
Where: This change applies to Lightning Experience and Salesforce Classic in Enterprise and Unlimited editions.
How: To enable user access policies, from Setup, in the Quick Find box, enter User Management Settings, and then select User Management Settings. Enable User Access Policies (Beta). The improved user interface is enabled by default, but you can disable the Enhanced Interface for User Access Policies (Beta) setting.
To create or manage your user access policies, from Setup, in the Quick Find box, enter User Access Policies, and then select User Access Policies.
Reference Picklists, Groups, and Queues in User Access Policies (Beta) (salesforce.com)
If you try to delete a permission set included in a permission set group that’s assigned to users, you now receive an error. You can only delete a permission set that isn’t assigned to users either directly or through a permission set group. Previously, this action wasn’t blocked, which allowed users to be assigned to empty permission set groups without enabled permissions.
Where: This change applies to Lightning Experience and Salesforce Classic in Contact Manager, Group, Essentials, Professional, Enterprise, Performance, Unlimited, Developer, and Database.com editions.
Get Notified Before Deleting Permission Sets Assigned to Users (salesforce.com)