Backend: Customer grid not filtered accordingly to admin scope

[FloForMagento]

Preconditions and environment

• Adobe Commerce ver. 2.4.5-p8

Steps to reproduce

1. In customer grid, with no filter set, have at least two customers on different websites in results.
2. In System, User Roles, create a new role. In Role ressources, change Role Scopes from All to custom, select only one website.
3. Affect this role to an admin user, log in with that admin user.
4. Go in Customers, all customers

Expected result

Grid should show customers accordingly to admin user scope.

Actual result

Magento throw an exception: "More permissions are needed to view this item."

Additional information

The problem is that Magento don't use admin user scope to filter request on customer_grid_flat. It does control scope after that, in Magento\AdminGws\Model\Model::customerLoadAfter, call to hasStoreAccess return false and lead to the exception.

Release note

No response

Triage and priority

• [ ] Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• [ ] Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• [X] Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• [ ] Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• [ ] Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant[bot]]

Hi @FloForMagento. Thank you for your report. To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

• @magento give me 2.4-develop instance - upcoming 2.4.x release
• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this

• To learn more about issue processing workflow, refer to the Code Contributions.

  Join Magento Community Engineering Slack and ask your questions in #github channel. :warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting. :clock10: You can find the schedule on the Magento Community Calendar page. :telephone_receiver: The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.