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)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Please review our Idea guidelines and best practices before posting a new idea, or voting on an existing one!