The usual reason for not allowing deletion of users in systems have to do with audit trail, logging and such.
A very basic example: If user X was the last one to edit and publish a document, if you deleted that user and then for some reason needed to know by who, why and how that page was created/changed/published the data would be incomplete.
Not being able to delete a user in an environment with audit trail and rollback features is definitely a good thing.
You could argue that some more permanent kind of inactivation would be nice to have, some that stored the deleted user out of sight for an administrator doing everyday work.
[quote=Frekvi]But do anyone know why? Have you found any workaround? Will try different things now, and will tell if I find any workaround.
\Fredrik[/quote]
Well I guess the answer to Why? is as I wrote; If you delete a user in an environment with audit trail and rollback functions you would end up with incomplete and inconsistent data. Being able to delete a user in such a system would be bad design, in my opinion.
But having an option to remove the inactivated user from the normal admin GUI would be a nice feature.
Perhaps there could be a quick search of the audit trail to see if the user is tied to any activity. If it isn't, then allow it to be deleted.
Sometimes users get created accidentally and are never used.
It would be nice to be able to create folders in the users tree view. Then you could move inactive users to a separate folder. That would solve the issue of inactive users taking up space in the tree view, and be nice to have for other reasons as well.
Anyone care to create an item in the issue tracker at codeplex?
I suppose I might add that a notifier that creating a user isn't reversible would be helpful, too, now that I have the scarlet letter of two never-to-use-again user accounts in my db soup ;)
I understand the idea of an audit trail, but it's pretty irritating for top level admins not to have this ability. Fortunately, it didn't seem to cause any problems when I deleted the row right out of the database.
Hi to all, for me the problem is to manage all documents related to the user you'll want to delete.
I'm now working to a maintenance project with this functionality:
- Versions manager (to show, delete by count, delete by date) -
Media Folder manager (to delete unused Folders and Files on File System) -
Log manager - User Manager (to delete a user)
The last one will allow Admins to delete users.
This is what I'm trying to do:
Check if the user who wants to be delete is related to any documents.
How to delete an umbraco user??
Anyone - please?
How do I actually delete an umbraco user?
Thank you.
Scott
You cannot delete a user. You only can deactivate the user.
Thomas
Yeah I figured, thats why I was asking on how to delete it :)
Thanks Thomas.
Sorry to bump this, but is there a particular reason you can't delete a user?
Fredrik
Hey Frederik,
Yup no delete option :(
The usual reason for not allowing deletion of users in systems have to do with audit trail, logging and such.
A very basic example: If user X was the last one to edit and publish a document, if you deleted that user and then for some reason needed to know by who, why and how that page was created/changed/published the data would be incomplete.
Not being able to delete a user in an environment with audit trail and rollback features is definitely a good thing.
You could argue that some more permanent kind of inactivation would be nice to have, some that stored the deleted user out of sight for an administrator doing everyday work.
But do anyone know why? Have you found any workaround?
\Fredrik
[quote=Frekvi]But do anyone know why? Have you found any workaround? Will try different things now, and will tell if I find any workaround.
\Fredrik[/quote]
Well I guess the answer to Why? is as I wrote; If you delete a user in an environment with audit trail and rollback functions you would end up with incomplete and inconsistent data. Being able to delete a user in such a system would be bad design, in my opinion.
But having an option to remove the inactivated user from the normal admin GUI would be a nice feature.
Thanks daniel! That's what I needed to hear ;) Then I got an answer for customers who like to know everything..
//Fredrik
Yeah me too, nice... and as you said it would be nice to remove it from the GUI.
Perhaps there could be a quick search of the audit trail to see if the user is tied to any activity. If it isn't, then allow it to be deleted.
Sometimes users get created accidentally and are never used.
Alright this thread is two years old, but I'd love to remove a user I sett up merely as a test, a user that has no node activity associated with it.
It would be nice to be able to create folders in the users tree view. Then you could move inactive users to a separate folder. That would solve the issue of inactive users taking up space in the tree view, and be nice to have for other reasons as well.
Anyone care to create an item in the issue tracker at codeplex?
I suppose I might add that a notifier that creating a user isn't reversible would be helpful, too, now that I have the scarlet letter of two never-to-use-again user accounts in my db soup ;)
I understand the idea of an audit trail, but it's pretty irritating for top level admins not to have this ability. Fortunately, it didn't seem to cause any problems when I deleted the row right out of the database.
you can also go into the DB and delete them there. but beware, for the reasons stated above!
Yea, prudence wins over OCD; so I haven't fished the user out of my db. Other, bigger, tastier fish to fry.
Hi to all,
for me the problem is to manage all documents related to the user you'll want to delete.
I'm now working to a maintenance project with this functionality:
- Versions manager (to show, delete by count, delete by date)
- Media Folder manager (to delete unused Folders and Files on File System)
- Log manager
- User Manager (to delete a user)
The last one will allow Admins to delete users.
This is what I'm trying to do:
Check if the user who wants to be delete is related to any documents.
If User haven't related documents
In this case the User will be delete (easy)
If User have 1 or more related documents
In this case there are 2 steps to do:
check which documents are related to this user
move them to a generic user
delete old user
I hope to release it as soon as possible
Any suggestion is always welcome ;-)
Happy heaster to all
Adriano
Adriano, I thought this post was DEAD but you just managed to REVIVE it... good work.. I am looking forward to seeing your project in action.
Right now I have no suggestions really, but if I get some I will for sure let you know.
Scott
Thank you Scott
Adriano
@Scott
hi Scott,
my project is now published. :-)
You can find it at this URL:
http://our.umbraco.org/projects/falm-housekeeping
. I've got same problem.. and project link doesn't exist..
Luckily I think I can just delete them out of DB as no references.. but this whole user things seems a bit wonky to me!
The project structure has been redone after the release of Our Umbraco v2.0, you should find it here:
http://our.umbraco.org/projects/developer-tools/falm-housekeeping
Steen
is working on a reply...