Blues Dude

Is this possible?

I added a vote to feature request #2365, thnx!

I'd also very badly need this to be seperate, as discussed in : https://sourceforge.net/p/keepass/discussion/329221/thread/06615d20d2/

We have several user groups which each use their own database. We use one enforced config file to centrally manage them. Database files are in separate folders with NTFS rights set for the corresponding group. So the user groups can only access their own database. Keepass is provisioned to them based on these groups, so when users start Keepass their own DB is loaded. Users don't know the location of the DB file on the network. Preventiong them to use "Save As" will prevent them from making/taking...

I would like the policy to only block save as 'other' locations

Poor response, too bad

Hi Paul, I get what you mean but the policy does not what it intends to do. It blocks save to file en save to url but also save entries. That is not how it should work. This functionality should be split up.

Most users do not know the kdbx location on file shares in general. With policy we already block export and print, save as is the next thing that we'd like to block. Only save entries should be possible