Comment 5 for bug 2043218

Upon further review of the 3 config tables, I can confirm that a new installation is setting UPDATE_ORG_SETTING as the update perm for circ.permit_renew_when_exceeds_fines (in Server Admin > Org Unit Setting Types), so if this perm were to be removed, the update perm for that setting would need to be changed to something else. I don't see any other instances where it is being set for new installs, but I could be missing something.

For existing installs, I can see where it would be a problem for Jeff's use case. We don't use the setting at all in PINES, but it makes sense for different scenarios. In looking further, there is also an UPDATE_ORG_UNIT_SETTING_ALL permission that is used more widely. I wonder if the fact there are two settings that sound like they should do the same thing was intentional or accidental? If accidental, then a solution could be to have the upgrade script swap out any existing usage of UPDATE_ORG_SETTING for UPDATE_ORG_UNIT_SETTING_ALL.

At this time,