I have several module instances of DMX on different pages. Each of them only gives access to certain set of sub-folders (sub-tree) which is easy to realise in DMX by chosing different local root folders (via module settings). However, if a user now browses by category, DMX displays files which are above the local root folder or in parallel folder branches, which should not be accessible from this module instance.

Example: local root is "Project X" with files from categories "Presentations", "Results" etc. But if I chose "Presentation" I do not only get the presentations that belong to this project, I also get the presentations of all other projects (well, given I have read permission, of course).

Does that seem logical to you?

Hi Mathias,

Strangely enough the answer is 'yes'. The folders are meant to 'organize' not 'protect'. The same goes for categories and search. If you have content that is visible to someone then that content can appear through either of those 3 channels. This is by design. I understand that people might find this weird, but this is how it was first set up. I can imagine that in a distant future I might implement a more strict separation like you suggest, but this is impossible in the current version without the risk of severe performance impacts.

A better alternative in the short run is to develop a custom presentation module for categories limiting to a particular substructure. Then the rest of DMX will not be burdened by any processing done in that module.

Peter