Hi

The start node / multiple start node functionality is great for restricting what appears in the content tree but I noticed one potential issue. If you still want users to be able to use the related links editor to link to pages outside of the start node (or its children) you need to change the start node to the root and add browse permissions to the root node down and then individually expand the permissions for the pages that need editing rights

Whilst it works fine, I now have a content tree that shows all the pages but I can't see which ones have extra permissions until I click on it. This is a user experience issue more than anything.

If there is a way to restrict to start nodes but still allow pickers like related links to look across the tree. I would love to know how?

Dave