Comment 4 for bug 1750894

Bill, you bring up a good point, and I think having a switch or flag on a setting-type (that is, type of setting, not setting-ish) table to specific workstation or user seems straight forward. +1

However, I wonder if we need to step back and define some terms, first. Primarily, what is meant by "setting" in this context. We currently have: org settings (YAOUS), user settings (opt-in for stuff, record defaults), in-client "settings" (sticky checkboxes, grid column definitions), things that are not settings but live beside the last type (last record retrieved, etc), settings that live in several places (receipt and other print templates), and maybe more that I'm forgetting.

I think before we can even start designing a solution we need to clarify exactly what we mean by "settings" lest we end up with something like the Windows Registry (or, ugh, systemd) catching all manner of random "things".

I'm almost always for the most general solution, but we've got four general solutions right now and I hope we avoid simply adding a fifth and moving the home of some existing settings over to that.