Hi Eric, 

This blog post may help you in hidding the pages in edit tree

http://tedgustaf.com/blog/2013/4/hide-pages-in-the-page-tree-in-episerver-7/

Hi Shahid

Unfortunatly that only works in episerver 7, and I need it for cms 7.5 :(

Bump.

Has no one had this requirement from a customer before? A "personalized/adjusted" page tree based on roles/accessrights?

I commented on Thomas blog post. If you use EPiServer 7.5, you need to add a Rank property to the query.

public override int Rank { get { return 100; } } //The default queries have 0 as rank

That is great! Thanks a lot Linus, seems to work as intended now :)

Hi Again!

I have another issue. The above method seems to affect the page tree everywhere in the edit mode where you can select pages (link dialog, link list et).

Is there someway to specify so that it's only the editor page tree component/view that is affected? I mean the component where editors navigate the structure of the site.

Hi Eric!

The answer is no, there is no simple way of just manipulating only what the navigation tree shows (at least not that I'm aware of). The code sample that Thomas has done basically changes the entire server side data store for content, so you should be aware that it's affecting all nagivation of content, not only pages.

Hi Linus!

Ah, I understand. It's fairly easy to just manipulate pages since I have access to start nodes, but if I can't control it for a specific view it won't help.

Do you have any other suggestions or examples of limiting what a specific editor can se in the navigation tree? What the customer want's is basically the "Favorites" feature that existed in CMS6R2 where and editor could bookmark certain nodes in the pagetree. That way they don't have to navigate a sometimes huge structure to create content.

My idea was to filter the navigation tree based on access rights so that an editor can only see and create content where they are allowed too. Maybe it's possible to build a custom plugin for this?

Hi again Eric!

The UI is pretty much prepared for this though there is currently no extensionpoint to define the root nodes for the page navigation tree. I did a test and it's åpretty easy to acomplish this so I'm investigating if it would be possible to add support for this, even though this might be in the form of an API or by setting a predefined profile setting.

/Linus

Thanks Linus, that sounds great. We quite often get the question from our customers and it would be a really nice feature :)

Putting a pin in this, and looking forward to hearing more about it in the future :)

Has there been any progress on being able to bookmark pagetree nodes? Has there been any progress in being able to traverse folders in the internal Page or Media Link Dialog to link to content that authors can't read? 
In Ektron, there was a difference between "Traverse" rights and "Read" rights. Out content authors don't need to see every folder when editing pages but still should be able to access all files and pages when inserting an internal link.