Communications & Readiness Connect

**Important Update: Platform Identity - Login Page Behavior Change impacting users logging in via login.salesforce.com and test.salesforce.com **What's changing

Email Becomes the Default Login Option: Login using an email address will become the primary default option on the standard login pages login.salesforce.com and test.salesforce.com. Making email the default login creates a unified, user-friendly process across Salesforce entry points. Users can still opt to log in using a username by clicking "Login with Username" on the login page.

Rollout timeline

This change is being deployed on a rolling basis across environments:

• Rollout to Sandbox environments began in late August and is expected to complete by September 30, 2026.
• Rollout to Production environments will begin October 5, with a majority completing in early November 2026.

** Note: This update applies to UI logins on login.salesforce.com and test.salesforce.com. Default email login does not apply to custom My Domain login pages or Experience Cloud login pages.

What you should do now

• Inform Your Users: Let your team know that email login will be the standard prompt, but they can select "Login with Username" at any time. Registered passkeys will continue to work seamlessly with both login methods.
• Check Shared or Unmonitored Accounts: Ensure users who log in do not rely on shared email accounts or unmonitored mailboxes, as email-based login requires access to incoming messages.
• Update Automated UI Tests: If your organization uses automated scripts or tests that log in through the Salesforce UI, update them to prevent disruptions:
• For Username-First Login: Update automated tests to submit the username, click Log In, and then enter the password.
• For Default Email Login: Update automated tests to click Login with Username first, or navigate directly to the username login screen by appending ?login=1 to your login URL (e.g., https://login.salesforce.com/?login=1).

For additional information, review the Prepare for Login Changes article or reach out to Support via Salesforce Help.

🎉 Big shoutout to our incredible Forum Ambassador @Bradley Weller for an awesome deep dive on "Send Opportunity Product Tables in an Email Supporting Multi-Language"!📘 Check out the article here >> https://help.salesforce.com/s/articleView?id=005460943&type=1

🔍 Found it helpful? Have thoughts to share?

 Let us know by clicking the "Yes" or "No"  button at the bottom of the article—your feedback helps us improve!> 🔍 Found it help" style="display: block;" /> #Flow

🎉 Big shoutout to our incredible Forum Ambassador & Salesforce MVP @Ajaypreet Singh Saini for an awesome deep dive on "Display Record URL as a hyperlink in Chatter post using flow"!📘 Check out the article here >> https://help.salesforce.com/s/articleView?id=005460491&type=1

🔍 Found it helpful? Have thoughts to share?

 Let us know by clicking the "Yes" or "No"  button at the bottom of the article—your feedback helps us improve!> 🔍 Found" style="display: block;" /> #Flow

*** Important Security Update: Enforcement of IP Allowlisting in Marketing Cloud Engagement on September 23, 2026 ***As part of our commitment to strengthening the default security of the Marketing Cloud Engagement platform, Salesforce is requiring the use of the login IP allowlist in blocking mode for all accounts. We have identified that your instance doesn't use the login IP allowlist in blocking mode. On September 23, 2026, we will enable it on your behalf.

Next Steps & Timeline

To help minimize potential disruption, we reviewed your recent login activity and compiled a list of recommended baseline IP addresses to include on your login IP allowlist. On September 23, 2026, we will enable blocking mode for your instance. After this date, users can log in to your Marketing Cloud Engagement account from an IP address on the allowlist.

Configuration Impact and Customer Responsibility

No action is required before September 23, 2026. To ensure your configuration is applied correctly, we recommend waiting until after September 23, 2026, before making any changes to your login IP allowlist settings. If you have any concerns, contact Salesforce Support.

After September 23, 2026, you are responsible for reviewing and maintaining your login IP allowlist. Monitor your login IP allowlist access logs on an ongoing basis to identify new IP ranges to add.  See View the Access Log, Add IP Addresses to the Allowlist, and Edit an IP Range.

When we enable blocking mode in your account, you can expect these changes:

• We will apply a Salesforce-recommended baseline IP list consisting of standard /24 (256 address) IP ranges. These ranges are based on IPs observed to successfully authenticate to your instance over the last six months, excluding known malicious IPs.
• "Log Violations and Deny Access" (blocking) mode will be enabled at the EID level for both UI Login and API access, with the IP ranges uniformly applied to all Business Units (BUs).

Resources

• Mandatory IP Allowlisting in Marketing Cloud Engagement
• View the Access Log
• Enable the Login IP Allowlist
• Add IP Addresses to the Allowlist
• Edit an IP Range

#Marketing Cloud Engagement #Marketing Cloud

*** Important Update to Amazon AI Features on your Salesforce Voice Account | Action may be required ***This is an important update regarding your Salesforce Voice environment and the proactive step we are taking to protect your account from unexpected billing charges.

What’s changed

As previously shared, Amazon, the underlying infrastructure provider for Salesforce Voice with Amazon Connect, recently introduced a new AI feature set: Amazon Connect Customer. This capability was deployed and enabled by default across all Salesforce Voice with Amazon Connect customer instances by Amazon.

What we're doing

Our priority remains transparency and ensuring that you only pay for services you actively choose to consume. Because this feature set was not included in your existing order form and is not part of the underlying product sold by Salesforce, we are proactively disabling additional AI features for Amazon Connect Customer across your account effective in the Winter ’27 release, which began on September 2, 2026. This change is rolling out across environments for Winter ’27, beginning with sandbox and moving through production.

Following the release, your account will have Amazon Connect Customer Basic functionality. We are taking this action to ensure you don’t incur unintended or unauthorized charges on your next billing cycle.

Your choice to opt in

Some organizations may want to leverage Amazon’s advanced AI capabilities to enhance their Salesforce Voice experience. You have full control to opt into AI features for Amazon Connect Customer if these fit your business needs. 

Please note that AI features for Amazon Connect Customer require a paid, usage-based add-on. If you choose to enable this add-on feature, usage for that add-on will be billed at 2.1× from the standard base rate. These charges originate from the underlying telephony provider's pricing and will be applied to your account in accordance with your agreement and the applicable rate card. By enabling the capability, you acknowledge and accept these charges.

To enable AI features for Amazon Connect Customer in Salesforce Voice with Amazon Connect, see a help article in an upcoming email communication prior to Winter ’27.

Billing acknowledgement: By choosing to manually enable this feature set, you are explicitly opting in to the service and agreeing to the associated 2.1x increase in usage costs.

SummaryWe apologize for any confusion caused by this upstream change from Amazon. We remain committed to ensuring that you have full control over your environment and your budget.

If you have any questions, require assistance assessing Amazon Connect Customer features, or want to discuss how this impacts your current configuration, please reach out to your Salesforce Account Executive or contact Salesforce Support. For additional information, review this Help Article.

Thank you for your continued partnership. 

#Service Cloud Voice

*** Important Update: Associate a B2C Commerce instance to your Managed Runtime production environment(s) by Sep 29, 2026 ***Salesforce is limiting how Managed Runtime (MRT) determines production environments. Currently, you can set any environment to production, regardless of whether it’s connected to an instance. This creates a lot of traffic, which harms the accuracy of monitoring and incident response for everyone on the platform.

To reduce traffic and improve capabilities, Salesforce is limiting which environments can be flagged as production. Starting September 29, 2026, an environment can be flagged as production only if it’s associated with a Staging or Production B2C Commerce instance.

Log Center logs and Log Center metrics aren't affected by this change. Both stay independently configurable on any environment, regardless of instance tier.

To keep production monitoring and related features on these environments, associate each one with a Staging or Production B2C Commerce instance before September 29, 2026.

1. Open Runtime Admin and go to the Environment Settings for the environments listed above.
2. Associate the environment with a Staging or Production B2C Commerce instance.
3. Confirm the production flag is still on after you save the association.
4. Redeploy the current bundle in that environment. This ensures the change takes effect immediately rather than waiting for your next scheduled deployment.

If you don't associate an instance by the deadline, you will lose production monitoring. Your Log Center logs and Log Center metrics settings won't change.

Need help?

Contact Salesforce Customer Support if you have questions about which instance to associate.

#B2C Commerce #B2B Commerce

⛰️🛡️ New Hands-on Workshop for Premier & Signature Developers: Secure the Code: Find and Fix Vulnerabilities (DEX003) 

Insecure custom code is one of the leading causes of data breaches. In this 90-minute instructor-led workshop, you'll step into the role of a security-focused developer to audit and remediate critical vulnerabilities in Lightning components and Apex classes through a series of challenges.  

This hands-on workshop teaches developers how to prevent script injection, encrypt data securely, manage secrets, and control record access. You'll also learn to identify authentication flaws and data exposure risks. this practical workshop is for developers working with custom code at any stage: 

• Build new code — learn to bake in secure patterns from the start, so vulnerabilities never make it to production
• Review existing code — sharpen your eye for spotting injection flaws, insecure data handling, and access control gaps in code you didn't write
• Maintain and harden production orgs — Use the Developer Console or VS Code to apply Salesforce platform security best practices that protect applications from evolving threats

Sessions are live and available! :calendar:

• Wed Sep 2 — 3:30pm CET/Paris
• Tues Sep 8 — 3:30pm ET/New York
• Mon Sep 21 — 9am IST/Kolkata
• Mon Oct 19 — 9am ET/New York
• Check the session listings for additional workshops across regions :tada:

Interested in the Admin version of this security workshop? Check out upcoming sessions for ADX012

👉 Premier and Signature customers — Register today on Trailhead Academy — Course code: DEX003

#Salesforce Developer #Slack Developers

🎉 Big shoutout to our incredible Forum Ambassador, @Smitha Thomas for an awesome deep dive on "Make a Feild Avalible as a Dashboard Filter!📘 Check out the article here >> https://help.salesforce.com/s/articleView?id=005408536&type=1 

🔍 Found it helpful? Have thoughts to share?

 Let us know by clicking the "Yes" or "No"  button at the bottom of the article—your feedback helps us improve!> 🔍 Found it helpful?" style="display: block;" /> #Reports & Dashboards

🎉 Big shoutout to our incredible Forum Ambassador, @Manoj Nambirajan for an awesome deep dive on "Send Opportunity Notification for Specific Stage Movements"!📘 Check out the article here >> https://help.salesforce.com/s/articleView?id=005393369&type=1 

🔍 Found it helpful? Have thoughts to share?

 Let us know by clicking the "Yes" or "No"  button at the bottom of the article—your feedback helps us improve!> 🔍 Found it helpful?" style="display: block;" /> #Flow

⛰️ 🔐 New Hands-on Workshop for Premier & Signature Admins: Secure the Org: Find and Fix Vulnerabilities (ADX012)

 Misconfigured security settings are one of the leading causes of data breaches. In this 90-minute instructor-led workshop, you'll step into the role of an internal security auditor to identify and fix real Salesforce vulnerabilities across the most common misconfiguration areas. 

This workshop was adapted from a fan-favorite capture-the-flag game that has been a hit at live Salesforce events — now available virtually so more admins can play! This practical workshop is for:

• Newer admins — you'll find the challenges approachable and manageable. The hands-on format makes security feel less daunting and more actionable
• Seasoned practitioners — you'll likely discover security settings you haven't previously been aware of
• All learners — challenges are independent of each other, so you can move at your own pace, skip ahead, and circle back with no pressure

Sessions are live and available!

• Fri Jul 31 — 9:00am ET [AMER]
• Mon Aug 3 — 3:30pm ET [AMER]
• Tue Aug 11 — 10:00am CET [EMEA]
• Check the session listings for more workshops across regions 

➡️ Premier and Signature customers — Register today on Trailhead Academy — Course code: ADX012

#Security