To answer your question yourself read this blog entry from gavin http://blog.hibernate.org/cgi-bin/blosxom.cgi/2006/06/22#stages-of-adoption BTW: when the user logs out (via identity.logout the session is invalidated and all Objects are removed. Or if you do not use this function you can call Seam.invalidateSession() yourself. Putting entitys in conversation scope is fully supported in Seam without the need to change the behaviour of the framework. With the security framework you can mark all pages that requires login. All other login can then be accessed without login. When you want really the login within an conversation, start the conversation when you render the login page. (eg propagation="join") In this situation it seems best for me, not to rely on the security framework. Write your own login method. (Look above what i have written about identy.logout) Understanding conversations is one of the hard part of seam. But the docu about that becomes better and better and is now in a good state for easy understanding. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4022514#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...