Skip to main content

I've noticed in the last few weeks that if I go into the permission set editor (or profile editor) and use the Find Settings search box to try to go to an object, it does not come up. Doesn't work for Contact: Find Settings in profiles and permsets broken?

 

Doesn't work for Account either:

Screenshot 2026-06-19 at 12.08.58 PM.png

 

Doesn't work with the whole word, part of the word, etc. And it doesn't seem to work for any object. 

 

I can get there with more clicks if I go to Object Settings>[object]. But that's annoying.

That quick find had definitely worked for the whole time I've been in the ecosystem.

 

Is this browser? (I use Safari.) Or client? (I'm fairly sure I've seen this in several client orgs, but haven't done a comprehensive survey.) Or release? (Screenshots are from prod for an org on Summer '26)

2 respuestas
  1. 24 jun, 16:00

    Likely a browser + Summer '26 UI regression, not your org config.

    A few things worth checking:

    1. Isolate browser first

     

    Try the same org in Chrome or Firefox. If Find Settings works there, it's definitively Safari/WebKit-specific — not your org or release config. Safari has historically had issues with Salesforce LWC-based Setup UI components.

    2. Check the Known Issues site

     

    Search permission set find settings at issues.salesforce.com — if others have hit it post-Summer '26, it will likely be logged there. Worth upvoting or adding yourself as "Affected" to push priority.

    3. Workaround in the meantime

     

    Object Settings > [Object] is the reliable path. Also works: Setup Quick Find → type the object name directly — takes you to the Object Manager page where you can navigate to Object Access and see all profiles/permission sets in one view, which is arguably better than the Find Settings box anyway.

    4. Raise a case with Salesforce Support

     

    Given you've seen it across multiple client orgs on Summer '26, that cross-org pattern is exactly what Support needs to escalate it as a platform regression rather than an org-specific issue.

     

    My read: Summer '26 likely shipped a UI change to the enhanced Profile/Permission Set editor that broke the search component in WebKit. Chrome-based browsers tend to catch these regressions later or not at all.

0/9000