Current state today allows the removal of a user with no checking if that user is a "creator" of an object. This creates orphans, and there is no way to assign ownership or control of the object to another user, such as an admin. An example here at GreenStone is dashboards--we had a consultant build us items, that consultant eventually completed their assignments and was removed from the system. Now we have object created by that person that Admins cannot manage--they cannot delete, alter, assign rights etc. Thus they are orphans-this breaks all standard object security and chain of custody rules.

REQUESTED FEATURE - when selecting a user to remove, the system should provide a complete list of all objects created by that user and allow transfer of ownership to an admin. The system should NOT allow a user to be removed if they have created objects.