This is not possible at the moment.
We could probably have it, if it becomes a popular feature request and if time permits it or someone contributes to it :)
Ok, thank you for the answer.
My next question is weather I can enable/disable the edit button per portlets and pages. For example, I want only user A to be able to see/click the edit button on portletinstance B when she visits page C (namely her own page). I guess this is not implemented either.
The reason for all these questions on finegrained user restrictions is that I am intending to use the portal to build a community website with personal userpages and let users adapt only their own pages and portlets for everyone else. The "other way around" as opposed to the "usual portal behaviour" where everybody have their own view of shared pages.
Am I way off?
In 2.6 we do the "usual portal behavior" where someone can create his own set of pages for his personal view.
I don't fully understand your use case.
My usecase is this: Each user "owns" a physical page object that is his own. That page has a unique pagename (the name of the user for simplicity). The more users, the more pages will have to be created in the portal. My aim is to only let the owner of the page see the edit button on the portlets (and maybe even not all the portlets). No one else but the owner gets to rearrange and go to edit mode in the portlets. This, I think, could be fixed with the relationship one-to-one between user and role so that user A and only user A has role A and his owned page can be edited by users with role A (namely himself).
conclusion: Every user is the admin of their own page but all other public pages should be set up by some "superadmin".
My question is, can the edit button be switched on/off depending on what user/role sees the page?
Does this idea fit in the "portal model"?
Unfortunately this scenario doesn't quite fit in the "portal model".
You are the first one with that requirement :) You could still dig in the JBoss Portal code to get what you want if you really want to, but i'm afraid you may have to go in the private API subject to changes