DotNetNuke 5.x changed the way users are deleted from a portal.  Instead of actually deleting the user, the user is marked as deleted.  Depending on your situation, this can be a feature or a flaw.  One thing is for certain, the way it is currently implemented in DotNetNuke 5.x is not a complete solution.  DNN Corp is aware of this and will be correcting this behavior in DNN 5.2.  However, this still means that managing deleted users will be different for DNN 4.x and 5.x.  We believe that the profile visibility options in Active Social 1.2 will allow us to offer additional capabilities, address the deleted users behavior and still maintain one codebase for Active Social.

The site administrator can choose which visibility options are available, if any at all.  This gives members the option to choose who could access their profile, whether or not be in the member list/search results or completely hidden.  The administrator can also override the sites for the entire site or a single profile. 

DotNetNuke 5.x admins may see this as an extra step.  When a user account is deleted, they will also need to locate the profile and set the visibility to private or hidden.  DotNetNuke 4.x might see this as an advantage.  They may not want the account to be deleted and prefer the behavior of DotNetNuke 5.x, but just can't upgrade at the moment. 

We are also planning additional features that will make member management much easier for administrators.  An admin should be able to take advantage of the advanced search capabilities in Active Social to locate a member and perform any tasks necessary at that point.  I expect we will see the advanced members tools in the next couple of months. 

More details about the visibility options will be available in the Active Social knowledge base very shortly.