anonymous wrote : | Ughhhh...this is the case. You must name one user (not a group) as the Admin for CMS. | | Does anyone else think this is a bad idea and worthy of Feature Request? What's the point of having user groups if you still need individual magic accounts? | This is not true anymore. You can designate any Role you like to become Administrators of the CMS including access to the Security Console. You will obviously have to setup your permissions for this Role accordingly. The CmsRootUserName in the configuration file serves a completely different purpose. As explained | <!-- | NOTE: cmsRootUserName denotes a single Portal user that has access to everything in the CMS. Denote this user | carefully and should be synonymous to the 'root' user in a Unix system. By default: this value is the built-in | 'admin' user account. This can be changed to any other user account registered in your Portal | --> | Basically if somehow you mess up your security policy and lock all users out or something like that, you can login with this root user and perform whatever fixes you need to set everything up properly. This feature will save you many stomach dropping incidents at the thought of having to dig through the database data to fix setup mistakes ;) Thanks View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4114283#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...