Control/Enforce running preflight script on target/project or organization level

Currently, whether the preflight script is used or not used is stored locally within the browser. It might make sense to either store this per user on the backend database or even provide an option for organization administrators to control whether the preflight script is enabled or disabled.

This issues serves for collecting use-cases and feedback.