Obviously from time-to-time I have people asking me to develop an integration plugin for software that was already running when aMember has been purchased. This is not a problem in itself and I have built quite a few and it is not a drama so long as the user information and login/logout processing can be worked out properly. But I think people don't understand the way of things with integration. In most cases integration is that aMember is the controller and the other application does what it is told. Bi-directional sync is possible (I have done it) but it a whole different level of complexity. If a forum is used as an example. The forum has userid, group and some fluff details. The process generally is that aMember controls the userid, password etc it also manages access to the group level access. So if you have 'Free', 'Subscribers', 'Staff' and 'Admin' there would be aMember products that relate to those levels and the control is then achieved. If you say something like 'I will set their access level in the other application' then why are you using aMember? Naturally it is possible to have aMember add new accounts into a third party application and then just leave 'em alone but why manage users in multiple locations, the whole reason I fell in love with aMember was being able to sew together a bunch of disparate applications, change the look & feel to agree with my site and then it all looked like a custom made she-bang. Before playing with your site software setup you really need to understand the way things work and the first consideration should be to make aMember the boss cocky even to the point of suffering some pain in order to make it so, in the end your life will be hugely easier. This rant is now at an end Larry