Security issue concern

Further to Kevin's reply, permissions within ProjectWise can get very complicated.

Are you trying to stop someone accessing an entire datasource, or just a specific work area within the datasource? If it is just a specific work area, you will need to ensure that the permissions are explicit through the whole folder tree. If someone is specified as no access at a high level folder, but is in another group or list with access to a sub-folder, they will be able to see the files by way of a search.

Hi Mick

For the search I was aware of this, find it useful but never had a chance to really implement in production

From the request I receive I decode this............  prevent from exporting, prevent to save as, prevent from copy-out/check out but at the same time allow client cache to be populate with an auto delete upon closing the document. Or hash the document in the local cache so it can be read only by an authorize client. The decrypt key will be set randomly in the admin panel and change every X minutes.

I saw the captivate function that may seems to solve some issue, like prevent to save outside of ProjectWise ( If I read correctly)

I could resume this to projecting/streaming the document on the screen, block the print screen so the only way to extract the data would be to take a picture of the screen...

Has Kevin Highlight unless I know exactly the paranoia level people have  about the share information we distribute :-)    it will be hard to figure out the proper setup/configuration.

Thank you for your in put. This is the type of feedback I as looking to help me build an idea of what is available and what can be configure

Unless there is something that I have missed, you will not be able to fulfill that criteria. If you can open a file as read-only, you have the ability to export or save-as. Even a captive environment does not stop the ability to export. It may stop the save-as but only on certain programs.

Unless there is something that I have missed, you will not be able to fulfill that criteria. If you can open a file as read-only, you have the ability to export or save-as. Even a captive environment does not stop the ability to export. It may stop the save-as but only on certain programs.