Proj Explr-Ability to prevent access'g files from Proj Exp tab when using items

[steveh3]

Have the ability to prevent certain users from accessing files via the Project Explorer tab. In the present software, all users have access to the files and could possibly print an older or revised file which is no longer or currently not active without any warning. Need the ability to force the users to access all files through item so it is marked with appropriate water mark when viewed and printed. Web Client is an option....but they also require Change Order Access.

I've tried to do it with limiting rights, but if you take rights away in Project Explorer, they also lose ability to access files via the item.

[bjzhangzx]

I may be wrong but I did a little test, and I think what you need can be done in vault.

You can simply deny all access for these users or groups in all lifecycle states of all files or even hide the entire Project Explorer for them, so that basically these users are entirely kicked out of the file world. Then in the specific item lifecycle state, Released, I guess, you can set the override security for the associated files. So as soon as the item is released, these poor users will finally gain the least access you generously give them.

I did this in 2016, but I think it can also be done in earlier versions, and remember you still need to assign these users Document Consumer role, at least.

[steveh3]

Hello...

I'm not sure that this will work.

I believe this is the out-of-the-box setting that you indicated.

If you take their rights away from Project Explorer completely, the file still show up on the item. But, if you try to access the file via the item....you won't have rights because the file actually resides in Project Explorer which you no longer have rights to.

Unless I'm missing something.

[smilinger]

You are right steve, If you take their rights away from Project Explorer completely, the user will not have rights to the files either. Good news is, I still have a workaround:

This way the user still cannot browse in the project explorer, but can access the files in lower level folders. However, the bad news is, the user can still use search to find files, at least those files they have access to, then get the old versions, they can even use search to find those old versions directly.

I guess this is not what you want either.

[smilinger]

Sorry steve, I am also bjzhangzx, I have two login name and I get confused myself.

[steveh3]

Yes...you are correct.

I've been down this road already. It will hide the directories. But, if they search they still can get to the files.

It's a little better...but there's not a hard stop preventing them.

Appreciate the insight.

Thx,

Steve H.

[Senthil_Kumar]

Thanks for sharing your Idea. We use this forum to guide product development and help users in the best way we can based on voting. We occasionally merge Ideas or archive old ones to keep the forum working properly- it ensures there is room for people to review new Ideas and that the most relevant and meaningful ones can gain votes. We’re archiving this Idea because it's been on the board for well over a year and hasn't received many votes from the community. If you want to raise it again and try to gain more support, you're welcome to do so. We’ve found that pictures and mock-ups can help get concepts across and win more votes from other users. If you have questions or see a connection between this Idea and others, let us know. - Vault product team

[steveh3]

Hello All...

This idea is rather old and pertained to just the Thick and old Thin clients at that time.

Would like to revise to make it more current request for an Idea and really should include all clients including Mobile apps and 2023 product releases.

I have no problem if they start with the just NEW Thin Client and then phase in the Mobile Apps, but here's my problem.....

In the item world and attempting to implement the Thin Client to the production floor and have security concerns what they have access. Production has access to files that are not yet released.

Am I missing a setting are is a setting not doing what it says it does?

Need a way to prevent a them from seeing file that has not yet been released, but have access to the latest released version of the files.

Here is a video demonstrating what is going on....

https://autode.sk/3p3BBvE

Am I missing a setting? Or is Thin client missing a setting.

Not sure we can implement with this security risk of production producing part which has not yet been released.

Here's a discussion thread on the topic...

https://forums.autodesk.com/t5/vault-forum/vault-2022-thin-client-security-concerns-with-files-that-...

Appreciated the help/guidance and votes in advance.

Best,

Steve Hilvers