Deep Validation in Create Permission

Summary Requirement Users should not be able to create an entry with relation to entries they have no permission to. Problem Cannot define "create" validation rule based on a related field. (except self related collections) Basic Example Example In this data model, users should not be able to create a many_collection entry that its one_collection status is draft • many_collection * id * one_collection (m2o) • one_collection * id * status Problem in "create" permission, no option to add rule based on one_collection.status. (except when many_collection and one_collection are same) <img width="991" height="542" alt="Screenshot 1404-04-24 at 14 28 05" src=" /> Motivation This has a wide range of use cases that some results in security issues.. for example in multi tenant architecture: We have a tenant field in each collection and users are limited to add, edit and delete entries…