📙

Link to section:

In some cases you may want to transform an incoming query, adding an additional limit or increasing the default limit, adding extra includes or restrict the results to a subset of keys. You can do so with the beforeFind trigger.

https://docs.parseplatform.org/cloudcode/guide/#beforefind

What is the issue?

Triggers are suggested to be used to prevent access to data. This should not be recommended as Parse Server provides a dedicated security layer for access restrictions. The docs as they are now encourage unsafe, custom practices for access control instead of using the more elaborate mechanisms of access control that were built for that purpose.

Here is just 1 example: https://stackoverflow.com/questions/73575340/parse-platform-authenticate-a-query-in-a-beforefind-trigger

Can you propose a solution?

Coment should be removed and instead an explicitly warning note should be added to triggers with a link to https://docs.parseplatform.org/parse-server/guide/#security.

Open the Cloud Code guide at the beforeFind section and review the linked Parse Server security guidance. Remove the recommendation that triggers should prevent data access, then add an explicit warning linking to the security guide. Done means the unsafe access-control advice is gone and readers are directed to the dedicated security mechanisms.