SPECIALIST COVERAGE
Salesforce Platform: automation, development and security
Guides and analysis for admins, developers and architects building scalable solutions on Salesforce.OrbTrail
Latest
12 stories found
PlatformFlow’s new user context closes a trust gap—but identity still defines the boundary
Winter ’27 can pin screen and autolaunched flows to user context regardless of their caller. The option makes CRUD, field access and sharing predictable, but it does not replace permission sets, customer verification or persona-based tests.
PlatformConsent now crosses two Marketing Clouds. The source of truth still has to be designed
Email, SMS and WhatsApp synchronization reduces fragmentation between Marketing Cloud Engagement and Marketing Cloud Next, but identity, explicit opt-in and universal unsubscribe make deployment a governance project—not a simple list mapping.
PlatformSalesforce kept permissions in profiles. That does not make the profile an access architecture
Cancelling the retirement removes a migration deadline, not the scaling problem. A sustainable model leaves only profile-dependent settings in the profile, composes capabilities in groups, and automates grants, revocation and expiration.
PlatformCity‑Forum shows that securing Experience Cloud requires testing what a visitor can actually read
The campaign does not rely on a platform flaw: it traverses Aura, LWR and self-registration to turn excessive public permissions into automated data collection.
PlatformWinter ’27 has already started for admins: the critical deadline is choosing where to test
Pre-release, the refresh cutoff, sandbox preview and three production waves create an environment problem—not merely a feature calendar.
PlatformSalesforce MFA enforcement: the challenge is proving login strength, not merely enabling a factor
Release-group enforcement separates standard and privileged users, exposes SSO gaps, and turns passkeys, recovery and testing into one identity program.