Content picker search with start node configured not taking user start nodes into account

[Mju-Dwarf]

Which Umbraco version are you using?

13.8.1

Bug summary

When a user with restricted access tries to open a content picker, a list of the nodes are not shown, however the user can search for the pages and find them that way. if the startnode in the content picker has list view enabled the user cant find the child nodes even when searching.
This bug also appears on the Multinode Treepicker

Specifics

I got a user with restricted access.
The user has access to a test page with a content picker or multinode treepicker.
That content picker/multinode treepicker has the start node parentPage and is use to select childPage, the user has access to none of these.

List view enabled on parentPage:
The user can neither see nor search for the child pages.

List view disable on parentPage:
The user cannot see a list of child pages, but is able to search for them.

---

Steps to reproduce

Install a clean umbraco 13.8.1
Create 3 pages.

• Test page
• ParentPage
• ChildPage
  Create a content picker in testpage that with a start node of parentpage.
  Setup dummy content.
  Create a user role with granular permission set to only allow access to testpage.
  Login to test user and try to use the content picker

Expected result / actual result

No response

---

This item has been added to our backlog AB#55161

[github-actions]

Hi there @Mju-Dwarf!

Firstly, a big thank you for raising this issue. Every piece of feedback we receive helps us to make Umbraco better.

We really appreciate your patience while we wait for our team to have a look at this but we wanted to let you know that we see this and share with you the plan for what comes next.

• We'll assess whether this issue relates to something that has already been fixed in a later version of the release that it has been raised for.
• If it's a bug, is it related to a release that we are actively supporting or is it related to a release that's in the end-of-life or security-only phase?
• We'll replicate the issue to ensure that the problem is as described.
• We'll decide whether the behavior is an issue or if the behavior is intended.

We wish we could work with everyone directly and assess your issue immediately but we're in the fortunate position of having lots of contributions to work with and only a few humans who are able to do it. We are making progress though and in the meantime, we will keep you in the loop and let you know when we have any questions.

Thanks, from your friendly Umbraco GitHub bot 🤖 🙂

[NguyenThuyLan]

Thanks @Mju-Dwarf , I was able to reproduce it on 13.9.0-rc.
The correct case should be that content (including search) cannot be selected without permission.

[AndyButland]

Fixed via #19800 and #19871, due in 13.11 and 16.2.