Comment 3 for bug 1750894

Question for all:

Given that a default value can be applied to any setting at the org unit level, is there a compelling reason for a given setting to also be applied at both the user and workstation level? Or can we safely assume every setting is either a user setting or a workstation setting?

By workstation setting, I mean the value is linked to a row in actor.workstation.

Allowing settings to apply to both users and workstations adds a bit of complexity to the code and UI. Non-admin users would have to make decisions at various points about where settings should be saved. Not to mention the different ways to determine precedence at run time.

Before we go forth and code, I'd like to see if we can avoid this. To clarify, I propose we make it possible for any setting to be a workstation or user setting (via local configuration), but never both. And all settings can have default values applied at the org unit level (with permission).

Thoughts?