Deleting a user

[tahdesign1]

We have the free Vault right now (2012) and I am about to move to pro 2014.

As a method of "releasing" files in the free Vault I had a number of fake users for specific production areas with the words Release in the name.

These users NEVER created any files. However when I want to release and protect a given design, I would log in as that fake user. Then I would check out all the design files WITHOUT downloading the files. This basically left these files locked by being checked out to that fake user. 

So I am trying to tighten some things up before we move for the upgrade where I will have true "Releasing" ability. The one thing I am doing trying to get ride of these fake users. I make sure that the fake user does not have anything checked out but I do not see where I can actually delete them.

Is it possible to deal a user?

[cbenner]

The short answer is, no.  Users remain in the database to preserve any legacy data that may be tied to that user's account.

[tahdesign1]

Yeah I was afraid of that and kind of already knew the answer. I can rename the users so I guess i can do that to force the down bottom. These users never actually created any content. However they were used to check stuff out to (without downloading) in order to lock it up.

[cbenner]

Not sure if it's already been suggested, but you may want to look in the Idea Station.  This would be a good request:  The ability to create and delete "Test" users in the Vault, whose actions are not needed for any legacy data.  I think that would be useful.

[ryan]

Since one core feature of vault is to "capture history", deleting users is not an option (otherwise, you wouldn't have an accurate history of who did what).   However, they can be disabled or renamed.

-Ryan

[tahdesign1]

I agree that design change history is one of the core reason for teh Vault. However, the users that i am talking about NEVER made a design change. They did check files out WITHOUT downloading from the Vault in order to lock them up.

I will be renaming them with something like ZZZ in front of the names to force them to the bottom of the list.

I also like the previous suggestion of posting this on the Idea station in the light of have test users that you can get rid of.

[BeKirra]

I don't know much about vault.

Just a quick question.

In administration, would changing the role of those "fake users" be the answer? Thanks.

BTW, this is the 1st time that I know the user's name can't be removed from the database.

[cbenner]

Well, the bottom line really is that leaving a user name in the list does nothing but take up space if that user name is not associated with any activity.  It really doesn't hurt a thing to have them in there.  If they're gone from the company, what are the chances they are going to show up one afternoon and log into the Vault and mess things up?  But, yes, from an Admin POV... you could change the user's roles and permissions, and even change the passwords associates with an account if this is a legitimate concern.  I think I have 4 or 5 former employees still in the user list, I never think twice about it.

[tahdesign1]

I agree that I would never want to delete a user that actually ever did any real work.

The users that I am talking about were just dumpy accounts that I created to check stuff out to as "released" to lock up the designs.

When I checked stuff out to them I did it WITHOUT downloading the files just to prevent users from editing them.

When someone needed to revise one of these design they would have to ask for them to be made available for the revision.

It was just my method of make the Free Vault have a locking release function.

I am in the process of developing the new deployments and rolling out Vault Pro so I will no longer have to use this work flow.

Was just trying to see if there was a way to get ride of them.

What I might do is just give them a temp name to force them to the bottom of the list.

Them when i need a new user I will rename one of these for that user account. Eventually I will get rid of them that way.