CMDBuild Forum

How delete wrong user

Old Versions
#1

Good morning. 

I have a question: I've created a user and it is wrong to "username". 

The application can not change the "username" or delete the wrong user 

What can I do? 

thanks

#2

It is enough that you make not active the account with the check at the bottom on the card
CMDBuild Team

#3
Hi,
how can you be sure it is enough? Many people have different opinion and preferences as well, and I think it's common
for such application as cmdbuild to allow administators to delete users.
I think as well that cmdbuild is a great cmdb tool but the tiny things such as unability to delete users, groups, deleting classes
which were previously populated but already "clean" make people disappointed.
On the other hand I understand that behind the scenes these kind of information are linked somehow to somewhere else therefore they
can't be deleted, but from the other software experience I have a feeling this is just wrong. There must be a way how could be common things done.

Previously Tecnoteca wrote:

It is enough that you make not active the account with the check at the bottom on the card
CMDBuild Team
#4

We understand your opinion but at the moment this is the philosophy of CMDBuild.
We will consider in the future whether to add functions for physical deletions.
We will not do so in the short term because our roadmap for the next 12 months already includes many features to implement.
CMDBuild Team

#5
we also think physical delete is necessary!  
Previously ju wrote:
Hi,
 
how can you be sure it is enough? Many people have different opinion and preferences as well, and I think it's common
for such application as cmdbuild to allow administators to delete users.
I think as well that cmdbuild is a great cmdb tool but the tiny things such as unability to delete users, groups,  deleting classes
which were previously populated but already "clean" make people disappointed.
On the other hand I understand that behind the scenes these kind of information are linked somehow to somewhere else therefore they
can't be deleted, but from the other software experience I have a feeling this is just wrong. There must be a way how could be common things done.
 
 

Previously Tecnoteca wrote:

It is enough that you make not active the account with the check at the bottom on the card
CMDBuild Team

 

#6
I will add my vote for this feature too. It's quite annoying scrolling through so many old/obsolete accounts. It makes user/group management more work than it needs to be. Which in general needs improvement anyway as it's a cumbersome process setting up all the filters and permissions for groups. We need to also be able to delete groups as well. 
 
I understand keeping the accounts for audit purposes but there needs to be better management in place, ie not show inactive accounts in the standard view, archive them or something. 

As an example, we have around 120 active user accounts at any given time (and would like to expand that), with employee turn over high in some areas (India) we have to deactivate 2-3 accounts per month so you can see after just a few years we'd have more inactive accounts than valid active accounts.
 
Previously martin wrote:
we also think physical delete is necessary!  

 

 

#7
Being slightly clumsy, I like that you can't delete certain classes, users due to relationships etc. If you really want to delete a user, do it from the database using PGADMIN, if the user isn't required then it won't have any affect on other classes, processes etc. If it does then you probably shouldn't have deleted them, hence the restrictions
 
On a side note, you say you have 120 active users, are you UK based company? We are looking to implement openMAINT and would like some real world feedback on the system being used day to day in a reactive, ppm environment. Not sure on forum rules but if you could pm me on marcgolborn@hotmail.com
 
Thanks
 
 
Previously Josh wrote:
I will add my vote for this feature too. It's quite annoying scrolling through so many old/obsolete accounts. It makes user/group management more work than it needs to be. Which in general needs improvement anyway as it's a cumbersome process setting up all the filters and permissions for groups. We need to also be able to delete groups as well. 
 
I understand keeping the accounts for audit purposes but there needs to be better management in place, ie not show inactive accounts in the standard view, archive them or something. 

As an example, we have around 120 active user accounts at any given time (and would like to expand that), with employee turn over high in some areas (India) we have to deactivate 2-3 accounts per month so you can see after just a few years we'd have more inactive accounts than valid active accounts.
 
Previously martin wrote:
we also think physical delete is necessary!  

 

 

 

#8

Has anyone tried to remove a user directly from the database?
I tried to remove it with a simple DELETE (DELETE FROM public.“User” WHERE “Id”=99999999;), without success.