Does anyone know a way to create a user who can only own and
disown documents?
We have a variety of skill levels in our group and for some the vault is very difficult. I have created a user "LOCKED" that everyone has the name and pass for, with the point being that anyone can LOCK parts and not have to worry about someone accidentally checking in a new version over the final design.
This works great and everyone is onboard with it, only problem is that some people forget they are logged in as "LOCKED" and can still potentially update parts without knowing it.
Anyway, if anyone has a solution or alternative, let me know! Thanks!
We have a variety of skill levels in our group and for some the vault is very difficult. I have created a user "LOCKED" that everyone has the name and pass for, with the point being that anyone can LOCK parts and not have to worry about someone accidentally checking in a new version over the final design.
This works great and everyone is onboard with it, only problem is that some people forget they are logged in as "LOCKED" and can still potentially update parts without knowing it.
Anyway, if anyone has a solution or alternative, let me know! Thanks!
If we are talking about Solidworks files only then one way to achieve this is by not installing solidworks on that particular users computer. They can still access the vault either by standalone or explorer and perform the functions you require.
Another method is to use lifecylces and create a user called "LOCKED" but only allow one admin to manage the "LOCKED" account. Create a lifecycle stage called "RELEASED" or something like it and add an automatic rule to change the owner to "LOCKED". The downside is the time required for the unlocking of files by the admin as revisioins arise.
At our company we use the lifecycle feature but leave the files "Unlocked". We depend on Groups and folder access for integrity. We also make sure that when we revise a model that we begin with the latest "RELEASED" version should there be other Non "RELEASED" versions they become evident when we apply the above rule.
I recommend that you take a look at the lifecycle features there may be a more elegant way to handle this.
Good luck,
Samuel