A new permission APPLY_WORKSTATION_SETTING has been added to control who may apply values to workstation settings. Use something like the following to apply the permission to all staff accounts (mileage may vary):

INSERT INTO permission.grp_perm_map (grp, perm, depth)
VALUES (
    (SELECT id FROM permission.grp_tree WHERE name = 'Staff'), -- name may vary
    (SELECT id FROM permission.perm_list WHERE code =
'APPLY_WORKSTATION_SETTING'),
    0 -- or 1, 2, etc.
);

Workstation setting types matching values previously stored in the browser (via localStorage or Hatch) are created as part of this feature. During upgrade, admins should consider whether any of these new setting types should be transferred to user and/or org unit settings instead. Setting type changes can be made at any time, but when a setting type is deleted all of its data is deleted, so a change in type means re-applying the settings in the browser client.

Values stored in the browser will automatically migrate to server settings as each setting is accessed in the browser client. Once migrated, the in-browser copies are deleted.

If a setting type does not exist where the browser expects one, the value is stored in-browser instead and a warning is issued in the console.