Thank you very much, Jon.

It's a good idea, unfortunately, after some studying I think linked schemas wouldn't work for me. If I understood correctly, this way I'll need to manually create a new linked schema for each new client (because filters cannot be generated dynamically) and as far as I know, you cannot create linked schemas programmatically.

The other problem is that some information (table rows) might be available to let's say 3 clients.
I use many-to-many binding tables to keep track of these relations and display only the rows I calculate should be displayed.
I cannot see a way to integrate this with filters.


I'm interested in custom schema implementation in Java, as you mentioned.
Could you tell me something more about this? Point me to the right direction? (I am new to interacting with Labkey via Java)

My idea is that, let's say I can add a column "Folder" to each table and simulate destinations that rows should "belong" to.
When displaying whole table (under the default URL mentioned in previous message), i will first filter table based on user permissions and this way he will only see rows belonging to folders he has at least Reader permissions in.

Or, absolutely sufficient would be to somehow block displaying the entire table under the URL - it's funny but this is really all i need:). Or to dynamically define filters to displaying that table.
Or block that URL (at least to non-admins) somehow or hide all columns from displaying after navigating to that URL.

Are those options possible within a single Java module or do I need to temper with LabKey source code?

Thanks again,
Martin