3 Kudos
Maarten65

Local Admins for every locations

Status: Future Consideration
by Contributor Maarten65 on ‎07-25-2012 01:14 AM

I like to create local admins. These are users which are leadings on the  locations. (read countries) 

We have five different countries connected to one database.

 

The five local admins should be able to:

 

1) Delete files, even if older versions exists. Or have dwf files attached to it.
2) Synchronize file properties when the jobserver ignored the file. (Should I set user security to write/edit enable in all states?)
3) Remove job from queue, either if still waiting for the job processor or in the list of jobs with an error.

 

These local admins must NOT be able to


1) change vault settings
2) change global settings

 

We have one Vault admin who is responsible for the Vault itself. (Life cycles, properies definitions, indexing, creating users and groups, etc)

 

 

Status: Future Consideration
Maarten65, thanks for submitting this idea. We will review this request as we look to improve our user roles and permissions in the future.
Comments
by Board Manager on ‎09-26-2012 01:23 PM
Status changed to: Future Consideration
Maarten65, thanks for submitting this idea. We will review this request as we look to improve our user roles and permissions in the future.
by thomas.helm on ‎12-03-2012 07:45 AM

In larger customer environments it would not be possible for one person to maintain the vault configuration. The idea will be to have the possibility to restrict specific admin tasks to specific user / groups. E.g. local admins should be able to add a new user to Vault and assign them to a specific folder where the user should have access. But the local admin should have no permissions to change the global lifecycle definition or behaviors like this.

 

by Mentor on ‎03-06-2013 08:38 AM

The Vault needs to have a sub-administrative level to give rights to users without giving the keys to the entire Vault away (some rights can only be held by the Administrator).

 

For instance, “Enforce Unique File Names”, file deletion, management of Categories, Lifecycles and states.

Also, a great enhancement would be to allow FULL ADMIN rights to only a portion or defined area of the Vault, through individual or user group rights.

 

The fact that Vault does not have this capability is extremely frustrating.

by Mentor on ‎09-21-2013 10:39 AM

The Vault needs to have sub-administrative level permissions to give rights to users without giving the keys to the entire Vault away (some rights can only be held by the Administrator).

 

For instance, “Enforce Unique File Names”, file deletion, management of Categories, Lifecycles and states.

Also, a great enhancement would be to allow FULL ADMIN rights to only a portion or defined area of the Vault, through individual or user group rights. For example: Content Center file deletion permissions.

 

The fact that Vault does not have this capability is extremely frustrating, as the I.T. department (at my company) is responsible for ProductStream and thus, Vault, but they have a limited understanding of the Vault and further more, limited time for the everyday user with "Please unlock this file" issues. They refuse to grant me Admin permissions (I'm the Cad Admin!?!), because that would mean giving up access to the entire Vault, it's servers and other "Behinde the scenes" access that they do not wish me to have.

 

All that I really need is access to categories, lifecycles, states, enforce unique file names, file deletion, remove reservation, revision schemes, oh wait, that's almost everything right? Maybe the issue is with my I.T. department...

 

Help!

by Mentor ‎10-21-2013 12:30 PM - edited ‎10-21-2013 12:31 PM

If anyone knows of a way of doing this with the tools that come with Vault productstream already, please let me hear your comments. Did I set up my Vault incorrectly???

 

I'm guessing that I've set up my Vault incorrectly and this is why I haven't received any Kudos for this idea.

 

Please help. 

by Valued Contributor tmoney2007 on ‎11-12-2013 06:07 PM

I agree with this,... a couple hundred users creating content in a vault means that we could really use the ability to give unconditional delete to certain users, but we can't allow them to have configuration control.

 

User configurable roles would be nice...

by Valued Contributor tmoney2007 on ‎11-12-2013 06:25 PM

Nope, its not possible.  I've looked into it.  Even if they have delete privileges at a particular lifecycle state, they won't have unconditional delete (files that have been released and files with historical versions related to other files).

 

I'm with you on this.

You are not logged in.

Log into access your profile, ask and answer questions, share ideas and more. Haven't signed up yet? Register

Announcements
IdeaStation Guidelines
Review guidelines and best practices
before posting a new idea
Top Kudoed Authors
User Kudos Count
14
13
11
7
7