This make managing the page security very difficult if this is true. The portal pages are a tree and each node in the tree "should" be able to declare the security for itself and it's subtree overriding inherited attributes if desired. For example the tree below | A | /\ | B C | /\ | D E | If node A is unrestricted and view/view recursive then nodes B & C should be visible by default to all. However, node C should be able to override inherited attributes and change security to be restricted for itself and it's subtree. Node C should also be able to terminate recursion of inherited attributes. Tom View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4110367#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...