module-defined schema permissions | martin | 2015-05-22 04:07 |
Status: Closed | ||
Hi, Ben. Your solution is pretty clever and functional, thank you very much:) There is just one more thing related I can't make work. I have Folder A, hidden from clients. Module with defined schema containing all the tables is activated only in this Folder A. Folder B is for clients. Here I created linked schema with queries written in a fashion similar to your suggestion. So...If I want to read my custom tables in Folder B, no problem, rows get filtered and clients see only what they are supposed to. If I want clients to also insert data to my custom tables from Folder B (to Folder A), I thought "Submitter" role to Folder A would be sufficient. However, this doesn't work. They need "submitter" + "reader" on Folder A to be able to insertRows. (and giving them reader permissions to Folder A would ruin all my effort:) Isn't this bug? I remember that Submitter role worked OK for inserting to lists. Is there a difference when inserting to module-defined schema? (this module is activated only in Folder A and nowhere else) Martin |
||