Hi Vitaja,

Thanks for your recommendation, I did that already but I can't find anything similar to what I mean.

I know that you can use Roles to allow users to view/edit only certain Type of Pages.
But the scope is application wide. I think it would be better and easier if someone could specify which page (instance NOT type) can have wich type(s) of documents as children.

This way, cmseditors could only create permited child pages under a certain page instance.

As it is right now, a cmsEditor, must select one among all (role permited) types of pages, when he is about to create a page under a PageItem. This tends to be a little bit confusing for the non expirianced ones.

Imagine there is a site that has a menuitem page named "HOTELS" and another one named "NEWS".

There is a Role named "CMSEditor" that can only see pages of type "NEW" and "HOTEL".

If CMSEditor try to add a Page under "HOTELS" then the CMSesk will propose "NEW" and "HOTEL" pages. But if CMSEditor selects "NEW" then this has no meaning becouse "HOTELS" page is designed to shows only "HOTEL" items.

I, as en expirianced CMSEditor and CMSDesigner can easily understand that there is no meaning in putting a "NEW" under a "HOTELS" page but what about my clients?

And this is just a simple setup. What if the permitted page types for CMSEditor are more than a lot?

I can understand that I could create a new Document Type for every main page of my site and then define allowed children types but this would not be as efficient as the rest of your product is.

Regards,


John