Profile filtering is enforced in Winter ’27: what changes and how to check
The short answer: The Enable Profile Filtering release update, available since Summer ’26, is enforced in Winter ’27. Once it applies, users see only their own profile name unless they hold the View All Profiles permission. Anything that reads another user’s profile name, such as a Flow, validation rule or Apex class, can then get a blank value instead of an error.
Say a sales manager complains that opportunities from the partner team aren’t routing to the right queue. Nothing was deployed. The Flow hasn’t changed in a year. It checks whether the record owner’s profile is “Partner Sales”, and since the update the profile name comes back empty for the person who triggered it, so the condition is never true. Nobody sees an error, which is why this one is worth testing on purpose.
Features vary by edition and license. Check the release notes for your org before you rely on any of this. This is one item from our Winter ’27 round-up for admins.
What does the Enable Profile Filtering release update do?
It restricts users to seeing their own profile name. According to Salesforce Ben, they see other profiles only if they have the View All Profiles permission. Salesforce Break says the setting is enabled by default from Summer ’26, and Salesforce Ben says it was added in Summer ’26 and is enforced in Winter ’27. Setup > Release Updates > Enable Profile Filtering has the testing and activation steps.
Salesforce Ben lists it with a note that you need to act only if users must see other profiles. That undersells the risk a little. The users don’t need to look at profiles. The code running as them does.
Is it enforced yet, and who is affected?
Probably, for your org. Salesforce Dictionary reports Winter ’27 production waves on September 4, October 2 and October 9, 2026. Salesforce Break’s screenshot of the Release Updates screen showed a completion deadline of September 1, 2026. Dates move, so open the Release Updates screen and read the status rather than trusting any post, this one included.
You’re affected if something running as a user without the permission reads another user’s profile name. Reported examples:
- A Flow that branches on the record owner’s profile name.
- A validation rule that compares profiles.
- Apex that queries
User.Profile.Namefor someone other than the running user. - Reports and formula fields that display the profile of another user.
- Managed packages that route by profile. Ask the vendor.
Salesforce Dictionary adds that the failure is partial: automation reading another user’s profile name usually gets a blank value rather than an error. That’s the reason a test run as a system administrator passes. Admins can see everything.
How do you check before enforcement, or after it?
Find the references first, then test as a standard user in a sandbox. Salesforce Ben’s preparation steps are a sensible order:
- Search your metadata for anything that references another user’s profile name: validation rules, Flows, Apex, reports and formula fields.
- In a sandbox, refactor those references, or add View All Profiles as a stopgap.
- Enable Profile Filtering in the sandbox and retest.
- Deploy to production, enable the setting, and run a final regression test.
For step 3, use login-as. Salesforce Dictionary’s advice is to walk the critical paths as a standard user, and to repeat the test for each profile if you’ve got several cut-down ones. The reasoning is simple: a sales rep and a service rep may get different results from the same Flow.
If it’s already enforced in your org and something has gone strange, start with a debug log on a failing record and look at what the profile value actually was. A blank where you expected “Partner Sales” tells you most of what you need. If you would rather hand the search-and-test work to someone senior, release readiness is part of our managed admin service.
What is the View All Profiles permission, and should you grant it?
View All Profiles is the permission that lets a user see other profile names. Grant it to the people and processes that genuinely need to see them, such as admins and operations teams. Salesforce Dictionary calls it the “escape hatch” and advises treating it as a fallback, because giving a broad visibility permission to undo a visibility restriction defeats the purpose.
The same source says users with certain other permissions, such as Customize Application and Manage Users, are also exempt, eight bypass permissions in all, though it names only three. We couldn’t confirm the full list from a primary source, so check the release note. If your admins already hold those, they’re probably fine, which is also why admin testing proves nothing.
The better fix is usually to stop checking profile names. A Flow that asks “is the owner’s profile Partner Sales” can ask about a custom permission, a field on the user, or a permission set assignment instead. Those are stable when profiles are renamed or cloned.
What does this say about profiles versus permission sets?
It says profile names are a weak thing to build logic on, and that Salesforce keeps tightening the profile. Salesforce Ben reports a Salesforce statement that the Spring ’26 end-of-life for permissions on profiles is no longer enforced, while still recommending a permission set-led model. The article’s date is unclear, so treat the exact timeline as unconfirmed.
A reasonable direction, offered as opinion: keep profiles minimal, put permissions in permission sets and groups, and make automation depend on what a person can do, not what their profile is called. Then a profile rename, a clone or this release update changes nothing about your logic. If you want to see where permissions come from in your org, a user access review is the natural next job.
What to do Monday:
1. Open Setup > Release Updates and note the status and date of Enable Profile Filtering.
2. Search Flows, validation rules, formula fields and Apex for “Profile.Name” and “$Profile”.
3. In a sandbox, log in as a standard user from each major profile and run the three processes that depend on profile checks.
4. Decide who gets View All Profiles, and give it through a permission set, not a profile.
Where we come in
Watchbill, by GTM Cloud, is pre-release and isn’t publicly listed yet. Today it shows what each person can do and which profile, permission set or group grants it, and compares two users or sets. That helps with the permission side of this clean-up. It doesn’t scan your Flows or Apex for profile names, and version 1 changes no access. Join the Watchbill pilot if untangling profiles is next.
Questions people ask
Do I need to do anything for profile filtering?
Only if something reads another user’s profile name. Salesforce Ben says admins need to act only if users must see other profiles. Search your Flows, validation rules, Apex and formula fields first. If nothing references another user’s profile name, there’s nothing to fix, but a sandbox test is cheap insurance.
Will profile filtering break my Flows?
It can. A Flow that checks the owner’s profile name may get a blank value as a user without View All Profiles, and it fails quietly rather than with an error. Test the Flow as a standard user. If it branches on profile, rewrite it to use a permission or a user field.
Can I turn profile filtering off?
Release updates are enforced on Salesforce’s schedule, and Salesforce can delay, change or cancel them. Once enforced, the release update isn’t a switch you control. Your lever is View All Profiles for the users and processes that need it. Read the update’s status in Setup > Release Updates for your org.
Sources
- Salesforce Ben: top 12 Winter ’27 features for admins: release update status, default behavior, View All Profiles.
- Salesforce Ben: Winter ’27 what to expect and how to prepare: what can break, preparation steps.
- Salesforce Break: field access and permission changes in Summer ’26: Summer ’26 default, Setup path, deadline screenshot (secondary source).
- Salesforce Break: Winter ’27 release updates for admins: enforcement and testing (secondary source).
- Salesforce Dictionary: Winter ’27 enforcement shuffle: blank-value failure mode, bypass permissions, release waves (secondary source).
- Salesforce Ben: permissions on profiles, latest retirement updates: Salesforce’s stance on profiles versus permission sets.
- Salesforce release note: Enable Profile Filtering: the release update, as linked from Salesforce Ben (the page would not load for us).