VP2017 - Hiding project explorer tab and force certain groups to use Item

VP2017 - Hiding project explorer tab and force certain groups to use Item

steveh5
Advisor Advisor
629 Views
3 Replies
Message 1 of 4

VP2017 - Hiding project explorer tab and force certain groups to use Item

steveh5
Advisor
Advisor

Gang (more to the Autodeskers)....

 

With the new permissions in VP2017...still looking at a way to force certain groups to use the item to access files. In prior versions, could hide folder structure in Proj. Explr. but they still could search and get to the files with no watermark.

 

Wondering if the new permissions could grant my request....Anybody know if possible before I try...

 

Here's an old wish list referencing this topic......http://forums.autodesk.com/t5/vault-ideas/proj-explr-ability-to-prevent-access-g-files-from-proj-exp...

 

And...for those who are going to say.."Just use the Thin Client"...problem is that Obsolete state is not a considered a released state with that app and proper files are not shown....and that's a whole different topic :-).

 

Thanks for the insight in advance,

 

Steve H.

Steve Hilvers
Inventor Certified User / Vault Professional Influencer
0 Likes
630 Views
3 Replies
Replies (3)
Message 2 of 4

paul.gunn
Alumni
Alumni

Hi Steve,

 

It is possible that the new security model could be helpful here. Basically the change is to allow the folder security to combine with the file's state security - so that both sets of permissions are fully enforced. Previously the state security would always override (ignore) the security of the folder the file was in.

 

So if you denied read to the files you want to keep hidden, then that denial would stay in effect regardless of the lifecycle state of files. One thing to note is that we still support the old override model (and this remains the case for migrated date), so any lifecycles will need to be configured to use the new option.

 

Hope this helps,

Paul

0 Likes
Message 3 of 4

smilinger
Advisor
Advisor

The combine security model is not helpful here.

 

Because with the combine model user who is denied access at the folder level is denied access forever, regardless of the item security.

 

So you are still stuck to the overriden model, the old way. You can deny user access at the folder level or even the whole project explorer, then set the item security to override file security when item is released. The result is weird:

 

  1. User can see the file through item window, but cannot open the file.
  2. User can download/get the file, however the file will be downloaded to C:\Users\username\Documents\Vault\Inaccessible, instead of the working folder.
  3. User can use View In Window command to view files. For inventor files, user also need access to the inventor project file (ipj).
  4. User can use the view panel to view non-CAD files (PDF, Excel, Word, etc.).
  5. User cannot use the view panel to view CAD files, because user has no access to the dwf visualization attachments.
  6. User can still search! however he can only search the files which are assigned to items released.

I am afraid vault itself is not fully prepared for such weird situation, because I experienced some crash during the test.

0 Likes
Message 4 of 4

cbenner
Mentor
Mentor

As far as I can tell, you STILL cannot see the watermark on Items in the Thin Client.  Visualizations still go back to the File dwf, which does not show the Item watermark.  Been a complaint of mine for years.

0 Likes