Your vote decides the Salesforce Spring ‘27 Release logo
Which one gets the job?
1️⃣ Biker Astro
2️⃣ Beekeeper Agent Astro
3️⃣ Climber Cloudy
4️⃣ Gardener Codey
Cast your vote here, or vote in our polls on X, LinkedIn, Facebook, or Instagram (or all four!). Voting closes Friday, October 30. The character with the most votes will become the official Salesforce Spring ’27 Release logo.
💬 We asked, you answered! Data 360 integrations is the topic you chose for our next True to the Core Deep Dive.
Join us November 10 for an extended live Q&A with Salesforce Product Managers @Varun Dewan and @Praveen Gonugunta. Bring your questions about Data 360 integrations and get answers directly from the product experts.
Here's what to expect:
✨ The latest in connectors and unstructured data processing
💡 Insights on zero copy architecture
💬 An extended live Q&A with the product team
📅 November 10 | 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 @* Salesforce Developers *
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
Hi there, we'd like to be able to track assets like technology and other purchases used internally i.e. not for sale. We'd like to record things like purchase date, serial numbers, and the vendor.
It seems that the Assets object isn't used for this kind of record keeping.
Is there a best practice, app you use, or solution for a place to house this information?
It depends on the complexity of the data you are wanting to store. If this is simply a case of storing the Asset with a Purchase Date, Invoice No., Supplier, Value etc., then creating your own Custom Object(s) would be the easiest solution. If you have a more complex scenario, bordering on Accounting, an App like this that has a Discount for Non-Profits might help: https://appexchange.salesforce.com/appxListingDetail?listingId=a0N30000004czBREAY
*** 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.
More Information
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:
As a result, my Environment Switcher is now showing 16+ orgs 😅
Problem:
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:
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 🙏
@Michal Wantusiak the picker is two lists mixed together, and only one of them is actually stuck.
If this is the VS Code or CLI org picker, the list is whatever sf org list still has authorized. sf org logout --target-org and the alias drops that org from the picker. It does not delete the org. sf alias set is what makes the two or three you actually use easy to spot.
If the org is still there after a logout, it is linked to your Trailblazer user, not just saved on the laptop. Trailhead playgrounds do that. Open your Trailblazer profile, Hands-On Orgs, and disconnect or delete the old playgrounds. Once that link is gone, the picker stops offering them.
A second email does split the list. It also splits your badges and Trailhead history. I would not do that just to hide playgrounds.
Support cannot hide an org that is still connected to you. Disconnect it, or log the CLI session out. If you need to keep one and stop grabbing the wrong tile, rename it under Setup, Company Information.
We’re happy to share Winter ‘27 Release resources! 🩵
🚨 BONUS: Get ready for FeatureFest at Dreamforce! 🚨 Discover what’s new in the Winter ’27 release, get personalized feature recommendations, connect with experts, earn exclusive swag, and leave ready to get more from Salesforce – all in one exciting Dreamforce experience. Stay tuned – we’ll share more details next week!
Release Matrix can be found here: https://trailhead.salesforce.com/trailblazer-community/feed/0D5KX00000pPZmY0AW
Overview deck can be found here: https://trailhead.salesforce.com/trailblazer-community/feed/0D5KX00000jASjE0AW
**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:
** 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
For additional information, review the Prepare for Login Changes article or reach out to Support via Salesforce Help.
