|
: 10 : 10 : 0 |
Currently, administrators have no control over what happens when an owner deletes a community/wiki/blog/activity. There is no soft deletion capability. There is no way of easily restoring it to the environment if the deletion was done errorneously or maliciously. There is no way to limit some owners to do everything but delete.
This really comes into play with shared resources like communities that have lived for a long time. It takes only one idiot to be given ownership of a community to help manage membership and have them delete the community by accident when they were trying to delete a member. If that happens, there is no CTRL+Z to allow admins to put it all back in place. Instead, Connections acts like it's 1990 and just blows everything away. You do not pass go, you do not get $200. This is not the way an enterprise collaboration platform should work.
I would suggest the following:
|