This release, my post may look different. I had a lot of thoughts, and there was a lot of content. It is sporadic, but I covered each item as its own block.

This is a strange addition, given we are now getting warnings about profiles being deprecated, but they have improved the configuration of searchable objects based on user profiles. This is currently in beta.

For anyone with some setup pages bookmarked, be weary as they may not continue to work as Salesforce is rolling out a new domain for setup: .salesforce-setup.com. Also, make to allowlist if you think this might cause an issue for anyone.

Pretty sure I covered this before, but just a reminder: News, Automated account fields, and Logos are going away, and so is the connection to Twitter. Besides Twitter, this will not affect many.

Ok, so permissions are a big one in this round-up, and I will include everything I could find in the release notes because I think it’s that important. Reminder: Spring ’26 right now is the drop dead date for profiles, and while that seems far off, we will be dealing with it quickly, so get ready.

1. We can now report on custom permission sets, including which users are attached to which permission set. This is a custom report type, so you will need to do some build to run the report.
2. This one is a godsend, as I cannot think of the number of times I have been asked what permissions are turned on in a permission set. Welcome the ability to see what is enabled in your permission set – currently in beta, but who cares! I have already tested this out in a sandbox, and man, does this save time.
3. I’ll be honest I am not sure I understand the purpose behind this one, but maybe with time, it will make sense. They have added a recalculate button to the permission set groups to help with failures.
4. What feels like 400 years later and probably several different Chrome plugins, Salesforce finally allows us to see the API names of fields in the permission set. I wish this was also coming to profiles so we could better understand as we migrate, but I will still take it.
5. Assuming you have permission set groups with a whole bunch of permission sets attached to them, this will be helpful to you. You can now see the count of permission sets included in a group.
6. Count limitations have been increased on the number of things you can filter a user by when assigning through the User Access Policies that Salesforce previously introduced. This is still in beta, but I think it is now public.

Dynamic forms got another update in this release. Any object that is LWC enabled can now be converted to a dynamic form. This includes standard objects. There are only a handful of objects left that do not meet this. Also included are mobile users, who can now appreciate the wonders dynamic forms offer. Something else that goes well with this is the ability to add Mass Quick Action buttons to related lists, allowing a user to update multiple records at once.

I doubt some people get excited about sharing updates, but we got two goodies in this update. We got the ability to finally report on who has access to an account through a new custom report type and be able to run reports on public groups (this one will be essential for a later post).

Another who did what where update that I am very interested in is Audit History on Opportunities. This allows you to see changes in Opportunity Splits and Opportunity Team members. I am hoping this will save some people headaches in the future.

A somewhat confusing update, based on the title vs. what it says in the subscription combined with little information provided, is that Web Quote Line functionality and Web Quote document functionality are being deprecated. I did some additional digging on this and found a trailhead community post where Salesforce says that Web Quotes no longer serve the value they used to. It might be time to move away if you are still using it.

In other sorts of CPQ news, there is a new behavior on Order when saved. This new behavior checks to ensure that if a child record (order product) is updated and impact should happen on the parent record, the behavior goes through.

A nifty sales tool coming out in this release called Intelligence View applies to both Contacts and Leads. It provides a home base for each object and allows reps to see everything in a dashboard-like form, leveraging the activities as the baseline. I have yet to learn about the customization options, but it looks interesting from the high level.

There have been several updates in the forecasting world, including a refreshed UI for the home page. There is also an update directed to managers, allowing them to decide on an opportunity-by-opportunity basis whether it should be in or out. General forecast users also get an update, where now, in the rollup view, more details are available on hover – allowing you to see what you need to quicker.

I swear, every time I write one of these posts now, Flow is the winner of the most updates, which is not any less accurate with this release.

1. Reactive screen flows – there are too many updates here to go through them all (this post is already long). Conceptually, though, this concept is fantastic.
2. No more ugly error messages that users do not know what to do with. Now, you can create custom error messages!
3. You can now do HTTP callouts directly from a flow. No code is needed, how about that for click-not-code.
4. Transform your data from one object to another – while they don’t say this, I feel like this is the type of mapping we get when converting a lead, and now we can have it anywhere.
5. One step closer to the concept of Draft in Flow, so we can save and come back later like most humans have to.
6. Flow Trigger Explorer gets some nifty search filter options.