Comment 3 for bug 1965542

+1

As a consortium where settings are managed centrally this is a Really Big Deal. As Terran notes, there are many cases where it is most useful to be able to quickly see all libraries' current settings at a glance. It is also useful to be able to work through a single list to update settings.

My example - I have multiple libraries that have recently changed email domains, so I am checking org.bounced_emails to make sure all libraries have been updated. Right now, a report is the only way to manage this.