Background
Currently we have a flat set of permissions for the module settings, when realisitically we should have a heirachical model like the rest of our modules and FOLIO. Many of the standard FOLIO Stripes components expect a single permission to be passed in as a string, so a multi-permission list for an action in a flatter structure is not always feasible.
In addition, changes were made historically to the "special" "settings.agreements.enabled", providing that with more power than it should ever have had access to. The "correct" model is likely another set of permissions sat above that base permission with any extra permissions granted via those. However the FOLIO model for "editing" permissions appears to be deprecation and recreation with a unique name, which is not possible for these "special" permissions that have conventional names throughout FOLIO.
We are then in a position where a special permission needs editing and no clear way to go about that. In addition, we have developer experience that points to the development workflow around editing/removing/creating new permissions being at best clunky and unclear, and at worst downright opaque and impossible.