When using an authoring instance to manage several websites with different templates one of the biggest issues is that there is no (easy) way to filter templates so that they are usable only in the "right" tree.

For example we would like to have two tree, e.g.
+ site-one
+ site-two

and make some templates only available under site-one and others only under site-two.

This can only achieved in magnolia at the moment by setting up two different users, which have visibility only on one of the website tree/site and denying permissions for them on unwanted templates. This is mostly unusable and there isn't any way to have a user which can edit both trees with the "right" templates only.

We could implement a "template filtering" in different ways... we though about:

• filter templates on paths: adding a path or regexp to the template definition which defines where the template can be used
• adding a parent/child rule to the template definition: a certain template could be used only in a tree where another specific template is used (e.g. the "content site-one" template could be only used in a tree under the "home site-one" template)