nova

50-75%, depending on the team. No one has local admin privileges. Our biggest use-case for triggers is opening multiple password safes. All users have their private safe and access at least one team safe, often daily.

I am aware of that post. "Step 2" is not feasible. That's why I suggested that KeePass could be configured to write triggers to the config.xml instead of enforced.xml.

Moving the triggers to the enforced.xml breaks the deployment for our company. We use the enforced.xml to disble auto-update (because we use software deployment). Having an enforced.xml but not configuring any triggers in the file disables all triggers for everyone. The end users have a lot of different configurations for their triggers which cannot be centralized. It is not feasible for them to edit the triggers manually in XML files. Telling them to use a portable KeePass instance defeats the purpose...

Moving the triggers to the enforced.xml breaks the deployment for our company. We use the enforced.xml to disble auto-update (because we use software deployment). Having an enforced.xml but not configuring any triggers in the file disables all triggers for everyone. The end users have a lot of different configurations for their triggers which cannot be centralized. It is not feasible for them to edit the triggers manuelly in XML files. Telling them to use a portable KeePass instance defeats the purpose...