[permissions V2] Fix - filter objects to search #12803
Conversation
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
There was a problem hiding this comment.
PR Summary
Added permission checks to the multiple record picker search to ensure users can only search for records they have read access to.
- Modified
useMultipleRecordPickerPerformSearchhook to filter searchable objects usinguseObjectPermissionshook before search execution - Change aligns with existing permission system by preventing unauthorized access to object records in search results
- Implements proper permission boundary at the UI level rather than relying solely on backend checks
1 file reviewed, no comments
Edit PR Review Bot Settings | Greptile
|
🚀 Preview Environment Ready! Your preview environment is available at: http://bore.pub:46960 This environment will automatically shut down when the PR is closed or after 5 hours. |
Suspect IssuesThis pull request was deployed and Sentry observed the following issues:
Did you find this useful? React with a 👍 or 👎 |
In morph relation pickers, we were not taking into account permissions when computing the list of objects to search for, while we should not search for objects we don't have read permissions on (permission denied error)