To clarify, we're trying to understand if Laserfiche can be configured to use a DIFFERENT directory to temporarily open PDF files, rather than the Windows temp folder.   What is happening on the client end is that their DoD Security Policy is making it impossible to modify an open file in the Windows temp directory, then resave it back, modified, into Laserfiche.  If we can point to another directory, even one that we create to use, then we won't have to use the locked down Windows temp directory. 

Confirmed it won't work - when customer changes the temp folder, the security policy tracks the new location and causes the same issue with not being able to modify and save back into Laserfiche.  Thanks for your good help on this!

Have you tried using the Check-Out/Check-In functionality instead? The Check-Out dialog allows the user to choose the Location (folder) for the checked out document.

----

Feel free to skip the following passage because it describes a very unlikely customer scenario.

I am not well-versed in system security. Please read with healthy skepticism.

Typically, an application relies on the Windows API function "GetTempPath" to retrieve the temporary directory. This is typically configured using the "TEMP" environment variable.

Normally, a client-side application is run with the same credential as the currently logged-in user. Therefore, files which are created and accessible by the client-side application are also accessible to the user. Allowing access to files by an application while blocking access from the user by other means would either require specialized software, or require a complicated configuration that is unlikely to be waterproof.

If the security policy blocks every application from writing any file to any temporary directory, and blocks the user from opening any file from any local directory, this is a hint that the security policy is intended to force an implementation of "isolation by virtualization" strategy.

Under this strategy, applications (such as the Laserfiche Windows Client) run on a computer (possibly in a server room) to which the end-user do not have physical access. Desktop virtualization software is used to enable end-users to interact with the application via keyboard, mouse, and screen display only. There is no direct access to files and applications on that application machine (guest environment) except those configured by the administrator. We do not sell this type of software, but we have heard some customers using our software inside this type of environment.