A tour · 4 stops · 1 min
Keeping Salesforce running
Changes to permissions and the platform beneath your customizations, alongside the new products.
This is the tour’s text. In 3D each stop frames the notes it talks about; every stop below links to its view.
A tour · Keeping Salesforce running
Security is the largest category
Jev, the classification model, places 9.9% of the archive under Security & Identity, ahead of Service. Changes to permission sets, authentication and sharing accumulate across the whole period, including years whose headline products belong to other categories.
See this stop in 3DInfrastructure & Ops · Summer ’25
An instance move can reach your API clients
Salesforce tells integration teams to replace instanced API URLs with My Domain URLs, to avoid disruption when an infrastructure update changes the instance name. The endpoint an existing client calls becomes part of the release work, even if its business logic stays the same.
See this stop in 3D2008 – 2026
A smaller share, more developer notes
The developer share falls from 25% to 4.9% of annual notes, while its count rises from 108 to 227. The category occupies less of a much larger archive, with more documented changes to follow.
Winter ’27 is a preview in this archive.
See this stop in 3DChanges flagged as potentially breaking
Changes that can affect existing customizations
Jev flags 29% of security, infrastructure and developer notes as potentially breaking. This subset includes changes to permissions and retired APIs. It brings compatibility into view alongside new features, with each point linked to Salesforce’s stated scope.
The flag is a model’s reading of the note, not a finding about your org.
See this stop in 3D