It should absolutely be optional. For me it's about admin usability... I used DNN for 6 years with no problems regarding user account deletions. Now with DNN 5 I have problems, and for no good reason. It's that simple. Another reason is privacy. I have one client who runs an adult membership site. The privacy statement is very clear about what happens when the accounts are deleted - they are deleted immediately with no records available to the owner. I haven't yet figured out how to approach this, but it's basically a fail at this point. Then, for me as a multi-portal host, it's about not filling up the db with massive lists of dead accounts. If someone had a username and then deleted it, then that username should be freed up for anyone to use. It's bizarre to me how certain fundamental functionality evades DNN for years, yet totally unrequested features like this one somehow bulldoze their way into the app. Where was the call for this.. (that's rhetorical) I've been planning on using that hard delete script I've seen floating around the place. Does anyone know if it's safe to hard delete in DNN5 at all, or is it going to cause yet more trouble? Regards Rob