* Salesforce Platform *

Ready to explore a new way to build apps and agents? 

Join us October 20 for True to the Core Deep Dive: Builder Central. Salesforce Product Managers @Tiaan Kruger and @Daivat Dholakia will give us a closer look at how admins can use natural language to turn business needs into solutions while staying in control. 

Here’s what to expect: 

✨ A look at Builder Central in action 

💡 Insights from the product team 

💬 An extended live Q&A to get your questions answered 

📅 October 20 | 9–10 a.m. PT 

➡️ RSVP at the link here. ⬅️ 

#True To The Core @IdeaExchange #AwesomeAdmins

@Salesforce Admins Live Sessions, @* Release Readiness Trailblazers *, @* Salesforce Platform *, @* Trailhead Official *, @Trailblazer Community Cove, @Admin Addicts,  @Dreamforce for Admins, @Architect Trailblazers

*** Important Update on: Salesforce Connected App & External Client App Security ***

Welcome to the Salesforce Connected App & External Client App Security Requirement Update: a consolidated view of upcoming changes impacting your connected apps and external client apps and related security settings. You received this email because you’re listed as an admin or security contact for a Salesforce org. 

The list of the changes mentioned in the email can be found here: Connected App & External Client App Security Requirement Updates. Each change also includes a link to a release note or knowledge article detailing the change and timelines.

To prevent authentication failures and service disruptions, Salesforce strongly recommends that you test these changes in a sandbox and deploy necessary updates to production before the enforcement dates.  

Please coordinate with your Salesforce Admin, App Developers, or App Owners to prepare for these changes. If you have questions about the retirements listed, refer to 

Salesforce Help or contact your Salesforce account team.

*** Important Update: Core Security Requirement Updates ***

 Welcome to the Salesforce Platform Security Requirement Update: a consolidated view of recent and upcoming high-impact changes for the Salesforce Platform and related security settings. You received this email because you’re listed as an admin or security contact for a Salesforce org.

The list of the changes mentioned in the email can be found here: Salesforce Platform Security Requirement Updates. Each change also includes a link to a release note or knowledge article detailing the change and timelines. 

To prevent authentication failures and service disruptions, Salesforce strongly recommends that you test these changes in a sandbox and deploy necessary updates to production before the enforcement dates. 

For information about other ongoing security changes, see Connected App & External Client App Security Requirement Updates and Security-Related Product Updates to Marketing Cloud Engagement.

As a reminder, these changes and other ongoing security improvements can generate password reset emails for your users. See the Winter ’27 release note, Security Enhancements May Require Users to Reset Passwords.

If you have questions about the changes listed, refer to Salesforce Help or contact your Salesforce account team.

Hey all 👋

Im hitting a usability issue with the Salesforce Environment Switcher / Org Picker

 and curious how others deal with this. 

Context:

• I work across multiple client orgs
• Im also doing a lot of Trailhead (Agentforce, Superbadges, etc.)
• All of this is tied to a single email / Trailblazer account

As a result, my Environment Switcher is now showing 16+ orgs 😅

Problem:

• I actively use ~2–3 orgs only
• The rest are old playgrounds / trials / historical
• I can't remove them from the list
• Switching or selecting the right org is becoming slow and error-prone

From what I see, this is expected behavior, the org list is built from all accounts linked to your email, and it's not really meant to be manually cleaned. 

Questions:

• Any workarounds to declutter (besides renaming tiles / search)?
• Do you use multiple Trailhead / emails as a strategy??
• Has anyone tried raising this with Salesforce / Trailhead support?

I'm considering opening a ticket, but wanted to validate if Im missing something obvious first.

Would love to hear how you handle this in real life 🙏 

**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

🚀 Apex Log MCP 2.0.1 for Salesforce — AI-Powered Debug Log Analysis!

Debugging Salesforce Apex logs can be time-consuming, especially when you're dealing with large and complex logs.

With Apex Log MCP 2.0.1, you can bring MCP and AI into your Salesforce debugging workflow. 🤖

In my latest video, I cover:

✅ What is Apex Log MCP? 

✅ How to set it up and configure it 

✅ Connect it with an AI assistant using MCP 

✅ Analyze Salesforce Apex debug logs with AI 

✅ Identify errors and performance issues faster 

✅ Practical demo and real-world usage

This is a great example of how MCP + AI can improve the Salesforce developer experience.

🎥 Watch the full video:

https://www.youtube.com/watch?v=QUdbooXcqgs

📺 Subscribe to Salesforce Hunt:

 https://www.youtube.com/@SalesforceHunt

@Agentblazer Community Group @* Sales Cloud - Getting Started *@* Release Readiness Trailblazers *@* Sales Cloud - Best Practices *@* Salesforce Administrators *@* Service Cloud * @* Salesforce Administrators *@* Salesforce Platform *@* Service Cloud *@* Sales Cloud - Getting Started *@* Sales Cloud - Best Practices *@Salesforce Flow Automation