"david.lloyd(a)jboss.com" wrote : | I could, but why? I think for the initial deployment/evaluation, it's easiest for the end user to just go straight into the console. Remember that it is an administration console, not an end-user application. So there's no real benefit to requiring a login - not from an evaluation perspective, or a prototyping perspective. I tend to disagree.... part of it is an administration console, part is simulating the process.. changing roles/users should be possible with seeing limited taskslists. Maybe the following thing sounds stupid, but if this (imo) basic functionality is not in the console, I will never get it soled to the managers here. It is then not usable for rapid prototyping and we need to develop a full webapp just to simulate the basics of a process. hmm.... "david.lloyd(a)jboss.com" wrote : | In fact it would make it harder since the users wouldn't know what to log in as unless we put the user list on the front page | - something I am unwilling to do, because the user will then have to remove the list to deploy it into production. I tend to disagree to. Often we create dummy users with the role in their name and a number added to it. Easily remembered and very usable. So the issue of the list on the homepage is not a real issue. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4054041#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...